Agent skill · product strategy · pproenca
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.
Why this skill is useful
Provides a structured workflow for designing features that extend the Acceptance Pipeline Specification, which includes domain-specific knowledge and procedural guidelines not commonly known.
What it needs
Requires acceptance-pipeline-catalog account access. About 3k tokens when loaded. Last updated 2026-07-24. 192 stars on the source repository.
What this skill does
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. 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 it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pproenca/acceptance-pipeline-feature-design