exact-coding-tcr
Test-Driven Development with a complete up-front test list, one-behavior Red-Green-Refactor cycles, Test-Commit-Revert discipline, and configurable human checkpoints. Invoke when the user explicitly a
SKILL.mdexperiments/workflows/exact-coding/sol/exact-tcr-v1.1-srp-pi/.pi/skills/exact-coding-tcr/SKILL.md
GitHubEXACT Coding TCR
Run one shared workflow: create the complete test list once, then implement one behavior at a time using TCRDD. Every RED, GREEN, and REFACTOR phase is verified and either committed or reverted.
Preparation
- Read
.pi/skills/test-list/SKILL.md. - Read
.pi/skills/tcrdd/SKILL.md. - Read
.pi/skills/exact-coding-tcr/human-in-the-loop.md. - Read the complete specification.
- Determine the project's language and test framework. If
.pi/skills/exact-coding-tcr/stacks/contains a matching profile, read it before changing code. - Determine the project's inactive-test mechanism, full-suite command, and applicable quality gates from the profile and repository.
- Require a clean Git working tree before creating the test list.
Sequence
Create the complete ordered test list with every future behavior inactive.
Stage the test list, run the full suite, and commit it only if the suite passes:
git add -A <full-test-suite-command> git commit -m "[TEST LIST] <feature>"If the suite fails, discard the test-list change with
git reset --hard HEAD.For exactly one behavior at a time, follow
.pi/skills/tcrdd/SKILL.md:- activate exactly one behavior and reach the intended behavioral RED,
- commit the verified RED or revert it,
- apply the Red checkpoint,
- make the smallest production change and commit the verified GREEN or revert it,
- apply the Green checkpoint,
- review production and test code under the Four Rules of Simple Design,
- apply each useful refactoring as its own commit-or-revert step,
- apply the Refactor checkpoint.
Continue until every listed behavior is executable and the full suite and all applicable quality gates from the active stack profile pass.
Apply the Task-End checkpoint.
A test already satisfied by an earlier generalization is legitimate evidence. Do not manufacture a failure or production change. Activate that test, run the full suite, and commit the passing test as [GREEN] <already-satisfied behavior>.
Human-in-the-loop
.pi/skills/exact-coding-tcr/human-in-the-loop.md is the single source of truth for checkpoints. This lab profile selects its autonomous level because the harness runs unattended.
At each checkpoint, wait for explicit approval when the configured autonomy level requires it. Do not stage, test, commit, or revert the next phase while waiting.
Completion
The feature is complete only when every listed behavior has an executable test, all tests and applicable quality gates pass, the Four Rules review is complete, and the working tree is clean.