Why sdd exists
AI needs a little structure. People need that structure to stay light.
Two problems you’ve probably felt
Chat-only coding ships fast. Then the why is gone — buried in threads, lost context windows, or a PR that only shows the diff.
Heavy process tools keep the trail — and often feel like a second job for a three-line fix.
You bounce between “move fast and forget” and “process theater.” Neither fits a world where the AI can draft a thousand lines before you finish naming the ticket.
The simple bet
The AI writes. sdd keeps the plan and progress.
- Notes live in your repo, next to the code — not only in a cloud product.
- Small work stays short; bigger work can go deeper.
- One short playbook, not a pile of plugins.
- Pick one AI at setup. Use any editor.
What we won’t force on you
- A required IDE extension
- A hosted suite as the only source of truth
- Mandatory archive folders
Who it’s for
| You | Why it helps |
|---|---|
| Solo / small team | A bit of structure without ceremony |
| Product team | Same trail in every PR |
| Enterprise | Reviewable steps next to the code |
Try before you buy the idea
Then: Everyday loop · New product