spec-driven-development

Use when a request needs concrete expected behavior before code changes — a new feature, an ambiguous goal, a change crossing several surfaces, or a choice…

Skill by arbor-ai-inc

IndexedApache-2.0

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/arbor-ai-inc-spec-driven-development

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Use when a request needs concrete expected behavior before code changes — a new feature, an ambiguous goal, a change crossing several surfaces, or a choice between plausible approaches whose tradeoffs matter. Not for typo fixes or self-contained changes whose behavior is already clear.

Use cases: agent-building

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/spec-driven-development

What's inside

Skill name: spec-driven-development
Description: Use when a request needs concrete expected behavior before code changes — a new feature, an ambiguous goal, a change crossing several surfaces, or a choice between plausible approaches whose tradeoffs matter. Not for typo fixes or self-contained changes whose behavior is already clear.
License: Apache-2.0
Instructions: 16 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

<!-- GENERATED by scripts/gen_adapters.py from skills/spec-driven-development/SKILL.md.
Do not edit: run the generator instead. The canonical workflow is
reference/spec-driven-development.md; this file only routes an agent to it. -->
Follow the canonical procedure in `.cadence/reference/spec-driven-development.md` exactly.

Restate the user-visible outcome concretely, surface assumptions before planning, and write acceptance criteria that can actually be verified.

**Scale down.** A two-line spec with acceptance criteria is the right answer when the behavior is obvious. The workflow failing by being too heavy is as real as it failing by being too light.

Load project context by kind, not by remembered path. A roadmap entry is not a built feature and a current-state doc can be stale — both failures look identical from outside, so check the code.

Pause for a human when the task is materially ambiguous, changes architecture, changes a data contract, or has wide blast radius. Use a Shape A brief (`.cadence/reference/human-brief.md`).

For a substantial spec, escalate to `.cadence/reference/spec-pipeline.md`: product intent reviewed and merged as its own PR *before* any engineering design begins.

From arbor-ai-inc/cadence, Apache-2.0.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Sep 8, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License: Apache-2.0
Repository: github.com/arbor-ai-inc/cadence
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from arbor-ai-inc

Cite this page

spec-driven-development skill. Agent Mart. https://agentmart.dev/skills/arbor-ai-inc-spec-driven-development (last updated 2026-10-24)