# Guide Spec-Driven Implementation

Feature work often drifts beyond approved acceptance criteria. This skill guides Claude, Codex, and Claude Code through AC review, TDD, scope checks, and completion review.

## Install

```bash
npx skillstore add clionegohan/spec-workflow
```

## Metadata

- Status: approved
- Slug: clionegohan-spec-workflow
- Skillstore revision: r1
- Version status: missing
- Tree hash: 4d7c1a3c976cd1bba01b06918ee81618540fa2fade7140e82cc86daf61cd0c09
- Author: Clionegohan
- GitHub username: Clionegohan
- License: MIT
- Repository: https://github.com/Clionegohan/YoRuH-Resonance-Archive-C4-Sync-/tree/main/atdd-sdd/.claude/skills/spec-workflow
- Ref: 26421118b848d9f1efc0aa169d8a7a9e7e0a877e
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/clionegohan-spec-workflow
- Manifest: https://skillstore.pages.dev/api/skills/clionegohan-spec-workflow/manifest

## Capabilities

- Prompts for acceptance criteria confirmation before implementation starts.
- Maps EARS-style acceptance criteria into test planning steps.
- Guides Red, Green, and Refactor phases during implementation.
- Identifies requests that are outside the current subtask scope.
- Supports branch and pull request handoff after user confirmation.

## Use Cases

- Implement Approved Subtasks: Use the workflow to read a subtask, confirm acceptance criteria, and implement only the approved scope.
- Keep Delivery Aligned: Use acceptance criteria checks to prevent extra features and confirm completion before status updates.
- Structure AI Pair Programming: Guide Claude, Codex, or Claude Code through a repeatable TDD cycle for feature work.

## Prompt Templates

### Start a Subtask

```
Implement subtask 001-01-01. Read the matching spec, summarize the acceptance criteria, and ask for approval before coding.
```

### Plan Tests from Criteria

```
Use the spec workflow for this story. Derive test cases from each acceptance criterion before making implementation changes.
```

### Handle Scope Change

```
Check whether this requested change is inside the current subtask acceptance criteria. If it is outside scope, propose the next step.
```

### Complete Story Handoff

```
After all tests pass, check every acceptance criterion, update the subtask status, and prepare the branch and pull request handoff.
```

## Limitations

- Requires existing subtask specifications in the expected specs folder structure.
- Does not create upstream epics, stories, or acceptance criteria.
- Depends on project test tools that already exist in the workspace.
- Branch and pull request steps depend on separate workflow skills.

## Best Practices

- Keep each prompt tied to one subtask and one approved acceptance criteria set.
- Review the proposed tests before allowing implementation changes.
- Require explicit approval before branch, status, or pull request updates.

## Anti Patterns

- Do not use the skill to invent acceptance criteria without upstream specification work.
- Do not bundle unrelated feature requests into one subtask implementation.
- Do not skip the Red phase when tests are available for the project.

## Security Audit

- Audited at: 2026-07-09T14:17:46.218\+00:00
- Summary: Most backtick-related findings are false positives caused by Markdown fences, inline formatting, and TypeScript examples. The filesystem findings are confirmed because SKILL.md references hidden .ai files through parent-directory traversal at lines 306-307.

## Stats

- Views: 224
- Downloads: 10
- Favorites: 0
- Popularity score: 0