DevSpecs Documentation
DevSpecs is a local-first CLI for bounded AI coding work. It turns repo intent into task slices, packed context, one-target prompts, checkpoints, and decision gates.
On first use, DevSpecs indexes local repo evidence before showing ds map,
ds recent, or ds find results. ds apply emits the next one-slice prompt,
and indexing progress stays out of JSON and quiet result streams.
Issue trackers are still useful for epics, stories, and tasks. They are not enough for the AI execution layer: agents create prompts, attempts, partial learnings, failed paths, and follow-up iterations between ticket updates. DevSpecs keeps that loop in local files.
Start with the task when you know the goal:
ds task "fix Swagger OAuth redirect"
ds apply
ds task checkpoint A01 --decision improve
ds task slice add <task-id> "cover missing redirect edge case" --after A01 --reason improve
ds apply
Use the trust layer when the target is unclear:
ds map
ds recent
ds find "oauth redirect"
Core Jobs
| Job | Command |
|---|---|
| Bound an agent task | ds task "<goal>" |
| Emit the next one-slice prompt | ds apply |
| Create a compact one-off task | ds task "<goal>" --quick |
| Add a follow-up slice | ds task slice add <task-id> "<follow-up>" --after A01 |
| Inspect packed context evidence | ds find "<topic>" |
| Understand system boundaries | ds map |
| Recover recent local direction | ds recent |
| Coordinate umbrella repo work | ds workspace ... |
Start Here
- Reproducible FastAPI workflow examples
- Task flow
- Recover existing intent
- Command reference
- Storage model
What DevSpecs Is Not
DevSpecs is not a hosted memory layer, task board, autonomous agent, or SaaS workspace. The CLI is the canonical product. Agent adapter files, slash command recipes, and future MCP servers should wrap the same CLI primitives.