plan-creation

Plan Creation

Purpose

This skill transforms the current project state into a single implementation increment.

Each implementation plan defines one bounded, reviewable, and executable unit of work.

The resulting plan becomes the engineering contract between planning, implementation, and review.

---

Lifecycle Stage

Repository Initialization
        ↓
Plan Creation
        ↓
Plan Review

Plan Creation defines what will be implemented next.

It does not perform implementation.

---

Role

Primary role:

Planning Agent

---

When to Use

Use this skill when:

• project initialization has been completed;
• the next implementation increment must be defined;
• a previous implementation plan has been completed;
• implementation priorities need to be adjusted.

Do not use this skill for:

• project discovery;
• architecture design;
• engineering design;
• production code;
• code review.

---

Inputs

Required:

• PROJECT.md
• ROADMAP.md
• ARCHITECTURE.md
• ENGINEERING.md

Additional context:

• ADRs;
• completed plans;
• current repository state.

Planning should reconcile documentation with the actual implementation before producing a new plan.

---

Outputs

Produce one implementation plan.

The plan should define:

• objective;
• scope;
• out-of-scope items;
• acceptance criteria;
• validation strategy;
• implementation checklist;
• risks.

The plan becomes the authoritative specification for the next implementation increment.

---

Procedure

Step 1 — Build Context

Review:

• project definition;
• roadmap;
• architecture;
• engineering design;
• ADRs;
• completed plans;
• current implementation.

Understand both project intent and repository state.

---

Step 2 — Select the Next Increment

Choose the smallest meaningful implementation increment.

The increment should:

• deliver measurable value;
• support the current roadmap phase;
• respect architecture;
• follow engineering conventions;
• remain independently reviewable.