claude

agents-tdd

Enforced test-driven development: an orchestrator drives plan -> failing tests -> independent validation -> implementation, with a fail-closed hook that blocks source writes until the tests exist, and a separate context that certifies the RED is real before GREEN may start. Use when a spec carries concrete scenarios and the tests should be the oracle rather than an afterthought — the validator exists because a test written by the same context that writes the code is not a check. Full history in CHANGELOG.md.

4 on GitHubby ForgePlanv0.6.0MITupdated 12 days agoworkflow
/

Plugin agents-tdd from marketplace ForgePlan-marketplace in ForgePlan/marketplace. Commands read from the repo's manifest — 12 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (2)

  • tdd-init

    One-time per-project setup for the enforced-TDD methodology — generates the `.forgeplan/tdd/stack.json` language binding that the `tdd-gate.sh` hook reads (test command, test/source file globs, the assertion-failure marker, lint command). Without it the gate cannot classify files and the TDD cycle c

  • tdd

    Enforced-TDD entry point. Runs the C1-C6 sub-cycle the tdd-orchestrator drives: precondition check (PRD + SPEC active with #### Scenarios) → tdd-planner (scenarios → test plan) → coder-tdd (RED: plan → failing tests) → tdd-test-validator (C4: certify tests, freeze the SPEC oracle on PASS via a norma

Subagents (4)

  • coder-tdd

    Methodology: TDD RED phase (C3 phase agent of the AD/AID-PDLC sub-cycle contract) + CRUD-R-A Profile C-coder scoped to TEST files. RFC-012 FR-2. EN: The RED test-writer. Reads the test PLAN (from tdd-planner) plus `.forgeplan/tdd/stack.json` (test_command + file globs + the per-stack red-confirm mar

  • tdd-orchestrator

    Methodology: TDD methodology master (Profile B-orchestrator) — the L2 stage-master of the TDD sub-cycle, first instance of the AD/AID-PDLC sub-cycle contract (ADR-010, contract C1-C6; RFC-012 FR-7). Peer of smith and sparc-orchestrator. Coordinates the RED→verify→GREEN flow by dispatching phase agen

  • tdd-planner

    Methodology: AD/AID-PDLC sub-cycle contract C3 (phase agent) + CRUD-R-A Profile A creator (test-PLAN artifact, language-NEUTRAL). First instance = enforced-TDD (RFC-012 FR-1 / ADR-010). EN: Language-NEUTRAL test planner — the first C3 phase agent of the enforced-TDD sub-cycle. Reads the FROZEN `####

  • tdd-test-validator

    Methodology: AD/AID-PDLC C4 independent verifier (ADR-010) + CRUD-R-A Profile B-gate (binary PASS/CONCERNS/BLOCKER verdict). Implements RFC-012 FR-3. EN: The independent verifier for the TDD sub-cycle (Profile B-gate, guardian-shaped). The DIFFERENT context that certifies the RED tests before GREEN

Hooks (1)

  • PreToolUse

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/tdd-gate.sh"

View source on GitHub forgeplan.dev

More from ForgePlan/marketplace

All 24 plugins →

Flagship workflow plugin of the ForgePlan ecosystem — the skills, templates and authoring contract the rest of the marketplace is written against: the smith methodology router (14 contexts), the agent-authoring guide every forgeplan-aware agent follows, and the gate, cleanup and insight skills that keep a pipeline honest. Use when you want the methodology itself rather than one specialist — deciding how to approach a task, gating an artifact before activation, or authoring a new agent to the house canon. Full history in CHANGELOG.md.

44 skills · 1 agent · hooks

4

Professional specialist agents: security and prompt-injection review, PII detection, architecture and staff-level system review, the pre-activation guardian gate, ADR and specification authors, research analysts and infrastructure roles. Use when a task needs a named expert rather than a generalist — an OWASP/STRIDE pass, an architectural fitness review, a decision recorded as an ADR, or the last gate before an artifact is activated. Full history in CHANGELOG.md.

30 agents

4

CANVAS design-system-to-code methodology: a coordinator walks a Pencil design through capture, audit, norm-check, vectorize and assemble, dispatching every phase and every verifier as a separate isolated context with a blocking generator-is-not-verifier gate at each handoff, plus a fail-closed hook that blocks source writes until the token contract is active. Use when a design system has to become working components in the project's own framework, with visual parity and token fidelity proven rather than asserted. Full history in CHANGELOG.md.

6 skills · 4 commands · 8 agents · hooks

4

Builds a navigable map of a project — zones, nodes and verified edges — as a `map.json`, through an eight-agent pipeline (scan -> extract -> verify -> emit -> validate) where every stage runs in a fresh isolated context and a deterministic guardian script, not an LLM, is the sole authority on whether the result can be trusted. Use when you need a structural view of a large or unfamiliar repository that a file tree cannot give, or when a project's forgeplan artifact graph should be shown alongside its code. Not a documentation generator: an edge is either sourced from the artifact graph or proven by a grep, and an unproven one is dropped rather than shipped as noise. Full history in CHANGELOG.md.

3 skills · 4 commands · 8 agents · hooks

4

fpl-hsmem

claude

Project-scoped cross-session memory for Hindsight API >=0.10.2 and <0.11.0. Use when a repository explicitly opts in via .hindsight.json; hooks default off, enrichment is operator-gated, and BankGate is client safety, not server authorization.

10 skills · 1 agent · 1 MCP server · hooks

4

Brownfield extraction pack — turns legacy code and documents into a structured forgeplan graph through a discover agent and twelve extraction skills (ubiquitous language, use cases, invariants, causal links, scenarios, knowledge-graph curation, reproducibility). Use when taking over an undocumented codebase and the first problem is not what to build but what is already there and why it is that way. Full history in CHANGELOG.md.

12 skills

4

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.

5 commands

HKUDS/CLI-Anything 58,665

Maintain agents-tdd?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins24 plugins