lifecycle

Copilot extension lifecycle checkpoints

This layer handles Specify extension lifecycle hooks, not Copilot native hooks/events. It adds no baseline artifacts, phases, or prerequisite exemptions. Read the selected baseline below, consider its User Input, and respect its scope and safeguards before dispatching anything.

Capture the current loaded skill's name, speckit-<command>, once for this invocation. <command> must be one of constitution, specify, clarify, plan, tasks, analyze, checklist, implement, or converge. Use that captured command for both events, even while invoking a hook's skill. Do not dispatch hooks for another command or for taskstoissues.

Apply these checkpoints exactly once per invocation:

1. Run Pre-Execution Checks below before starting the baseline workflow, whether it begins with Outline, Goal, or Execution Steps.
2. Execute the selected baseline unchanged, including all its artifact prerequisites, user approval gates, read-only boundaries, and validation.
3. Run Post-Execution Checks below at the established completion checkpoint:
   • For specify, clarify, plan, tasks, and implement, after successful workflow/validation and before the baseline Completion Report (or its equivalent final summary). Defer that report until post-hooks finish; do not stop at an earlier Done When list or report instruction.
   • For constitution and checklist, after the baseline update/generation and its summary.
   • For analyze, after the analysis report and remediation offer.
   • For converge, after producing and reporting converged or tasks_appended in-session, before listing hooks. A completed Lean assessment that reports remaining work already covered by existing open tasks also reaches this checkpoint, even when nothing is appended. This is not convergence and must not be reported as such. Blocked or unverified assessments do not reach it.

Do not run successful-completion post-hooks if the baseline stops on a failed prerequisite, gate, or validation. Never use a hook to bypass such a stop. This is the sole lifecycle dispatcher in the supported baseline composition: do not perform a second hook pass for a baseline report, Done When item, or EXECUTE_COMMAND marker. Track each dispatched (event, extension, command) in this invocation; do not invoke it twice, automatically retry it, or re-enter the current lifecycle command recursively. This tracking is session guidance, not a persistent lock or host-enforced guarantee.