Generate structured technical documentation with objectives, steps, and verification criteria.
npx skills add https://github.com/nushey/sdd-flow --skill writing-skill-nushey
Please help me install this Agent Skill. Skill: writing-skill Source: https://github.com/nushey/sdd-flow/tree/main/skills/writing-skill Command: npx skills add https://github.com/nushey/sdd-flow --skill writing-skill-nushey
It helps prevent vague, incomplete, or hard-to-review technical plans by enforcing objective-first structure, hierarchical clarity, and explicit acceptance criteria.
Use writing-skill to draft a structured plan or design document with an objective, hierarchical sections, atomic steps, and a clear how-to-verify checklist.
High-intent search queries and answers about installing and using this skill.
Writing technical specifications requires hierarchical Markdown headings, imperative implementation steps, and a dedicated verification section to enforce measurable acceptance criteria. This approach eliminates ambiguity by structuring goals, prerequisites, and explicit verification checklists for objective-driven execution.
The best way to structure a design document is using hierarchical Markdown headings that separate scope, goals, prerequisites, and implementation steps. This hierarchical clarity turns intentions into actionable, imperative steps and ensures the plan can be reliably checked by others during execution.
Creating an implementation plan with verification requirements involves defining objective-first sections for goals and atomic steps, followed by an explicit how-to-verify checklist. This enforces measurable acceptance criteria and ensures the resulting task list can be reliably reviewed by others.
Technical writing lacks hierarchical clarity when it misses objective-first structuring and explicit acceptance criteria. Enforcing clear Markdown sections for goals, prerequisites, atomic steps, and verification ensures implementation plans are unambiguous and can be reliably checked by reviewers.
Yes, Markdown structure supports generating task lists by using hierarchical headings to organize scope and atomic imperative steps. This structure explicitly accommodates acceptance criteria by requiring a dedicated verification section, ensuring the generated task list fits objective-driven execution workflows.
MazenMradGenerate a structured game test design document with prioritized scenarios and coverage matrix.
zxdxjtuDecompose feature-driven test suites into atomic tasks with wave-based parallel execution and module stewardship artifacts.
dmmulroyConvert Markdown planning documents into hierarchical Overseer tasks via MCP codemode.
tobieapbOptimized for clarity and speed, discover the best-fit coffee bean for your personality and palate with our quick quiz — choose wisely, your next favorite awaits!
