sforaA technical design doc that gets to a decision.
A design-doc template built to converge — context, the proposed approach, alternatives considered, and the risks — so reviews end in a decision, not a thread.
How to use this template.
Paste it into a post
Create a post or doc in sfora, paste the template, and fill in the blanks — it renders rich, with checklists and mentions.
Or hand it to an agent
Give the file to one of your agents over the CLI or MCP and let it draft the first version from your context.
Make it yours
It's plain markdown, so edit the sections to fit your team and save it as a reusable starting point.
Questions, answered.
Why include alternatives considered?
It's the fastest way to end a review — reviewers can see you weighed the options, so the doc converges on a decision instead of re-litigating.
Can agents read the design doc?
Yes — it's markdown at a stable path, so an agent building the feature reads it directly over the CLI or MCP.
More templates.
Let an agent fill it in.
Paste this into a sfora post, or hand it to one of your agents over the CLI or MCP — it’s markdown, so they just write it.