Translate Product Requirements Documents into technical specifications and implementation epics.
npx skills add https://github.com/MmtBkn/swe --skill swe-spec
Please help me install this Agent Skill. Skill: swe-spec Source: https://github.com/MmtBkn/swe/tree/main/swe-spec Command: npx skills add https://github.com/MmtBkn/swe --skill swe-spec
This Skill automates the translation of Product Requirements Documents (PRDs) into comprehensive technical specifications, detailed architecture designs, and actionable implementation epics, ensuring alignment with repository standards and best practices.
swe-spec to generate a detailed technical design document, define API contracts, outline database schema changes, and create epics for the engineering team to implement.Use the swe-spec skill to turn the PRD located at 'proposals/new-feature-prd.md' into a technical specification and implementation epics.
High-intent search queries and answers about installing and using this skill.
To turn a PRD into a technical specification, you provide the product requirements document to an automated translation tool that generates detailed architectural designs and actionable implementation epics. This ensures alignment with repository standards and engineering best practices.
Deriving implementation epics from requirements analysis involves breaking down technical specifications into manageable development tasks with clear scope and acceptance criteria. This ensures traceability from the original product requirements directly to actionable engineering stories.
Generating detailed architecture designs from a PRD requires analyzing repository context and applying software design best practices. This produces structured technical specifications including API contracts, database schema changes, and testing plans.
Yes, you can use existing repository context to outline database schema changes and define API contracts. The system analyzes the repository environment to ensure generated technical specifications align with current engineering standards and project scope.
The best way to ensure traceability from software design to implementation epics is to automate the translation of PRDs into structured technical specifications. This creates a clear lineage from architectural designs directly to actionable development stories.
stellarlinkcoGather product requirements interactively and generate Markdown PRD documents.
coolbeevipConvert technical debt specifications into engineering issues with dependency tracking.
HillBombCreationsAutomate code review workflows with Python static analysis and AWS documentation.
tgmarinhoConvert conversation content into a Product Requirements Document and publish it to an issue tracker.