Agent skill

Atdd

by swingerman in swingerman/engineer

A skill your agent uses to write a feature's acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline.

MITAuto-check passedAgent Workflows

Install Atdd

skills CLI
$ npx skills add swingerman/engineer --skill atdd -a claude-code

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

GitHub CLI
$ gh skill install swingerman/engineer atdd --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/swingerman/engineer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineer/skills/atdd .claude/skills/atdd && 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
atdd
GitHub stars
154
Token cost
~1.2k tokens
SKILL.md length
551 words
Files
1
Skills in repo
27
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses to write a feature's acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline.

  • Works in 4 steps: Entry gate → Run the acceptance workflow → Handoff → …
  • Write a features acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline
  • SKILL.md covers When to use, Workflow and References
  • Calls python3

What it does

Atdd is an agent skill from swingerman/engineer. Use to write a feature's acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline. The engineer-namespace entry point into the atdd plugin's acceptance workflow. Triggers — "/engineer.atdd", "write the spec", "Checkpoint 3", "formalize the ACs as specs", "generate the test pipeline".

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Disciplined Agentic Engineering — a methodology kit for Claude Code: acceptance-test-first specs, explicit checkpoints, and autonomy you can actually leave running. The engineer… The licence is MIT.

When your agent uses it

  • Write a features acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline
  • — /engineer.atdd
  • Formalize the ACs as specs
  • Generate the test pipeline

Example prompts

  • “s acceptance workflow. Triggers —”
  • “write the spec”
  • “Checkpoint 3”
  • “/atdd”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Entry gate
  2. Run the acceptance workflow
  3. Handoff
  4. Dispatch the next checkpoint

What it can do on your machine

Read from SKILL.md and the folder at commit 32947eb. 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

    Shell commands in SKILL.md call:

    • python3

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

  • Network

    Links to these hosts (documentation or services it may open):

    • notion.so

    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

Atdd loads about 1.2k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 551 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~79
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from swingerman/engineer at commit 32947eb, republished under its MIT licence (© swingerman). 551 words, ~1,155 tokens.

