Individual skill
acceptance-pipeline-feature-design
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.
skills/.experimental/acceptance-pipeline-feature-design/SKILL.md
Source commit cf93c57cac89d6fc3e4194686000411567f5caf3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 221
- Repository last updated
- Aug 15, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,039 bytesgotchas.mddoc · 36 bytesmetadata.jsonasset · 672 bytesreferences/extension-catalog.mddoc · 8,714 bytesreferences/phase-1-survey.mddoc · 3,958 bytesreferences/phase-2-extension-point.mddoc · 4,926 bytesreferences/phase-3-draft-spec.mddoc · 6,834 bytesreferences/phase-4-conformance.mddoc · 5,411 bytesreferences/phase-5-impact-analysis.mddoc · 6,475 bytesreferences/style-guide.mddoc · 7,525 bytesscripts/README.mddoc · 195 bytes
Read excerpt
# 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)
