multi-project-spec-mapper

What This Skill Does

The multi-project-spec-mapper is an advanced AI agent skill designed to streamline technical requirements gathering for complex, multi-repo, or microservices-based software architectures. It functions as an automated bridge between high-level user stories and granular project-specific documentation. By scanning your project's configuration, the skill identifies active JIRA or GitHub sync profiles across multiple services (FE, BE, MOBILE, INFRA). It then performs intelligent natural language classification on your raw requirement documents, mapping specific features to the relevant architectural domain. Beyond classification, it automates the file system hierarchy, creating standardized directories and YAML-frontmatter-compliant specification files for each project, ensuring your development teams have immediate access to context-aware documentation.

Installation

To integrate this skill into your OpenClaw environment, execute the following installation command in your terminal:

clawhub install openclaw/skills/skills/anton-abyzov/sw-multi-project-spec-mapper

Ensure that your workspace contains a valid .specweave configuration folder. Once installed, the skill will automatically monitor your spec generation workflows and provide project-specific categorization suggestions.

Use Cases

This skill is ideal for:

• Microservices Orchestration: Automatically distributing requirements for a unified user flow across separate repositories.
• Brownfield Project Migration: Converting legacy monolithic requirement documents into structured, team-specific documentation.
• Multi-Platform Feature Releases: Synchronizing user stories across Web, iOS, and Android platforms to ensure feature parity.
• DevOps/Infrastructure Alignment: Mapping feature requests to infrastructure or deployment tasks automatically.

Example Prompts

1. "OpenClaw, I have a massive feature doc for the new Checkout flow. Can you use the multi-project-spec-mapper to split this into separate FE and BE specs and assign them to the correct JIRA components?"
2. "Analyze this list of user stories and map them to our MOBILE, FE, and BE folders based on our current tech stack: React, React Native, and Node.js."
3. "Setup our project documentation structure for a new microservice. I want the multi-project-spec-mapper to create sub-directories for FE and BE and ensure the YAML frontmatter is configured for our JIRA sync."

Tips & Limitations

• Config Priority: Always ensure your config.json is updated with all active project aliases so the mapper recognizes your full stack.
• Mandatory Frontmatter: Remember that the skill requires specific YAML headers to sync with your external JIRA/GitHub repositories; do not remove the project or increment tags.
• Confidence Thresholds: The skill operates on probability; always verify classifications for edge cases where a feature might span across both UI and Backend logic.
• Manual Refinement: While highly accurate, always review the generated file structure for 'Shared' components to ensure dependencies are documented correctly in the SHARED folder.