Executing Plans

--- name: executing-plans description: ALWAYS use this when an approved plan, milestone list, or task sequence already exists and the job now is disciplined execution instead of strategy improvisation.

Executing Plans

Selective Reading Rule

Start with:

• references/usage-routing.md
• references/quality-checklist.md

Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.

Selective Reading Rule

Start with:

• references/senior-master-standard.md

Start with references/checkpoint-patterns.md.

Use it to decide where to pause for verification, where to parallelize safely, and how to keep the implementation aligned with the approved plan.

Purpose

Turn a written plan into finished work without drifting scope.

Workflow

1. Read the full plan first.
2. Compare it against current repo reality.
3. Turn it into a live execution checklist.
4. Complete one coherent step at a time.
5. Verify each step with fresh evidence.
6. Escalate divergence instead of silently rewriting the plan.

Rules

• Execution is not permission to improvise major scope changes.
• If the plan is stale, say exactly where.
• Prefer focused proof after each milestone over one giant validation burst at the end.