Loading

Write the design doc or RFC

A structured proposal with prior art and trade-offs filled in.

10 minEngineeringClaude Cowork
Loading

Set up

Try a plugin

The Engineering plugin ships with /system-design as a starting point, already structured to fill an RFC template and look up prior art across your wiki. If your admin manages plugins and it's not available yet, skip this step. The prompt below works without it.

EngineeringStreamline engineering workflows — standups, code review, architecture decisions, incident response, and technical documentation. Works with your existing tools or standalone.
Add
/system-designDesign systems, services, and architectures.
Open in Claude
/architectureCreate or evaluate an architecture decision record (ADR).
Open in Claude

Connect your tools

Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access.

Add a connector for each tool you want Claude to use.

Confluence
Look up prior RFCs and architecture pages and write the new doc straight into your engineering space. Confluence access comes through the Atlassian Rovo connector (Jira and Confluence).
Connect
GitHub
Read the relevant code and past ADRs so the proposal references the system as it actually is.
Connect
NotionOptional
Pull the RFC template and publish the draft into your design-review database.
Connect

Set your working folder

Drag the files you'll use (your RFC template, the one-pager or notes you've already written, related past RFCs, the service's architecture diagram) into one folder and point Claude at it. Claude reads from there and writes the draft, the alternatives table, and the diagram back to it. Create a project from your RFCs folder so your template, your review checklist, and your team's writing conventions stay attached.

RFCs / 0087-streaming-events
rfc-template.mdJan 4, 20262 KB
notes-streaming-migration.mdApr 24, 20265 KB
current-pipeline-diagram.pngMar 11, 2026142 KB
In Cowork’s chat bar:RFCs / 0087-streaming-events

The prompt

Copy this into Claude

Write a design doc for moving our event pipeline from batch to streaming. Look up prior art and architecture constraints, then draft the proposal in our RFC template: problem, goals and non-goals, two or three approaches with trade-offs, the recommendation, and open questions. I'll fill in the parts only I know.

RFCs / 0087-streaming-events

Why this works

Prompt

Ask for prior art explicitly. Claude searches your wiki and past RFCs so the doc cites what's been tried before.

Prompt

Force two or three approaches. You get a real trade-off table, not a sales pitch for the first idea.

Prompt

Say which parts you'll fill in. Claude handles structure and lookup; you spend time on the actual judgment call.

Source

Give it your template to follow. Output follows your sections and headings, so reviewers see the structure they expect.

Get a better draft

Practice

Add an example to match. Drop an example you like into the folder and Claude matches your structure and voice.

Practice

Ask it to flag uncertainty. Add "flag anything you're not confident about" so you know where to look first when you review the draft.

Make Claude work for you

A plugin skill is a starting point. Customize it with your own practices and expertise, or save what you've done as a skill of your own. A few minutes of conversation and it runs with your standards from then on.

Make what we've done in this task so far into a skill, or edit the /system-design skill with my feedback.

RFCs

Make it repeatable

Run it from any one-pager

Design docs start as a paragraph in a Slack thread or a notes file. Ask Claude to set up a scheduled task or open Scheduled in the sidebar, and the customized skill watches your RFCs/inbox folder and turns any new one-pager into a structured first draft.

Set up a scheduled task for weekdays at 9am: check RFCs/inbox for new one-pagers, run /system-design on each one, and write the structured draft to a numbered folder under RFCs/.

RFCs
Scheduled taskActive
RFC inbox to draft

Weekdays at 9am, picks up new one-pagers from RFCs/inbox, runs /system-design with prior-art lookup, and writes a structured draft to a numbered RFC folder.

Every weekday at 9:00amOpen in Claude

Share with your teammates

Your customized /system-design now carries your template, your prior-art sources, and your reviewers' standing questions. Share it so every tech lead's RFC arrives in the same shape, and architecture review spends time on the decision instead of the formatting.

What changes for design review