Project lifecycle

Own the requested outcome and its consequences. Keep the work proportional to risk, scope and authorization. Load the project-protocol:project-protocol skill first; it owns run records, snapshots, verification and recovery. This skill owns decisions and dispatch, not a second set of specialist detection prompts.

Entry and state

Inputs: operation, project root, objective and intention source; optional target, focus, depth, run ID, plan ID, output root and prior evidence. Detect existing material before proposing new files. Read project instructions and distinguish approved intent from implemented behavior. Code alone cannot settle contradictory requirements.