Create acceptance criteria and verification fixtures before writing implementation code.
npx skills add https://github.com/dmooney/Rundale --skill task-start-dmooney
Please help me install this Agent Skill. Skill: task-start Source: https://github.com/dmooney/Rundale/tree/main/.agents/skills/task-start Command: npx skills add https://github.com/dmooney/Rundale --skill task-start-dmooney
It prevents wasted effort by forcing teams to define acceptance criteria and a verification fixture before any implementation begins, so the final code is judged against observable signals rather than intent.
.proofs/<task-id>/ directory with an acceptance-criteria document and (for larger features) supporting design and plan artifacts.parish/testing/fixtures/play_<task-id>.txt script that makes each criterion visible in the game’s JSON output.Use the task-start skill with a kebab-case task id to produce .proofs/<task-id>/acceptance-criteria.md and parish/testing/fixtures/play_<task-id>.txt describing done, then stop for human review.
High-intent search queries and answers about installing and using this skill.
Defining acceptance criteria before coding involves creating a `.proofs/<task-id>/` bundle with an `acceptance-criteria.md` document and a verification fixture to establish observable signals for expected behavior.
A deterministic verification fixture is a `play_<task-id>.txt` script that makes each acceptance criterion visible in the game's JSON output, ensuring the harness demonstrates expected behavior.
CI readiness for game harness features requires creating a proof bundle with explicit acceptance criteria and a deterministic test fixture that produces observable in-game JSON signals before implementation begins.
Depth-first feature decomposition requires adding a design note and implementation plan under `docs/design/` and `docs/plans/` for non-trivial features, referencing affected subsystems and observable harness signals.
No, this coding workflow requires writing the test fixture and acceptance criteria first, stopping for human review before any implementation code is written to prevent wasted effort.
Defining done before writing artifacts ensures final code is judged against observable signals rather than intent, preventing wasted effort by forcing teams to establish verification fixtures before implementation begins.
zccz14Compare README goals against origin/main and generate coordinator handoff signals.
dmooneyVerify Rundale gameplay changes live by running Parish engine scripts and inspecting JSON outputs.
otto-poblyshConvert feature specifications into multi-step implementation plans with file paths and test-first tasks.
AsiaOstrichGuide teams through ATDD workflows with Given-When-Then acceptance criteria.