Writer

The Writer produces polished content grounded in your team's actual context. Blog posts, documentation, release notes, proposals — all informed by your knowledge graph, your product tree, and your brand voice. No hallucinating features that don't exist.

What the Writer does

Before writing a single word, the Writer reads your knowledge graph — decisions, principles, product features, and prior content. The output is grounded in what your team actually builds and believes, not a generic AI draft that needs heavy editing to match your voice.

Every artifact the Writer produces is linked to the task and visible for review before publishing. You review, request changes, and approve. Nothing goes out without a human in the loop.

When it activates

• A new feature shipped — "write the release notes and blog post"
• Documentation is out of date — "rewrite the onboarding docs"
• A decision was made — "write up the rationale as an internal memo"
• Marketing needs content — "write a blog post about our approach to X"
• A customer asked a question — "write a help article answering this"

What it reads

• Knowledge atoms — especially LEARNING and DECISION
• The product tree — features, what actually exists
• Prior content artifacts — for voice and style
• The task description and brief you give it

What it needs

• A clear brief: what type of content, who it's for, what it should cover
• Optional: a source document or set of atoms to draw from
• Optional: tone guidance (formal, conversational, technical)
• The richer your knowledge graph, the more grounded and accurate the output

What it produces

• A polished draft saved as an artifact on the task
• Cited references to the atoms and documents it drew from
• A summary comment noting key decisions made in the writing

Example: documenting a growth experiment

Your team just shipped a referral program. The Coder opened the PR, it merged, and now you need: release notes, updated docs, and a blog post announcing the feature.

You create three tasks and assign each to the Writer. It reads the PR description, the atoms saved by the Researcher during planning, and your brand voice guidelines. In 10 minutes you have three drafts ready for review — all consistent, all grounded in what actually shipped.

Best for

• Documentation — user-facing and internal
• Marketing content — blog posts, landing page copy, case studies
• Internal memos — decision writeups, post-mortems, strategy summaries
• Changelog entries and release notes
• Proposals and specs that require synthesis of existing knowledge