Spec-first
Development methodology
A project workspace where the problem, specification, task queue and working memory remain connected as agents execute.
Published workspace template
Write down what the work is for.
Discovery begins with the product problem. Agent identity, operator context and tool boundaries surround that intent so the workspace has a clear purpose before tasks begin.
- Input
- The problem and the operator’s context
- Output
- A product definition
- Mechanism
- /discovery → product/problem.md
- Technology
- problem.md · IDENTITY.md · USER.md
Give a feature an explicit contract.
Features enter the feature map and acquire written specifications. The spec records the intended result and becomes a shared reference for implementation.
- Input
- A defined product problem and feature
- Output
- A specification and queued work
- Mechanism
- /new-feature → spec → task_queue.md
- Technology
- Feature map · specifications · task queue
Let the queue drive the work.
The agent works from the task queue and workspace instructions. Tools, peer routing and working memory provide the context needed to keep execution attached to the specification.
- Input
- A task and its specification
- Output
- Implementation and recorded working state
- Mechanism
- Task queue → /loop → implementation
- Technology
- TOOLS.md · AGENTS.md · memory
Make the finished work teach the next build.
The success workflow reconciles implementation and documentation. Living specs move from plans to production references as the work is completed.
- Input
- The implemented change
- Output
- Updated reference material and the next task
- Mechanism
- Implementation → /success → reference
- Technology
- Living specs · /success · /loop
Recorded evidence
agent-spec-first · README + Git history
- 18 Mar 2026 · OpenClaw + spec-first workspace template · Committed · eb08253
- 18 Mar 2026 · Project agent role clarified · Committed · 4d62385
Related work