What problem does it solve? Closing out a sprint requires reading the plan, dev report, conformance results, and every VP review, then making a defensible accept/reject call — a process that is easy to do inconsistently or skip entirely. This Skill inventories the sprint directory, enforces that required artifacts exist, and guides the CTO agent through a structured decision synthesis. ## Core Features & Use Cases - Artifact Inventory and Gating: Lists all sprint files, flags missing canonical artifacts (sprint-plan.md, dev-report.md, conformance.md), and refuses to accept a sprint that was never objectively verified. - Structured Decision Synthesis: Tallies BLOCKER/MAJOR/MINOR findings per VP review, checks conformance NOT-MET/UNVERIFIED items, verifies Phase 1 blockers were addressed, and enforces a provenance gate on quantitative comparison claims. - Decision File Output: Writes a timestamped cto-decision file to the sprint directory with verdict (APPROVED, APPROVED-WITH-CONDITIONS, REJECTED-FOR-REVISION, or ESCALATE-TO-CEO), reasoning, and action items. - Use Case: After a dev team finishes a sprint and all VP reviews are in, run this Skill against the sprint directory to produce a formal, auditable accept/reject decision with a five-line CEO summary. ## Quick Start Run the sprint-accept skill with the path to your completed sprint directory, for example by asking to accept the work in sprints/sprint-03.
