<h2 id="role">Role</h2>
<p>The Design Doc Writer takes an approved PRD and produces a technical design
document that bridges product requirements to implementation. Its Task
Breakdown section feeds directly into Claude Code's plan mode.</p>
<p>Interview-first. The agent asks questions one at a time to surface
constraints, validate architectural choices, and stress-test alternatives
before committing anything to the page.</p>
<h2 id="identity">Identity</h2>
<p><img src="/images/agent-design-doc-writer.png" alt="Design Doc Writer avatar"></p>
<ul>
<li><strong>Model</strong>: Opus</li>
<li><strong>Animal totem</strong>: Nautilus (mathematically precise structure, scales from first principles)</li>
</ul>
<h2 id="workflow">Workflow</h2>
<ol>
<li>Read system context (CLAUDE.md, wiki index, existing design docs, agent definitions, target PRD)</li>
<li>Interview Kyle one question at a time across five categories:
architecture, alternatives, constraints, task breakdown, open questions</li>
<li>Gate: "I have enough to write a design doc. Proceeding."</li>
<li>Write design doc to <code>wiki/design-docs/&#x3C;slug>.md</code> using the standard template</li>
<li>Validate: delegate to a fresh validator subagent that checks every task
is atomic, sequenced, and maps back to a PRD acceptance criterion</li>
</ol>
<h2 id="output">Output</h2>
<p>A draft design doc at <code>apps/blog/blog/markdown/wiki/design-docs/&#x3C;slug>.md</code>.</p>
<h2 id="invocation">Invocation</h2>
<pre><code class="language-bash">claude --agent design-doc-writer
</code></pre>
<h2 id="agent-definition">Agent definition</h2>
<p>Source: <code>.claude/agents/design-doc-writer.md</code></p>


Takes an approved PRD and produces a technical design document with architecture, alternatives, and a task breakdown.

Kyle Pericak

"It works in my environment"

Design Doc Writer

Role

Identity

Workflow

Output

Invocation

Agent definition