Generate a multi-slice GitHub issue plan with acceptance criteria.
npx skills add https://github.com/pollockjj/grader-in-the-loop --skill tdd-plan-pollockjj
Please help me install this Agent Skill. Skill: tdd-plan Source: https://github.com/pollockjj/grader-in-the-loop/tree/main/.claude/skills/tdd-plan Command: npx skills add https://github.com/pollockjj/grader-in-the-loop --skill tdd-plan-pollockjj
This Skill formalizes multi-step planning and governance for complex tasks, converting intended work into a verifiable GitHub issue blueprint before any implementation begins.
Engage the tdd-plan skill when a task requires multi-step coordination across files or systems or when the scope is unclear and root-cause analysis is required.
High-intent search queries and answers about installing and using this skill.
Multi-slice work planning creates a structured GitHub issue blueprint defining objective-focused slices, acceptance criteria, and evidence requirements before any implementation begins. This formalizes governance by locking scope and enforcing artifacts for deterministic evaluation to ensure reproducible execution.
Plan-first governance is a formalization process converting intended work into a verifiable blueprint with locked acceptance criteria and evidence requirements before coding starts. It coordinates across files and systems, ensuring no implementation occurs until QA gates pass to reduce scope creep and risk.
You need to formalize acceptance criteria when a task requires multi-step coordination across files or systems, or when scope is unclear requiring root-cause analysis. Locking criteria prior to work ensures slices remain verifiable, executable, and reproducible by downstream QA automation processes.
Yes, you can coordinate TDD execution across multiple files by generating a multi-slice plan that defines objective-focused slices and verifiable acceptance criteria. This structured blueprint ensures slices are executable by the tdd-slice skill and verifiable by the qa-skill for deterministic evaluation.
The best way to enforce QA gates is by generating a structured plan that locks acceptance criteria and requires evidence artifacts before allowing implementation. This plan-first governance approach coordinates across files and systems, ensuring no code is written until deterministic evaluation passes.
s0lci700Execute one phase of a multi-phase plan per session with structured handoff.
rupertsworldAutomate test-first development and plan-driven implementation using TDD.
moltbook-experimentsExecute deterministic compute jobs from Git commit snapshots in a public log.
wtthorntonCreates user stories, epics, and tasks with Fibonacci point estimates.
