diagnose
Turn a bug symptom into a fix with a regression test that locks it down. If the user opens vague ("there's a bug", "/diagnose"),…
@eduwxyzInstall SkillDevelopment
Skill
/feature
Kick off the full feature workflow — interview-to-spec, optional spec-approach, tdd, verify, then review — when starting a new feature from scratch. Thin orchestrator: confirms intent in one sentence, then hands off to the first stage and lets each downstream skill activate on
Claude Code
$ npx -y skills add eduwxyz/my-awesome-skills --skill feature --agent claude-code
Codex
$ npx skills add eduwxyz/my-awesome-skills --skill feature -a codex -y
Cursor
$ npx skills add eduwxyz/my-awesome-skills --skill feature -a cursor -y
Gemini CLI
$ npx skills add eduwxyz/my-awesome-skills --skill feature -a gemini-cli -y
GitHub Copilot
$ npx skills add eduwxyz/my-awesome-skills --skill feature -a github-copilot -y
OpenCode
$ npx skills add eduwxyz/my-awesome-skills --skill feature -a opencode -y
Windsurf
$ npx skills add eduwxyz/my-awesome-skills --skill feature -a windsurf -y
SKILL.md
feature.SKILL.mdname: feature
description: Kick off the full feature workflow — interview-to-spec, optional spec-approach, tdd, verify, then review — when starting a new feature from scratch. Thin orchestrator: confirms intent in one sentence, then hands off to the first stage and lets each downstream skill activate on its own. Trigger when the user says "new feature", "let's build a feature", "start a feature", "build feature X end-to-end", "kick off a feature", "/feature".
Feature
The orchestrated path for building a new feature, from idea to PR-ready. This skill is a thin dispatcher — it confirms intent and hands off. Each downstream skill activates on its own.
When to use this
You want the full SDD pipeline in order without having to remember each step.
When NOT to use this
- **Bug fix.** Use `diagnose` instead.
- **Trivial change** that doesn't need a spec (one-line config, doc tweak). Edit directly.
- **Already partway through a workflow.** Resume at the relevant stage by invoking the matching skill (`interview-to-spec`, `spec-approach`, `tdd`, `verify`).
The pipeline
You will pass through these stages in order:
1. **`interview-to-spec`** — hand off. The skill conducts the interview and writes `spec/<slug>.md` (Goal, Behaviors, Acceptance criteria, Out of scope, Edge cases).
2. **`spec-approach`** *(optional)* — when the spec is written, judge whether the HOW is non-trivial:
- Multiple modules touched?
- Multiple viable approaches?
- Architectural decision required?
- Schema or API changes?
If yes, invoke `spec-approach` to append `## Approach` to the spec. If no, skip and move on.
3. **`tdd`** — hand off. Red-green-refactor against the spec's Behaviors + Acceptance criteria. The skill itself ensures `.agents/tdd/test-command.txt` is configured on first run, and its Stop hook will gate on green tests + a pass through `simplify`.
4. **`verify`** — hand off. Maps every AC to a green test. If gaps exist, the skill auto-iterates with `tdd` until clean. Will not return until the verdict is `Ready`.
5. **`review`** *(built-in)* — when verify reports `Ready`, hand off for code review. Then open the PR.
How handoff works
This skill ends as soon as you invoke `interview-to-spec`. It does not stay active across the pipeline. Each downstream skill activates from its own trigger phrasing as the conversation progresses.
If you stop the session midway and resume later, invoke the next stage's skill directly — do not re-invoke `feature`.
What to do first
Confirm the user's intent in **one sentence** ("Kicking off the feature workflow for `<short-description>`."), then immediately invoke `interview-to-spec`. Do not attempt the interview yourself — that is `interview-to-spec`'s job.
Read more
name: feature description: Kick off the full feature workflow — interview-to-spec, optional spec-approach, tdd, verify, then review — when starting a new feature from scratch. Thin orchestrator: confirms intent in one sentence, then hands off to the first stage and lets each downstream skill activate on its own. Trigger when the user says "new feature", "let's build a feature", "start a feature", "build feature X end-to-end", "kick off a feature", "/feature".
Feature
The orchestrated path for building a new feature, from idea to PR-ready. This skill is a thin dispatcher — it confirms intent and hands off. Each downstream skill activates on its own.
When to use this
You want the full SDD pipeline in order without having to remember each step.
When NOT to use this
- **Bug fix.** Use `diagnose` instead.
- **Trivial change** that doesn't need a spec (one-line config, doc tweak). Edit directly.
- **Already partway through a workflow.** Resume at the relevant stage by invoking the matching skill (`interview-to-spec`, `spec-approach`, `tdd`, `verify`).
The pipeline
You will pass through these stages in order:
1. **`interview-to-spec`** — hand off. The skill conducts the interview and writes `spec/<slug>.md` (Goal, Behaviors, Acceptance criteria, Out of scope, Edge cases).
2. **`spec-approach`** *(optional)* — when the spec is written, judge whether the HOW is non-trivial:
- Multiple modules touched?
- Multiple viable approaches?
- Architectural decision required?
- Schema or API changes?
If yes, invoke `spec-approach` to append `## Approach` to the spec. If no, skip and move on.
3. **`tdd`** — hand off. Red-green-refactor against the spec's Behaviors + Acceptance criteria. The skill itself ensures `.agents/tdd/test-command.txt` is configured on first run, and its Stop hook will gate on green tests + a pass through `simplify`.
4. **`verify`** — hand off. Maps every AC to a green test. If gaps exist, the skill auto-iterates with `tdd` until clean. Will not return until the verdict is `Ready`.
5. **`review`** *(built-in)* — when verify reports `Ready`, hand off for code review. Then open the PR.
How handoff works
This skill ends as soon as you invoke `interview-to-spec`. It does not stay active across the pipeline. Each downstream skill activates from its own trigger phrasing as the conversation progresses.
If you stop the session midway and resume later, invoke the next stage's skill directly — do not re-invoke `feature`.
What to do first
Confirm the user's intent in **one sentence** ("Kicking off the feature workflow for `<short-description>`."), then immediately invoke `interview-to-spec`. Do not attempt the interview yourself — that is `interview-to-spec`'s job.
Stats
15
Stars
1
Forks
Maintained
Maintenance
Shell
Language
Last commit
Created
Ships withsdd-pipeline
A spec-driven development pipeline for Claude Code and Codex CLI. Refine the spec before you code, let TDD enforce it, verify nothing slipped, then review.
156 skills
Stars on GitHub
Momentum
- stars in total
- 15
Other skills on sdd-pipeline.
@eduwxyzInstall Skillinterview-to-spec
Conduct a focused interview to draft a spec.md for an upcoming task (the input step of SDD — spec-driven development). Walks…
@eduwxyzInstall Skillspec-approach
Add a refined `## Approach` section to an existing feature spec.md before TDD executes it. Reads the spec, explores the codebase…
@eduwxyzInstall Skilltdd
Drives feature work and bug fixes through a tight failing-test-first loop. Trigger when implementing, fixing, or refactoring…
@eduwxyzInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about feature.
- Which coding agents can use feature?
- feature installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.