Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/aleksbuss/orchestra/spec-driven-developmentnpx skills add aleksbuss/orchestra --skill spec-driven-developmentgit clone --depth 1 https://github.com/aleksbuss/orchestraWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/aleksbuss/orchestra/spec-driven-development)<a href="https://agentmods.dev/skills/aleksbuss/orchestra/spec-driven-development"><img src="https://agentmods.dev/badge/skills/aleksbuss/orchestra/spec-driven-development.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00043 | $0.01810 |
| Opus 5 | $0.00022 | $0.00905 |
| Sonnet 5 | $0.00009 | $0.00362 |
| Haiku 4.5 | $0.00004 | $0.00181 |
Grade A, and why
spec-driven-development scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
94% identical to as-spec-driven-development — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Development
Overview
Write a structured specification before writing any code. The spec is the shared source of truth between you and the human engineer — it defines what we're building, why, and how we'll know it's done. Code without a spec is guessing.
When to Use
- Starting a new project or feature
- Requirements are ambiguous or incomplete
- The change touches multiple files or modules
- You're about to make an architectural decision
- The task would take more than 30 minutes to implement
When NOT to use: Single-line fixes, typo corrections, or changes where requirements are unambiguous and self-contained.
The Gated Workflow
Spec-driven development has four phases. Do not advance to the next phase until the current one is validated.
SPECIFY ──→ PLAN ──→ TASKS ──→ IMPLEMENT
│ │ │ │
▼ ▼ ▼ ▼
Human Human Human Human
reviews reviews reviews reviews
Phase 1: Specify
Start with a high-level vision. Ask the human clarifying questions until requirements are concrete.
Surface assumptions immediately. Before writing any spec content, list what you're assuming:
ASSUMPTIONS I'M MAKING:
1. This is a web application (not native mobile)
2. Authentication uses session-based cookies (not JWT)
3. The database is PostgreSQL (based on existing Prisma schema)
4. We're targeting modern browsers only (no IE11)
→ Correct me now or I'll proceed with these.
Don't silently fill in ambiguous requirements. The spec's entire purpose is to surface misunderstandings before code gets written — assumptions are the most dangerous form of misunderstanding.
Write a spec document covering these six core areas:
-
Objective — What are we building and why? Who is the user? What does success look like?
-
Commands — Full executable commands with flags, not just tool names.
Build: npm run build Test: npm test -- --coverage Lint: npm run lint --fix Dev: npm run dev
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 205 lines · 43 tokens per session scan A 386c599468ca
spec-driven-development is a skill published in the GitHub repository aleksbuss/orchestra (2 stars, last pushed 6d ago), licensed MIT. It adds 43 tokens to every session and 1,810 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to as-spec-driven-development, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
comm-agent-skill
Communication specialist for the OpenClaw multi-agent system. Use this skill when the task involves: drafting or sending emails, posting to Discord or other chat platforms, scheduling calendar events, sending notifications, or any outbound communication on behalf of the user. Always drafts before sending and requires…
data-agent-skill
Data processing and analysis specialist for the OpenClaw multi-agent system. Use this skill when the task involves: parsing CSV/JSON/Excel files, data cleaning and transformation, SQL queries, statistical analysis, generating charts or visualizations, aggregating data from multiple sources, or extracting insights from…
research-agent-skill
Information gathering and research specialist for the OpenClaw multi-agent system. Use this skill when the task involves: web search, fact-checking, comparing products or technologies, summarizing articles, gathering documentation, researching errors, or producing structured reports with sources. Also use for "what is…
system-agent-skill
System administration specialist for the OpenClaw multi-agent system. Use this skill when the task involves: package installation (apt), service management (systemctl), configuration file editing, cron job scheduling, firewall rules (ufw), disk space management, log inspection (journalctl), user/group management…
vision-agent-skill
Vision-capable agent for image analysis, screenshot interpretation, OCR, and visual tasks. Uses kimi-k2.5 for its vision capabilities (text+image input, 125k context).
code-agent-skill
Software development specialist for the OpenClaw multi-agent system. Use this skill when the task involves: writing new code, debugging existing code, code review, writing tests, git operations (commit, branch, merge), refactoring, setting up projects, or any software engineering work in Python, JavaScript/TypeScript…