From dev-workflow
Run the role-isolated TDD build workflow against an approved plan file. Invokes the build-isolated-tdd Workflow (test-author != implementer != judge). Explicit-only - this is expensive and side-effecting; invoke with /build, never auto-triggered.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-workflow:buildThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Standalone build phase. Invokes the `build-isolated-tdd` Workflow on an already-approved plan
Standalone build phase. Invokes the build-isolated-tdd Workflow on an already-approved plan
file:
Workflow({
scriptPath: "${CLAUDE_PLUGIN_ROOT}/workflows/build-isolated-tdd.js",
args: { ticketId: "<TICKET>", planPath: "<PLAN-PATH>", repoPath: "<repo>" }
})
The workflow guarantees by control flow (not prompting):
repoPath and planPath are required (the workflow fails fast on missing args and never
improvises a target). ticketId is optional - omit it to run without Linear (work-log
decisions just log). LOCAL only - the Workflow tool is not available in CI.
Handle the returned status as the implement orchestrator's Phase 4 does (complete,
needs-ratification -> ratify + resumeFromRunId, or a failed gate -> surface and fix).
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub johnplummer/jp-plugins --plugin dev-workflow