Phase validate
Skill yarlson/yarstack/plugins/yarstack/skills/phase-validate
Engineering workflows and standards for Codex and Claude Code: plan, implement, test, review, and deliver repository changes.
npx -y skills add yarlson/yarstack --skill phase-validateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Validate exactly one implemented phase or scoped change against its authoritative contract. Use after implementation to re-derive criterion-level conclusions from current evidence and fix only required implementation gaps.
SKILL.md
2.1 KB, as published. Nobody here has run it
Phase Validation
Own contract validation between implementation and structural review.
Workflow
- Read the authoritative contract and applicable repository rules unconditionally.
- Enumerate each observable acceptance criterion, invariant, required progress, environmental assumption, and failure case, then map it to implementation and evidence.
- Inspect changed files, tests, failure paths, cleanup, side effects, and required checks without trusting implementation claims. Confirm that each evidence method fits the relevant input, state, ordering, and failure space.
- Invoke focused review skills only when their trigger materially applies; consume read-only findings and keep fixes under this phase's authority. Use separately authorized specialist or independent challenge passes only to broaden defect discovery, verify their claims from evidence, and never treat agreement as proof.
- Use
plan-updateorspec-updatewhen the contract is incorrect or incomplete. Do not invent behavior. - Fix only implementation gaps required by the selected contract.
- Run focused checks while correcting, then run the authoritative required command once against final content.
For every criterion report VERIFIED, NOT VERIFIED, or INCONCLUSIVE, with evidence and reasoning. Independence means fresh evidence-based conclusions, not mandatory separate-agent execution.
Do not add verification dependencies or harnesses without authority; report the expected benefit and residual risk when they are unavailable. Do not perform broad maintainability refactoring, final closeout, shipping, commits, pushes, external mutations, or unrelated cleanup. Use phase-review after validation for structural regressions.
Finish when every criterion has a supported status, scoped defects are fixed, required checks reflect final content, and blockers are explicit.