Define architecture decisions and map requirements to technical approaches before planning.
npx skills add https://github.com/NSObjects/specpowers --skill designing
Please help me install this Agent Skill. Skill: designing Source: https://github.com/NSObjects/specpowers/tree/main/skills/designing Command: npx skills add https://github.com/NSObjects/specpowers --skill designing
Prevents premature coding by ensuring every requirement and scenario leads to a mapped technical approach before implementation begins.
Ask the designing skill to map every requirement to a technical approach before moving into planning.
High-intent search queries and answers about installing and using this skill.
To map requirements to a technical architecture, you define architecture decisions and trace each requirement to a specific technical approach, ensuring implementation begins with a clear technical plan rather than guesses.
Documenting architecture decisions involves analyzing requirements, discovering existing patterns, and recording documented trade-offs to break features into single-purpose units with clear file boundaries and interfaces.
You need spec-driven technical design when requirements and scenarios are understood but architectural approaches, data flow, and file boundaries remain undecided, preventing premature coding by finalizing the technical plan.
Ensure requirement traceability by mapping every agreed spec and scenario to a defined technical approach, tracking each requirement through pattern discovery and design isolation before entering the planning phase.
Yes, you can isolate feature boundaries by breaking features into single-purpose units with defined interfaces, mapping files clearly once your agreed specs provide understood requirements and scenarios.
Starting without a technical design risks premature coding by leaving architectural approaches undecided, meaning data flow and responsibilities lack mapped trade-offs and clear file boundaries before planning begins.
blueif16Analyze PRDs and generate split mini-PRDs with YAML sections.
estevanhernandez-stack-edTranslate PRDs into architecture blueprints with data flows and file structures.
oxhagolliDecompose approved plans into independent parallel work streams for subagents.
falconntGuide teams through structured brainstorming with one-question-at-a-time exploration.
