Write ADRs, RFCs, design specs, and requirement documents with testable statements.
npx skills add https://github.com/SgtPooki/skills --skill writing-spec-sgtpooki
Please help me install this Agent Skill. Skill: writing-spec Source: https://github.com/SgtPooki/skills/tree/main/skills/writing-spec Command: npx skills add https://github.com/SgtPooki/skills --skill writing-spec-sgtpooki
High-intent search queries and answers about installing and using this skill.
Use the MADR skeleton: context stating the forces factually, at least two options with honest costs, the decision with its deciding factor, and consequences including the losses. Record one decision per ADR, number them, and never edit a superseded ADR.
Pair every requirement with a validation condition describing how you will know it is met, and keep one requirement per statement. Use RFC 2119 keywords like MUST and SHOULD only when the document declares them or the repo already follows that convention.
Use EARS only when requirements need unusual rigor, such as safety-relevant behavior, protocol conformance, or contractual acceptance criteria. For ordinary ADRs and design specs, the basic testable-requirement rule is sufficient.
Specs record decisions or constrain future behavior, while documentation explains current behavior. This skill covers the former; documents explaining existing behavior belong to a docs-writing skill instead.
Only use RFC 2119/8174 keywords when the document explicitly declares them or the repository already writes specs that way. Without the declaration, use plain lowercase must and should consistently.
BEIRUXGuide collaborative drafting of technical specs, proposals, and decision records.
arthur-debertBreak specs and ADRs into epic and work stream tracker issues.
human-avatarTranscribes and summarizes audio/video files with ChatGPT-grade AI.
Busboom-FooApply small code changes directly to master with a deterministic test workflow.
