design-doc
Author a design document (RFC) for a feature or system before the decision is locked — problem, requirements, options, proposed design, risks.
Skill by prestarius
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/prestarius-design-doc
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: documents, design, writing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/design-doc
What's inside
- Skill name
design-doc- Description
- Author a design document (RFC) for a feature or system before the decision is locked — problem, requirements, options, proposed design, risks. Use whenever the user says "write a design doc", "draft an RFC", "write up the design", "proposal for the team", or has finished discussing an approach and needs the document that carries it to reviewers. Upstream of domain-modeling (the ADR) and to-spec (the implementation spec).
- License
- MIT
- Compatibility
- Claude Code (uses effort); name + description work in any Agent Skills tool
- Instructions
- 23 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
Write ONE Markdown design document a reviewer can evaluate without having been in the discussion. Read `./CONTEXT.md` first — stack, domain language, constraints come from there, not assumptions. Sections, in order: 1. **Problem & context** — what hurts today and why now. Neutral; no solution yet. 2. **Goals / non-goals** — what this design must achieve; what is explicitly out of scope. 3. **Requirements & constraints** — functional and non-functional (scale, latency, budget, compliance per `CONTEXT.md`), each marked hard or soft. 4. **Current state** — the relevant existing architecture, in the project's own terms. 5. **Proposed design** — the recommended approach, concrete enough to challenge: components, boundaries, data flow, sync/async choices. Bias to the simplest design that meets the requirements; say what was deliberately left simple. 6. **Options considered** — the real alternatives via the `tradeoff-table` skill, plus the one-line reason each lost. A design doc with no rejected options is incomplete. 7. **Risks & open questions** — what could invalidate the design; what reviewers must decide. Style: decisive, terse, no hedging; diagrams (Mermaid) where they remove ambiguity. If something load-bearing is genuinely unknown, ask one sharp question before writing rather than inventing it. Downstream: once the design is accepted, capture the decision with the `domain-modeling` skill; to hand the build to an agent, use `to-spec`; to hand it to a team, use `to-tickets`.
From prestarius/jet-skills-stack, MIT.
More from prestarius/jet-skills-stack
- 0.587score
document
prestarius
Generate complete, structured documentation for a feature, module, API, or project using the Diataxis framework (tutorial / how-to / reference / explanation).
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
article-writing
prestarius
Draft a long-form article, blog post, essay, or technical write-up in the author's own voice — outline first, then a full draft that reads like a person wrote…
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
migration-plan
prestarius
Turn a modernization goal or architectural finding into a phased migration plan — current state to target state with coexistence, cutover criteria, and…
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
meeting-notes
prestarius
Turn raw meeting notes or a transcript into structured minutes — decisions, action items with owners, open questions — and route them onward (Obsidian note…
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
power-phrase
prestarius
Orchestrate a full build session with the 6 Power Phrases framework — interview, spec, verify, sub-agents, skill-capture, automate — sequencing the phases and…
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
postmortem
prestarius
Write a blameless incident postmortem — impact, timeline, contributing factors, what went well/poorly, concrete follow-up actions.
SkillAFreshness: A★ 1Claude Code +9 - 0.584score
changelog-watch
prestarius
Diff the Claude Code changelog since this stack's verified baseline and report which skills, hooks, or docs are possibly stale.
SkillAFreshness: A★ 1Claude Code - 0.579score
architect-review
prestarius
Review a design, PR, or proposal as a Staff Solution Architect — simplicity, scalability, event-driven boundaries, security, cost, compliance, operability —…
SkillAFreshness: A★ 1Claude Code +9 - 0.552score
skill-stocktake
prestarius
Audit a collection of Claude Code skills for overlap, stale technical references, context cost, name/trigger/scope drift, and (for third-party skills) unsafe…
SkillBFreshness: B★ 1Claude Code +9 - 0.547score
headless-loop
prestarius
Generate ready-to-run Claude Code automation loop scripts for unattended, headless workflows.
SkillBFreshness: B★ 1Claude Code +9 - 0.547score
estimate
prestarius
Estimate effort for a feature, plan, or backlog with explicit assumptions and confidence ranges — never a single confident number.
SkillBFreshness: B★ 1Claude Code +9 - 0.547score
market-research
prestarius
Research a market, landscape, or set of players and produce source-attributed findings — every claim cited, recency noted.
SkillBFreshness: B★ 1Claude Code +9
Signals
- Stars
- 1
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Oct 19, 2026 (9 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/prestarius/jet-skills-stack
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from prestarius
- 0.587score
migration-plan
prestarius
Turn a modernization goal or architectural finding into a phased migration plan — current state to target state with coexistence, cutover criteria, and…
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
postmortem
prestarius
Write a blameless incident postmortem — impact, timeline, contributing factors, what went well/poorly, concrete follow-up actions.
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
document
prestarius
Generate complete, structured documentation for a feature, module, API, or project using the Diataxis framework (tutorial / how-to / reference / explanation).
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
article-writing
prestarius
Draft a long-form article, blog post, essay, or technical write-up in the author's own voice — outline first, then a full draft that reads like a person wrote…
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
meeting-notes
prestarius
Turn raw meeting notes or a transcript into structured minutes — decisions, action items with owners, open questions — and route them onward (Obsidian note…
SkillAFreshness: A★ 1Claude Code +9 - 0.587score
power-phrase
prestarius
Orchestrate a full build session with the 6 Power Phrases framework — interview, spec, verify, sub-agents, skill-capture, automate — sequencing the phases and…
SkillAFreshness: A★ 1Claude Code +9
Cite this page
design-doc skill. Agent Mart. https://agentmart.dev/skills/prestarius-design-doc (last updated 2026-10-24)