Execute one TDD plan slice under a mandatory QA gate.
npx skills add https://github.com/pollockjj/grader-in-the-loop --skill tdd-slice-pollockjj
Please help me install this Agent Skill. Skill: tdd-slice Source: https://github.com/pollockjj/grader-in-the-loop/tree/main/.claude/skills/tdd-slice Command: npx skills add https://github.com/pollockjj/grader-in-the-loop --skill tdd-slice-pollockjj
It enforces disciplined, evidence-based slicing of a multi-slice plan by executing one slice at a time under a strict QA gate, preventing self-review and skipping phases.
Start the slice by issuing a command like 'start slice 1' after ensuring a PLAN_*.md exists and a tracking issue is open.
High-intent search queries and answers about installing and using this skill.
To enforce strict QA gating during test-driven development, you execute a single plan slice at a time and require an explicit external QA-certified PASS verdict before progressing. This prevents self-review and stops phases from being skipped.
A TDD slice is a single executable portion of a larger multi-slice plan. It requires artifact-backed verification and an external adversarial QA gate to validate the work before moving to the next slice.
To start a TDD slice, you need a tracked plan file like PLAN_*.md and an open tracking issue. These prerequisites ensure collaborative software-delivery workflows have artifact-backed validation before execution begins.
You prevent skipping phases in automated TDD workflows by applying a mandatory adversarial QA gate. This gate prohibits advancing to the next slice without explicit, artifact-backed QA-certified approval.
Yes, you can use TDD slicing for collaborative software delivery. It supports workflows requiring plan and issue tracking by enforcing disciplined, evidence-based slicing with external QA validation.
pollockjjGenerate a multi-slice GitHub issue plan with acceptance criteria.
NNPopovDetermine the next spec workflow command for a Flutter feature slice.
dachentOrchestrate multi-phase planning with proceed gates and adversarial review.
michaelalberAutomates the RED-GREEN-REFACTOR cycle for autonomous code development with strict TDD guardrails.
