New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Acceptance Pipeline Feature Design

by pproenca in pproenca/dot-skills

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…

MITAuto-check passed

Install Acceptance Pipeline Feature Design

skills CLI
$ npx skills add pproenca/dot-skills --skill acceptance-pipeline-feature-design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pproenca/dot-skills acceptance-pipeline-feature-design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.experimental/acceptance-pipeline-feature-design .claude/skills/acceptance-pipeline-feature-design && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
acceptance-pipeline-feature-design
GitHub stars
215
Token cost
~1.5k tokens
SKILL.md length
610 words
Files
11 (incl. scripts, references)
Skills in repo
41
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 2 steps: Start by reading the… → Read the phase reference that matches…
  • Someone asks how would I add X to the acceptance pipeline
  • SKILL.md covers When to Apply, Prerequisite, Workflow Overview and How to Use, plus 4 more sections
  • Discusses spec-level changes to the parser

What it does

Acceptance Pipeline Feature Design is an agent skill from pproenca/dot-skills. 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…

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts and reference files (for example `gotchas.md`, `metadata.json` and `references/extension-catalog.md`).

The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.

When your agent uses it

  • Someone asks how would I add X to the acceptance pipeline
  • Discusses spec-level changes to the parser
  • Reporter components — even if they dont explicitly say feature design. Works in tandem with the acceptance-pipeline-catalog skill
  • Which provides the baseline spec reference

Example prompts

  • “how would I add X to the acceptance pipeline”
  • “t explicitly say”
  • “Use the acceptance-pipeline-feature-design skill to design new features, extensions, or modifications to Uncle Bob's Acceptance Pipeline…”
  • “/acceptance-pipeline-feature-design”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Acceptance Pipeline Feature Design loads about 1.5k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 145 tokens; SKILL.md has 610 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~145
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 610 words, ~1,494 tokens.

Download SKILL.mdSave it as .claude/skills/acceptance-pipeline-feature-design/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
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:
PhaseReferenceWhen to Read
1Survey Existing SpecAlways — first step for any feature design
2Identify Extension PointAfter survey — classify where the feature attaches
3Draft Feature SpecAfter classification — write the spec section
4Conformance DesignAfter drafting — add testable conformance items
5Impact AnalysisAfter conformance — assess compatibility
  1. Consult supporting references as needed:
ReferenceWhen to Read
Style GuideDuring Phase 3 — Uncle Bob's spec writing patterns
Extension CatalogDuring Phase 2 — ideas and complexity notes for future extensions
Show full SKILL.md (215 more words)Show less

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 PointWhat ChangesImpact Level
ParserNew Gherkin syntax acceptedMedium — affects IR and downstream
IRNew fields or objects in JSON interchangeHigh — all consumers affected
GeneratorNew output formats or generation strategiesLow — isolated to generation
RuntimeNew execution modes, hooks, dispatchMedium — affects handler contracts
HandlersNew matching strategies or contractsLow-Medium — isolated to step matching
MutatorNew mutation strategies or filtersLow — isolated to mutation mode
ReporterNew report formats or output channelsLow — isolated to reporting
PipelineNew stages or operating modesHigh — structural change
Cross-cuttingSpans multiple componentsHighest — 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.
  • 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 for failure points discovered during use.

© pproenca, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (scripts, references) in skills/.experimental/acceptance-pipeline-feature-design of pproenca/dot-skills.

  • SKILL.md
  • gotchas.md
  • metadata.json
  • references/extension-catalog.md
  • references/phase-1-survey.md
  • references/phase-2-extension-point.md
  • references/phase-3-draft-spec.md
  • references/phase-4-conformance.md
  • references/phase-5-impact-analysis.md
  • references/style-guide.md
  • scripts/README.md

Open the folder on GitHubat commit cf93c57

Compare with similar skills

Acceptance Pipeline Feature Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Acceptance Pipeline Feature Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Acceptance Pipeline Feature Design this skillpproenca/dot-skills215—~1.5kAutomated safety check: PassMIT
Uncle Bob Craftsickn33/agentic-awesome-skills47k2 repos~2.6kAutomated safety check: PassMIT
Design Systemaffaan-m/ECC276k—~698Automated safety check: PassMIT
Design Guidepaperclipai/paperclip99k1 repos~3.1kAutomated safety check: PassMIT
Design Audit Against Rams' Principlesthedotmack/claude-mem99k—~4.6kAutomated safety check: PassApache-2.0
Figma Design to Codewarpdotdev/warp65k4 repos~2.9kAutomated safety check: PassAGPL-3.0

