execution

To resume tracked plan execution, provide a Linear issue with a valid plan-authority envelope and a linked tracked-plan. The Skill consumes these authoritative pointers, validates alignment, and updates runtime state by appending progress events rather than rewriting history.

Plan drift occurs when runtime state diverges from the original plan intent. Prevent plan drift by validating the linked tracked-plan and plan-authority envelope alignment before execution, ensuring runtime state updates remain append-only and never modify stable plan intent.

Yes, tracked plan execution requires helper scripts to read, validate, and append progress events. These scripts validate the plan-authority envelope, linked tracked-plan, and execution surface to guard against invalid cross-surface states during runtime.

Yes, you can continue plan execution when new plan events occur by triggering the execution Skill. It reads the latest plan events, validates the execution surface, and resumes from the current runtime state without modifying the original tracked-plan intent.

Append-only plan execution prevents modification of stable plan intent, meaning historical progress events cannot be rewritten. Execution is blocked if the plan-authority envelope or linked tracked-plan is missing, or if cross-surface consistency checks fail.

Yes, plan execution consumes the authoritative Linear issue pointer as part of workflow validation. It cross-references the Linear issue with the canonical linked tracked-plan and plan-authority envelope to ensure safe execution and prevent invalid cross-surface states.