Writing Design Docs skill: what it does and how to install it
Structures proposals, RFCs, specifications and migration plans with explicit choices, costs, evidence and review-ready completeness checks.
Summary generated from the skill's documentation.
Install
$ npx skills add riekelt/technical-writer --skill writing-design-docsRun it in a terminal. If your agent is already running, start a new session so it picks the skill up.
About this skill
What it does. Builds design documents from a conclusion-first structure with numbered chapters, goals and non-goals, a grounding section for verified facts, and a Why & What box for each significant choice. It separates facts from proposals, records alternatives and fallbacks, assigns owners to open questions, and checks for vague requirements, undefined references and unverifiable outputs.
When to use it. Use it for proposals, RFCs, design documents, specifications, migration plans and other writing that argues for or scopes a change. Do not use it for recording an already-made decision, procedures or status reports.
History
Repo stars
33
Tracking since . A chart appears once there are 7 days of data.
Stars are counted for the whole repository, which holds 7 skills.
Installs
18.3k
Tracking since . A chart appears once there are 7 days of data.
Installs via skills.sh
Similar skills
- Write Feature DocsDrafts Warp feature documentation from product and technical specs, verifies claims in the codebase, and produces an MDX page with a review-ready draft PR.
- Research GrantsWrites research proposals for NSF, NIH, DOE and DARPA, with agency-specific formatting, review criteria and budgets.
- Scientific WritingDrafts, revises and audits scientific manuscripts with evidence provenance and reporting-guideline coverage.