Can it handle monorepos and multi-repo setups?

Absolutely. It can organize files into separate directories within a monorepo or map them to entirely different external GitHub repositories and JIRA boards.

Does this work with custom project names?

Yes, you can define custom project identifiers, specific keywords, and mapping rules within the SpecWeave config.json file.

How does the skill decide which project a user story belongs to?

It analyzes keywords like 'UI', 'API', or 'native' and technical stacks like 'React' or 'PostgreSQL' to calculate a confidence score for each project mapping.

What happens if a user story covers multiple domains?

The skill can route cross-cutting concerns to a 'SHARED' folder or suggest splitting the story based on the specific acceptance criteria provided.

Multi-Project Spec Mapper

Name: Multi-Project Spec Mapper
Author: anton-abyzov

byanton-abyzov

•

Collaboration Tools

Organizes complex software specifications by intelligently mapping user stories to specific project domains like frontend, backend, and mobile.

About

The Multi-Project Spec Mapper is a specialized capability for SpecWeave designed to automate the organization of large-scale software documentation. It analyzes monolithic specifications and user stories to determine their technical context—detecting keywords like 'UI' for frontend or 'API' for backend—and automatically routes them into structured project folders. This skill is essential for teams working with microservices, brownfield migrations, or multi-platform applications, ensuring that JIRA epics and GitHub repositories stay perfectly synchronized across separate engineering domains without manual intervention.

Key Features

Bidirectional synchronization with JIRA and GitHub project structures
Customizable confidence thresholds for tech-stack mapping
Intelligent project detection via configuration analysis
Automated splitting of monolithic specs into project-specific files
Keyword-based user story classification for FE, BE, Mobile, and Infra
13 GitHub stars

Use Cases

Organizing specifications for a microservices architecture with multiple service repositories
Splitting a single feature request into separate frontend and backend implementation tasks
Synchronizing user stories across different JIRA boards for specialized engineering teams

About

Key Features

Bidirectional synchronization with JIRA and GitHub project structures
Customizable confidence thresholds for tech-stack mapping
Intelligent project detection via configuration analysis
Automated splitting of monolithic specs into project-specific files
Keyword-based user story classification for FE, BE, Mobile, and Infra
13 GitHub stars

Use Cases

Organizing specifications for a microservices architecture with multiple service repositories
Splitting a single feature request into separate frontend and backend implementation tasks
Synchronizing user stories across different JIRA boards for specialized engineering teams