acceptance-pipeline-feature-design — Claude Code skill
The acceptance-pipeline-feature-design skill helps design Acceptance Pipeline extensions, covering Gherkin syntax, JSON IR fields, pipeline stages, mutation strategies, and reports.
MIT 141 installs ★ 227 updated 2026-08-15
npx skills add pproenca/dot-skills --skill acceptance-pipeline-feature-design -a claude-codeWhat acceptance-pipeline-feature-design does
The skill guides an agent through five ordered phases: reviewing the current specification, classifying the extension point, drafting requirements, defining conformance checks, and assessing impact. Its deliverables are a specification section, numbered testable items, and a component-by-component impact table.
It covers the parser, IR, generator, runtime, handlers, mutator, reporter, and pipeline. Cross-cutting changes receive their own analysis. acceptance-pipeline-catalog is required first because it supplies the baseline for 9 components, the JSON IR schema, and existing checklists. Without that catalog, the design lacks the stated reference foundation.
What it helps with
- design a new mutation strategy
- add Gherkin syntax support
- extend the JSON IR with fields
- define another report format
- assess backward compatibility
Example prompts for the agent
- Design support for Gherkin data tables in the Acceptance Pipeline.
- Add a mutation strategy and map the components it affects.
- Write a spec for a new JSON IR field with testable conformance items.
How to install acceptance-pipeline-feature-design
1Skills CLI (Vercel)
npx skills add pproenca/dot-skills --skill acceptance-pipeline-feature-design -a claude-code2Manually: put the files in place
~/.claude/skills/acceptance-pipeline-feature-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/acceptance-pipeline-feature-design/
1Skills CLI (Vercel)
npx skills add pproenca/dot-skills --skill acceptance-pipeline-feature-design -a codex2Manually: put the files in place
.agents/skills/acceptance-pipeline-feature-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pproenca/dot-skills --skill acceptance-pipeline-feature-design -a cursor2Manually: put the files in place
.cursor/skills/acceptance-pipeline-feature-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pproenca/dot-skills skills/.experimental/acceptance-pipeline-feature-design2Manually: put the files in place
.github/skills/acceptance-pipeline-feature-design/SKILL.md1Skills CLI (Vercel)
npx skills add pproenca/dot-skills --skill acceptance-pipeline-feature-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/pproenca/dot-skills --path skills/.experimental/acceptance-pipeline-feature-designManually: put the files in place
.devin/skills/acceptance-pipeline-feature-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pproenca/dot-skills --skill acceptance-pipeline-feature-design -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about acceptance-pipeline-feature-design
How do I install acceptance-pipeline-feature-design in Claude Code?
Run npx skills add pproenca/dot-skills --skill acceptance-pipeline-feature-design -a claude-code, then check ~/.claude/skills/acceptance-pipeline-feature-design/SKILL.md.
What does acceptance-pipeline-feature-design do?
It turns Acceptance Pipeline changes into a structured design with behavioral requirements, extension-point analysis, conformance checks, and compatibility impact.
What must be available before using it?
Read acceptance-pipeline-catalog first. It provides the baseline for 9 components, the JSON IR schema, and the existing conformance checklists.
Source text
SKILL.md · MIT
--- name: acceptance-pipeline-feature-design description: Designs new features, extensions, or modifications to Uncle Bob's Acceptance Pipeline Specification — new mutation strategies, Gherkin syntax support, report formats, pipeline stages, IR fields, or handler patterns. Trigger when someone asks "how would I add X to the acceptance pipeline" or discusses spec-level changes to the parser, generator, runtime, mutator, or reporter components — even if they don't explicitly say "feature design." Works in tandem with the acceptance-pipeline-catalog skill, which provides the baseline spec reference. --- # Acceptance Pipeline Feature Design Guides agents through designing new features that extend Uncle Bob's Acceptance Pipeline Specification. Produces spec-quality output — language-neutral, implementation-agnostic, with precise behavioral requirements — that matches the style and rigor of the original spec. This is a composition skill. It does not catalog what exists (that is `acceptance-pipeline-catalog`'s job). Instead, it provides a structured workflow for designing what comes next. ## When to Apply - Designing a new mutation strategy, value type, or filter mechanism for the mutator - Adding new Gherkin syntax support (data tables, tags, Rules keyword) to the parser - Extending the JSON IR with new fields or objects - Creating new report formats (HTML, JUnit XML) or output channels - Adding new pipeline stages or operating modes (parallel runs, coverage filtering) - Any spec-level change that affects multiple pipeline components (cross-cutting) ## Prerequisite Before using this skill, ensure `acceptance-pipeline-catalog` is available. That skill provides the baseline reference for the 9 required components, JSON IR schema, conformance checklist (21 items), and agent setup checklist (15 steps). This skill builds on top of that foundation. ## Workflow Overview The workflow has five phases, executed in order. Each phase builds on the output of the previous one — skipping phases produces incomplete or inconsistent designs. ``` Phase 1: Survey Existing Spec → Know what exists before proposing changes Phase 2: Identify Extension Point → Classify where the feature attaches Phase 3: Draft Feature Spec → Write the spec section in Uncle Bob's style Phase 4: Conformance Design → Add testable conformance items Phase 5: Impact Analysis → Assess backward compatibility and migration ``` **Why this order matters:** - Phase 1 prevents reinventing existing capabilities and ensures the design uses established patterns. - Phase 2 forces classification before writing — a parser extension has different constraints than a reporter extension. - Phase 3 produces the actual spec text, informed by the classification from Phase 2. - Phase 4 ensures the feature is testable from outside the implementation — if you cannot write conformance items, the spec is too vague. - Phase 5 comes last because you need the complete spec and conformance items to assess impact accurately. ## How to Use 1. Start by reading the `acceptance-pipeline-catalog` skill to understand the current spec 2. Read the phase reference that matches your current workflow step: | Phase | Reference | When to Read | |-------|-----------|-------------| | 1 | [Survey Existing Spec](references/phase-1-survey.md) | Always — first step for any feature design | | 2 | [Identify Extension Point](references/phase-2-extension-point.md) | After survey — classify where the feature attaches | | 3 | [Draft Feature Spec](references/phase-3-draft-spec.md) | After classification — write the spec section | | 4 | [Conformance Design](references/phase-4-conformance.md) | After drafting — add testable conformance items | | 5 | [Impact Analysis](references/phase-5-impact-analysis.md) | After conformance — assess compatibility | 3. Consult supporting references as needed: | Reference | When to Read | |-----------|-------------| | [Style Guide](references/style-guide.md) | During Phase 3 — Uncle Bob's spec writing patterns | | [Extension Catalog](references/extension-catalog.md) | During Phase 2 — ideas and complexity notes for future extensions | ## Extension Point Quick Reference Features attach to one or more of these 9 components. The JSON IR is the highest-impact extension point because all components consume it. | Extension Point | What Changes | Impact Level | |----------------|-------------|-------------| | Parser | New Gherkin syntax accepted | Medium — affects IR and downstream | | IR | New fields or objects in JSON interchange | **High** — all consumers affected | | Generator | New output formats or generation strategies | Low — isolated to generation | | Runtime | New execution modes, hooks, dispatch | Medium — affects handler contracts | | Handlers | New matching strategies or contracts | Low-Medium — isolated to step matching | | Mutator | New mutation strategies or filters | Low — isolated to mutation mode | | Reporter | New report formats or output channels | Low — isolated to reporting | | Pipeline | New stages or operating modes | **High** — structural change | | Cross-cutting | Spans multiple components | **Highest** — requires careful analysis | ## Output The workflow produces these artifacts: 1. **Feature spec section** — Ready to insert into the Acceptance Pipeline Specification. Written in Uncle Bob's style with purpose paragraph, behavioral requirements, data formats, and examples. 2. **Conformance items** — Numbered, testable items extending the existing 21-item checklist. 3. **Impact analysis table** — Component-by-component assessment of change type, IR effects, breaking changes, and new conformance items. ## Related Skills - `acceptance-pipeline-catalog` — Baseline reference for the complete spec (prerequisite) - `clean-code` — Uncle Bob's coding principles (useful context for style alignment) ## Gotchas See [gotchas.md](gotchas.md) for failure points discovered during use.
© pproenca · MIT · pproenca/dot-skills