Write detailed design issues with standardized templates before creating specs.
npx skills add https://github.com/Varuas37/spec-test --skill spec-issue
Please help me install this Agent Skill. Skill: spec-issue Source: https://github.com/Varuas37/spec-test/tree/main/src/spec_test/skills/spec-issue Command: npx skills add https://github.com/Varuas37/spec-test --skill spec-issue
This skill guides teams to write a detailed issue before creating specs to capture the rationale, context, trade-offs, and decisions.
Create a new issue under design/issues/NNN-short-title.md, including a Summary, Motivation, Detailed Description, Options Considered, Decision, and Related Specs. Then link it to the relevant specs and mark status steps as completed.
High-intent search queries and answers about installing and using this skill.
Document design decisions by writing a detailed issue first to capture rationale, context, and trade-offs. Use a standardized issue template containing Summary, Motivation, Options Considered, and Decision sections before proceeding to spec creation.
A structured issue template for feature planning must include Summary, Motivation, Detailed Description, Options Considered, Decision, Related Specs, and Status. This ensures consistent documentation of problems and trade-offs across the team.
Write an issue before defining specs when planning new features, clarifying problems, or documenting trade-offs. This approach anchors decisions and captures context upfront, preventing loss of rationale during later specification phases.
Organize issue files by saving them under the design/issues directory using the naming convention NNN-short-title.md. This standardized storage links issues directly to related specs and tracks completion status effectively.
Writing issues before specs works for tracking feature status by including a Status section in the issue document. Teams mark status steps as completed and link the issue to relevant specs for full workflow visibility.
The best way to capture rationale and trade-offs is drafting an issue outlining the problem, options considered, and final decision. This structured documentation preserves context and anchors decisions before spec development begins.
OzeroHAXDefine project context, problem statement, and MVP boundaries.
growilabsReview technical design documents and issue a GO/NO-GO decision.
thrashr888Generate standardized project documentation using the 5-style system templates.
vrcmsCapture and maintain architectural decision records in standardized markdown format.
