Skip to content
Agentmart
Submit a tool

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

IndexedMIT★ 1
Write a review

Chalk Labs

Need help deploying design-doc?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

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.

We use your email only for this newsletter. Privacy

About

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).

Use cases: documents, design, writing

Reviews

Write a review

No 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 and code. Checked Nov 1, 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

Signals

Stars
1
Forks
0
Open issues
0
Last commit (this folder)
Oct 19, 2026 (13 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

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get design-doc running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying design-doc?

CallGet help
Cite this page

design-doc skill. Agent Mart. https://agentmart.dev/skills/prestarius-design-doc (last updated 2026-10-24)