Download SKILL.mdSave it as .claude/skills/atdd/SKILL.md (or your agent's skills folder).
name
atdd
description
Use to write a feature's acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline. The engineer-namespace entry point into the atdd plugin's acceptance workflow. Triggers — "/engineer.atdd", "write the spec", "Checkpoint 3", "formalize the ACs as specs", "generate the test pipeline".

atdd

The DAE pipeline's Checkpoint 3 (Spec) entry point. AC discovery (Checkpoint 2, discover-acs) decided what behaviors must work; this step formalizes them as a standard-Gherkin spec.md and generates the project-specific test pipeline.

This skill is a thin bridge: the acceptance workflow itself lives in the atdd plugin (atdd:atdd). engineer.atdd wraps it with the DAE checkpoint contract — the entry gate in, the handoff out — so the acceptance pipeline is a first-class checkpoint of the engineer pipeline rather than a separate detour.

Requires the atdd plugin. If it is not installed, tell the user to run /plugin install atdd@disciplined-agentic-engineering and stop.

When to use

Checkpoint 3, after discover-acs (Checkpoint 2) has produced an approved acs.md. Produces spec.md + the feature's .build/ pipeline.

Not for: AC discovery (discover-acs); planning (plan); using the acceptance workflow outside a DAE feature folder (invoke atdd:atdd directly).

Workflow

Step 0 — Entry gate

Verify the prior checkpoint is complete: run ${CLAUDE_PLUGIN_ROOT}/scripts/dae_handoff.py <feature-dir> --through 2. On a non-zero exit, stop and surface the gap to the human.

Verify branch hygiene: run ${CLAUDE_PLUGIN_ROOT}/scripts/dae_branch.py <feature-dir>. On a non-zero exit, stop and surface the message to the human — switch branches and re-invoke. The check honors the git.manual: true manifest opt-out.

After the gate passes, show the pipeline breadcrumb: run ${CLAUDE_PLUGIN_ROOT}/scripts/dae_progress.py <feature-dir> and present its output to the human — it shows where this checkpoint sits in the DAE pipeline. The breadcrumb is advisory: a non-zero exit or a missing progress.md never blocks the skill. Then create one TodoWrite todo per workflow step below. See ${CLAUDE_PLUGIN_ROOT}/references/progress-indicator.md.

Show full SKILL.md (300 more words)Show less
Step 1 — Run the acceptance workflow

Invoke the atdd:atdd skill, scoped to this feature: write the feature's spec.md in standard Gherkin from acs.md, then generate the test pipeline (the pipeline-builder agent + the portable dae_gherkin.py parser). Present spec.md to the human for approval — specs are the human's contract.

If the harness seeds a DB and manifest.acceptance.fixture_parity.check is set, require the generated pipeline to run that check as a pre-run gate (fail loud on fixture↔schema drift, before the acceptance tests), so drift can't fake a RED cliff or mask a real defect. See ${CLAUDE_PLUGIN_ROOT}/references/fixture-parity.md — the robust fix (boot the test DB from canonical schema + migrations) belongs in the pipeline-builder, which this skill bridges to.

If the generated CI runner needs dae_gherkin.py (it lives only in the version-pinned plugin cache and is absent in CI), vendor it into the project with a drift check rather than a bare copy that silently goes stale on a plugin bump: record python3 ${CLAUDE_PLUGIN_ROOT}/scripts/dae_gherkin.py --fingerprint at vendor time and have CI assert the vendored copy's --fingerprint still matches it, failing loud on drift. (The robust fix — a pip-installable parser — also lives in the pipeline-builder.)

Step 2 — Handoff

Emit a summary per ${CLAUDE_PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: 3; the exit_criteria block asserts Checkpoint 3's criteria (Foundation Design Section 8) — spec.md parses to a valid IR, every AC maps to ≥1 scenario, spec-check passes — each with verified_by and evidence. recommended_next: "/engineer.plan".

Step 3 — Dispatch the next checkpoint

spec.md is the human's contract and gets human approval in Step 1. Once approved, auto-dispatch /engineer.plan at autonomy medium/high; confirm-then-dispatch at low. See ${CLAUDE_PLUGIN_ROOT}/references/handoff-dispatch.md. Don't bounce the mechanical "ready to plan?" question back to the human after they already approved the spec.

References

  • ${CLAUDE_PLUGIN_ROOT}/references/handoff-dispatch.md — when to dispatch vs stop
  • Foundation Design — the Checkpoint Exit Contract (Section 8)
  • atdd:atdd — the acceptance workflow this skill bridges to

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

Files

Just SKILL.md in engineer/skills/atdd of swingerman/engineer.

Open the folder on GitHubat commit 32947eb

Compare with similar skills

Atdd 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.

Atdd compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Atdd this skillswingerman/engineer154—~1.2kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k62 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official37k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k34 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official37k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 62 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    37k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 34 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    37k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    794 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from swingerman/engineer

All 27 skills in this repo
  • Crap Analyzer

    swingerman/engineer

    A skill your agent uses to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP (complexity × untested) on changed methods.

    154 GitHub stars~1.2k tokensUpdated 14 days ago
    Auto-check passed
  • Atdd Mutate

    swingerman/engineer

    A skill your agent uses to add a third validation layer to the ATDD workflow — after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies the tests actually catch bugs.

    154 GitHub stars~2.7k tokensUpdated 14 days ago
    Auto-check passed
  • Fix

    swingerman/engineer

    A skill your agent uses to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end.

    154 GitHub stars~3k tokensUpdated 14 days ago
    Auto-check passed
  • Atdd

    swingerman/engineer

    A skill your agent uses to drive feature work through the Acceptance Test Driven Development workflow — Given/When/Then specs before code, a project-specific test pipeline, and two parallel test…

    154 GitHub stars~2.8k tokensUpdated 14 days ago
    Auto-check passed
  • Harden

    swingerman/engineer

    Use after a feature passes Light Verify (CP7), to prove the tests actually catch bugs and, where the code warrants it, to formally check its invariants — Checkpoint 8.

    154 GitHub stars~1.8k tokensUpdated 14 days ago
    Auto-check passed
  • Next

    swingerman/engineer

    Use at the start of a work session, or any time the question is "what should I pick up now" across the whole project.

    154 GitHub stars~3k tokensUpdated 14 days ago
    Auto-check passed

Categories

Questions about Atdd

What does Atdd do?

A skill your agent uses to write a feature's acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline. Atdd is an agent skill from swingerman/engineer. Use to write a feature's acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline.

When should I use Atdd?

Atdd fits situations like: write a features acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline; — /engineer.atdd; formalize the ACs as specs; generate the test pipeline.

How do I install Atdd in Claude Code?

Run `npx skills add swingerman/engineer --skill atdd -a claude-code`. Or copy the skill folder (engineer/skills/atdd in swingerman/engineer) into .claude/skills/atdd in your project. Claude Code loads it when a task matches its description.

How do I install Atdd in Codex?

Run `npx skills add swingerman/engineer --skill atdd -a codex`. Or copy the skill folder (engineer/skills/atdd in swingerman/engineer) into .agents/skills/atdd in your project. Codex loads it when a task matches its description.

Can I use Atdd 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 swingerman/engineer --skill atdd -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/atdd, .gemini/skills/atdd, .github/skills/atdd and .opencode/skills/atdd in your project.

What does Atdd need to run?

Going by SKILL.md and its folder, Atdd needs the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Atdd access the network?

SKILL.md names 1 domain. As links in the text: notion.so. This is read from the text; nothing was executed.

Is Atdd 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. Review the folder before installing.

What licence does Atdd use?

Atdd 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 Atdd use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Atdd?

Skills that share tags, products or a category with Atdd: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 37k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Atdd?

swingerman (a GitHub user) maintains it in swingerman/engineer, which has 154 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 23, 2026.

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