Git Workflow v2.7.0

Git Workflow v2.7.0

Adds /plan-tdd ($plan-tdd in Codex): design a reviewed Test-Driven Development plan before writing code. You describe a feature or point it at a ticket; it asks for missing context, then produces the test plan for you to approve.

Highlights

• Spec-to-TDD planning: turns a plain-language description or a ticket into RED-GREEN-REFACTOR behavior cycles with concrete assertions.
• Clarifying questions: when scope, edge cases, or risk boundaries are unclear, it asks through the host's user-input mechanism instead of guessing.
• Explicit risk matrix: surfaces high-risk scenarios that specs usually miss — privilege escalation, data leakage, impersonation — and marks each as covered, partial, or not covered.
• Two artifacts: a self-contained, offline HTML brief for review plus a machine-readable plan.yaml that /tdd can implement.
• Optional RED skeletons: after you approve the plan, it can scaffold failing test stubs — identifiers derived from the stable cycle id, behavior text kept in escaped strings/comments.
• Cross-runtime: available to both Claude Code and Codex with no per-runtime setup; the skill body is host-neutral.

Use it

/plan-tdd Add role-based access to the admin settings endpoint

Answer the clarifying questions, open the generated HTML under .git-workflow/plan-tdd/<slug>/ to confirm it captures your intent, then run /tdd to implement it test-first.

See the changelog for details.