What problem does it solve? Complex engineering work often loses critical context between sessions, forcing agents or developers to rediscover architectural decisions after interruptions. This Skill produces implementation plans that act as persistent execution contracts, preserving verified context, decisions, progress state, and validation criteria so another agent can resume work without reconstructing hidden reasoning. ## Core Features & Use Cases - Structured Plan Lifecycle: Manages plans through DRAFT, READY, IN_PROGRESS, BLOCKED, REPLANNING, and terminal states with a defined storage hierarchy under docs/public/plans and an INDEX.md catalog. - Execution Contract Definition: Captures requirements with traceability IDs, design decisions, invariants, change maps, dependency ordering, and explicit executor discretion boundaries. - Living Execution State: Maintains Current State Snapshots, checkpoint ledgers, compliance matrices, decision logs, deviation records, and handoff snapshots for safe resumption after context loss. - Use Case: When asked to plan a multi-milestone refactor such as an audio engine lifecycle migration, the Skill inspects repository evidence, records the baseline revision, and authors a READY plan with step-level validation gates that a separate execution agent can follow. ## Quick Start Ask the assistant to author a formal implementation plan for your feature or refactor before any code changes begin.
