execution-plan-manager

Execution Plan Manager

Purpose

Create, resume, analyze, and converge execution plans for standard or deep frontend work after the goal is defined.

This skill prevents large tasks from becoming unbounded development sessions. It splits work into small verified slices, selects the minimum useful context budget, records stop/resume state when needed, and decides whether a slice needs a one-pass check, bounded retry loop, goal-based loop, independent review, or durable memory handoff.

When To Use

Use this skill only after AGENTS.md and common/prompt-intent-routing-rules.md classify the task as Standard Workflow or Deep Workflow.

Use this skill when:

• a goal contract exists or the user goal is already explicit;
• the task needs more than one implementation slice;
• the task may need stop/resume state;
• the task has dependencies, blockers, or ordered phases;
• the task should be split before coding;
• the user asks to continue an existing large task;
• the agent needs to compare completed work with the plan;
• the task may require measurable iteration and should be handed to loop-workflow-planner.

When Not To Use

Do not use this skill for Lightweight Workflow prompts, including one small bug, one obvious typo, one obvious type error, one small styling adjustment, one isolated component change, one direct file-scope edit, or one local refactor with clear boundaries.

Do not use this skill to implement code, install tools, scaffold projects, rewrite architecture, create tests, or perform visual QA.

If a lightweight task reveals hidden scope or repeated failure, escalate first using common/prompt-intent-routing-rules.md, then use this skill only if the escalated task is standard or deep.

Required Context

1. Read AGENTS.md.
2. Read common/prompt-intent-routing-rules.md when task scale is not obvious.
3. Read common/planning-rules.md.
4. Read common/planning-analysis-rules.md only in analyze mode.
5. Read common/convergence-rules.md only in converge mode.
6. Read common/checkpoint-rules.md when durable stop/resume state is needed.
7. Read common/agent-loop-policy.md when the plan may need measurable iteration.
8. Confirm the workflow level is Standard Workflow or Deep Workflow.
9. Read the current goal contract from the response, user request, or project/active-goals.md when present and relevant.
10. Read only project overlays needed to slice the task safely, such as project/stack-profile.md, project/architecture-map.md, project/styling-profile.md, or project/verification-profile.md.
11. Read affected source files only when slicing, analysis, or convergence cannot be done safely without them.