Plugin Claude Code
Marketplace for the fullStack-pipeline plugin: a multi-agent TDD development pipeline for Claude Code.
Plugin Claude Code
Marketplace for the fullStack-pipeline plugin: a multi-agent TDD development pipeline for Claude Code.
Plugin Claude Code
Multi-agent TDD development pipeline: discovery, planning, red tests, implementation, review with complexity ratchet, and a local task registry. Portable across projects via a per-project profile.
Agent
Implements one area's production code until the pipeline's failing tests pass. Spawned by the pipeline orchestrator with an area name, a plan file path, and the list of tests to satisfy. Does not make architecture decisions.
Agent
Audits a completed pipeline task before commit — runs tests, enforces the cyclomatic-complexity ratchet on changed code, verifies plan delivery and contract compliance. Read-only on code; reports defects, never fixes them.
Agent
Writes failing tests (TDD red) for one area of the project before any implementation exists. Spawned by the pipeline orchestrator with an area name and a plan file path. Never writes production code.
Hook
Runs before the agent uses a tool for Write, Edit and Bash tool calls, executing tdd-guard.js and commit-gate.js via node (2 commands). From felipeJJ/fullStack-pipeline.
Hook
Runs after a tool call finishes for Bash tool calls, executing post-commit.js via node. From felipeJJ/fullStack-pipeline.
Skill Claude CodeCodex
Use when a project has no .claude/pipeline/profile.json yet and the user wants to adopt the fullStack-pipeline workflow, or when the profile needs to be reconfigured (new area, changed test commands, new thresholds).
Skill Claude CodeCodex
Use when starting any development task (feature, bugfix, refactor, hotfix) in a project that has a pipeline profile (.claude/pipeline/profile.json), before writing or editing any production code.
Skill Claude CodeCodex
Use when the user asks about pipeline tasks — listing open tasks, searching past tasks or bugfixes, reviewing a plan before execution, checking what was delivered in a task, or registering a task retroactively (hotfix done outside the pipeline).