Claude Skills by KashZod

Test-driven implementation of a plan produced by /plan: loads the JSON tracker, then per chunk writes a failing test, implements until it passes, and runs a two-agent quality gate (review-impl conformance + red-team correctness). Use after /plan has produced an approved tracker. Requires a tracker whose plan_review gate passed.

Structured planning process: explores the code, decomposes a feature into independently-testable TDD chunks with a dependency graph, writes a JSON tracker, and gates the plan through an independent review-plan agent before any code is written. Use after /spec (or on its own) and before /implement, to decide HOW to build it.

Structured specification process: explores code, generates user stories with testable acceptance criteria, resolves ambiguities through interactive clarification, validates completeness, and outputs a lightweight spec. Use before /plan to clarify WHAT to build.