Similar skills

  • Uncle Bob Craft

    sickn33/agentic-awesome-skills

    A skill your agent uses when performing code review, writing or refactoring code, or discussing architecture; complements clean-code and does not replace project linter/formatter.

    47k GitHub starsUsed in 2 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Design System

    affaan-m/ECC

    Generate a design system from an existing codebase or audit one for visual consistency: extract tokens (colors, typography, spacing, shadows) into design-tokens.json and CSS custom properties with…

    276k GitHub stars~698 tokensUpdated 4 days ago
    Frontend & DesignAuto-check passed

  • Design Guide

    paperclipai/paperclip

    Paperclip UI design system guide for building consistent, reusable frontend components.

    99k GitHub starsUsed in 1 repo~3.1k tokens
    Frontend & DesignAuto-check passed

  • Design Audit Against Rams' Principles

    thedotmack/claude-mem

    Audits a design against Dieter Rams' ten principles of good design, scores each with evidence, and hands off a make-plan prompt for a new, refined or redesigned outcome.

    99k GitHub stars~4.6k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Figma Design to Code

    warpdotdev/warp

    Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.

    65k GitHub starsUsed in 4 repos~2.9k tokens
    Frontend & DesignAuto-check passed

  • Design Consultation

    garrytan/gstack

    Learns about your product, studies the landscape and writes a DESIGN.md with a full design system covering type, color, layout, spacing and motion.

    136k GitHub stars~15k tokensUpdated today
    Frontend & DesignAuto-check: notes

More from pproenca/dot-skills

All 41 skills in this repo

  • Audio Voice Recovery

    pproenca/dot-skills

    Audio forensics and voice recovery guidelines for CSI-level audio analysis.

    215 GitHub stars~3.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Codemod React Pipeline

    pproenca/dot-skills

    Guided, scripted pipeline for running JSX/TSX/React codemods safely across large legacy codebases.

    215 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

  • Dev Rfc

    pproenca/dot-skills

    Create well-structured RFCs and technical proposals for software projects.

    215 GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Dx Harness

    pproenca/dot-skills

    Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.

    215 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed

  • Language Spec Author

    pproenca/dot-skills

    Turn a rough idea for a language into a complete, implementable specification — a DSL, query, config/data, template, or protocol language — by interviewing the author dimension by dimension until…

    215 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed

  • Python Pep Author

    pproenca/dot-skills

    Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python…

    215 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Acceptance Pipeline Feature Design

What does Acceptance Pipeline Feature Design do?

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…. Acceptance Pipeline Feature Design is an agent skill from pproenca/dot-skills. 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.

When should I use Acceptance Pipeline Feature Design?

Acceptance Pipeline Feature Design fits situations like: someone asks how would I add X to the acceptance pipeline; discusses spec-level changes to the parser; reporter components — even if they dont explicitly say feature design. Works in tandem with the acceptance-pipeline-catalog skill; which provides the baseline spec reference.

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`. Or copy the skill folder (skills/.experimental/acceptance-pipeline-feature-design in pproenca/dot-skills) into .claude/skills/acceptance-pipeline-feature-design in your project. Claude Code loads it when a task matches its description.

How do I install Acceptance Pipeline Feature Design in Codex?

Run `npx skills add pproenca/dot-skills --skill acceptance-pipeline-feature-design -a codex`. Or copy the skill folder (skills/.experimental/acceptance-pipeline-feature-design in pproenca/dot-skills) into .agents/skills/acceptance-pipeline-feature-design in your project. Codex loads it when a task matches its description.

Can I use Acceptance Pipeline Feature Design in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pproenca/dot-skills --skill acceptance-pipeline-feature-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/acceptance-pipeline-feature-design, .gemini/skills/acceptance-pipeline-feature-design, .github/skills/acceptance-pipeline-feature-design and .opencode/skills/acceptance-pipeline-feature-design in your project.

What does Acceptance Pipeline Feature Design need to run?

SKILL.md names no scripts, command-line tools or credentials: Acceptance Pipeline Feature Design is instructions for the agent only.

Does Acceptance Pipeline Feature Design access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Acceptance Pipeline Feature Design safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Acceptance Pipeline Feature Design use?

Acceptance Pipeline Feature Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Acceptance Pipeline Feature Design use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to Acceptance Pipeline Feature Design?

Skills that share tags, products or a category with Acceptance Pipeline Feature Design: Uncle Bob Craft (sickn33/agentic-awesome-skills, 47k stars), Design System (affaan-m/ECC, 276k stars), Design Guide (paperclipai/paperclip, 99k stars) and Design Audit Against Rams' Principles (thedotmack/claude-mem, 99k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Acceptance Pipeline Feature Design?

pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 215 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on August 15, 2026.

Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.