Clarify requirements and produce validated solution designs before coding.
npx skills add https://github.com/GmwEnterprise/route-spec --skill design-gmwenterprise
Please help me install this Agent Skill. Skill: design Source: https://github.com/GmwEnterprise/route-spec/tree/main/skills/design Command: npx skills add https://github.com/GmwEnterprise/route-spec --skill design-gmwenterprise
This skill eliminates the risk of rework and scope creep caused by ambiguous requirements and unplanned development, by ensuring requirements are fully clarified and a validated solution design is agreed upon before any coding begins.
Use the design skill to create a solution design for the new third-party payment integration feature with unclear requirements.
High-intent search queries and answers about installing and using this skill.
To clarify ambiguous software requirements before development, you can use targeted blocking questions with reference options to resolve critical scope ambiguities. This approach prevents scope creep and ensures a validated solution design is agreed upon before coding begins.
Preventing development rework from unclear scope requires defining explicit in-scope and out-of-scope items alongside acceptance criteria. Creating a validated solution design prior to coding initiation effectively eliminates the risk of unplanned development and rework.
Performing code impact analysis for a new feature involves identifying affected code files and outlining potential risks within your solution design. This ensures all impacted modules are documented and validated against functional requirements before execution.
Documenting acceptance criteria for medium-to-large development tasks is essential for defining clear scope and preventing rework. It ensures functional requirements are satisfied and provides a validated solution design before any coding begins.
Targeted blocking questions can resolve critical scope ambiguities by asking one question at a time with 2-3 reference options. This method prevents overwhelming the user while effectively confirming the implementation direction for unclear requirements.
devmuslimExtract business rules and requirements from BRD, SRS, and User Stories.
idiotLeoLYJEnforce alignment between interaction, architecture, design, and implementation phases.
noise-xyzAnalyze Brane SDK code changes to identify affected modules and tests.
seiei-sogenTransform unstructured requirements into implementation plans with testable tasks and interface definitions.
