Synthesize feature BRDs from Jira, Axure, Figma, and Confluence artifacts.
npx skills add https://github.com/Scripsteam/scrips-stack --skill synth
Please help me install this Agent Skill. Skill: synth Source: https://github.com/Scripsteam/scrips-stack/tree/main/synth Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill synth
This synthesis BRD generator brings Jira epic details, Axure, Figma, Confluence, and brain memos together into a single, comprehensive BRD with six mandatory sections, reducing context-switching and ensuring alignment across design and product teams.
Announce a feature slug and run synth to generate the BRD scaffold for that feature.
High-intent search queries and answers about installing and using this skill.
To generate a BRD from Jira, Figma, and Confluence, synthesize these artifacts alongside Axure and brain memos into a unified document. This process aggregates scattered design and product context into a cohesive six-section Business Requirements Document scaffold.
You need to synthesize a BRD when starting a new feature or when Jira epics are sparse and require deeper product context. It enforces traceability to sources and mandatory sections for personas, journeys, state machines, and acceptance criteria before sprint execution.
Synthesizing feature requirements requires six mandatory sections: personas, journeys, entity state machines, BDD use cases, integration scenarios, and acceptance criteria. This structure enforces Stage 02 pipeline rules and ensures comprehensive feature documentation.
Yes, you can aggregate Axure prototypes and brain memos into a single requirements document. The synthesis process brings these inputs together with Jira and Figma artifacts, reducing context-switching and aligning design and product teams.
Yes, generating a BRD scaffold enforces traceability to Jira, Confluence, and other source artifacts. It maps aggregated inputs directly into the mandatory sections, ensuring every persona, state machine, and acceptance criterion traces back to original design and epic details.
STUkhConsolidate project requirements from Jira, Confluence, Figma, and local files into a unified spec.
codihausOrganize customer requirements into a Business Requirements Document with use cases.
damianpapadopoulosSynthesize product discovery briefs from Jira, Confluence, and user input.
abhishekchoudhariConvert PRDs into Jira-ready Epic and Story hierarchies.
