Spec Driven Workflow

Run development from an executable specification with traceable requirement IDs and merge-time coverage gates. Use when starting a greenfield feature, reviving a stale spec, or gating merges on requirement coverage.

1,157 stars 217 forksProductivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add borghei/Claude-Skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add borghei/Claude-Skills --skill spec-driven-workflow
Manual install
git clone --depth 1 https://github.com/borghei/Claude-Skills.git /tmp/Claude-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skills/engineering/spec-driven-workflow ~/.claude/skills/spec-driven-workflow

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Spec-Driven Workflow

Development where the specification is the source of truth and the code is its
implementation, rather than a document that was true at kickoff and fiction by week
three. The mechanism is unglamorous: every normative statement gets a stable ID, every
ID appears in a test, and the merge gate fails when the two drift apart. Without that
mechanical link a spec is a memo, and memos do not survive contact with a sprint.

## When to use this skill

- **Starting a greenfield feature** where the interface is contested and the cost of building the wrong thing is high
- **Reviving a stale spec** that no longer matches shipped behaviour and needs reconciling before the next change
- **Gating merges on coverage** so a PR that implements two of five committed requirements cannot silently land
- **Auditing what actually shipped** ahead of a stakeholder review or a compliance obligation
- **Handing a feature to another team** who need the intent, not just the code
- **Generating an implementation** from a spec — which only works if the spec is precise enough that two engineers would build the same thing
- **Capturing a spec from a conversation** — a chat thread, design call or agent session where the decisions already exist but nobody wrote them down
- **Implementing ticket by ticket** from an approved spec, test-first, with a review and a commit per ticket

## Inputs the skill expects
Read the full skill on GitHub

Details

Skill name
spec-driven-workflow
Path
engineering/spec-driven-workflow/SKILL.md
Repo updated
8 November 2026

FAQ

What does the Spec Driven Workflow skill do?

Run development from an executable specification with traceable requirement IDs and merge-time coverage gates. Use when starting a greenfield feature, reviving a stale spec, or gating merges on requirement coverage.

How do I install the Spec Driven Workflow skill?

Claude Code plugin: /plugin marketplace add borghei/Claude-Skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Spec Driven Workflow popular?

It lives in borghei/Claude-Skills, which has 1,157 GitHub stars and 217 forks, and is included in 1 curated skill list.

Related skills

Cto Advisor

1.2k

borghei/Claude-Skills

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, or making architecture decisions.

Software DevelopmentIn 1 list217

Customer Success Manager

1.2k

borghei/Claude-Skills

Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success

Marketing, Sales & BusinessIn 1 list217

Financial Analyst

1.2k

borghei/Claude-Skills

Performs financial ratio analysis, DCF valuation, budget variance analysis, and rolling forecast construction for strategic decision-making

Finance & CryptoIn 1 list217

Summarize Meeting

1.2k

borghei/Claude-Skills

Turns meeting notes or transcripts into a summary of decisions, owned and dated action items, and open questions. Use when writing up a meeting, a recap email or a decision log; for patterns across a series use meeting-analyzer.

Productivity & NotesIn 1 list217

Scrum Master

1.2k

borghei/Claude-Skills

Scores sprint health, forecasts velocity with Monte Carlo, analyses retros and plans capacity from sprint data. Use when facilitating sprint planning, diagnosing a velocity drop, or checking whether retro actions land.

Productivity & NotesIn 1 list217

Team Communications

1.2k

borghei/Claude-Skills

Design a delivery team's communication system — channel routing, meeting-load reduction, status structure, escalation SLAs, timezone norms. Use when the calendar is full, updates go unread, or blockers surface late.

Productivity & NotesIn 1 list217

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.