ai-coding-skills/skills/create-plan/opencode/SKILL.md

name, description

name	description
create-plan	Use when starting a new feature, project, or complex task that needs structured planning with milestones, bite-sized stories, and resumable execution context in Opencode workflows. Trigger for "create a plan", "make a plan", "plan this", and similar planning requests.

Create Plan (Opencode)

Create and maintain a local plan folder under docs/plans/ (or docs/plan/ if that repository convention is already in use).

Process

Phase 1: Analyze

• Explore the codebase and existing patterns.

Phase 2: Gather Requirements

• Ask questions one at a time until user says ready.
• Confirm scope, constraints, success criteria, dependencies.

Phase 3: Design

• Use Opencode planning/brainstorming flow.
• Propose 2-3 approaches and recommend one.

Phase 4: Plan

• Break into milestones and bite-sized stories.

Phase 5: Generate Plan Files (MANDATORY)

Create docs/plans/YYYY-MM-DD-<short-title>/ with all files below:

1. original-plan.md - copy of original planner-generated plan.
2. final-transcript.md - copy of final planning transcript used to reach approved plan.
3. milestone-plan.md - full implementation spec (from template).
4. story-tracker.md - story/milestone status tracker (from template).
5. continuation-runbook.md - execution instructions and context (from template).

Use templates from this skill's templates/ folder.

Phase 6: Handoff

Always instruct the executing agent:

Read docs/plans/YYYY-MM-DD-<short-title>/continuation-runbook.md first, then execute from that folder.

Do not rely on planner-private files during implementation.

Execution Rules to Include in Plan (MANDATORY)

• Run lint/typecheck/tests after each milestone.
• Prefer linting changed files only for speed.
• Commit locally after each completed milestone (do not push).
• Stop and ask user for feedback.
• Apply feedback, rerun checks, and commit again.
• Move to next milestone only after user approval.
• After all milestones are completed and approved, ask permission to push.
• Only after approved push: mark plan as completed.

Gitignore Note

If docs/plans or docs/plan is gitignored, this is expected. Do not treat inability to commit plan-file updates as a problem. These files are local to the user.

Verification Checklist

• Plan directory created under docs/plans/ (or repo-standard docs/plan/)
• original-plan.md present
• final-transcript.md present
• milestone-plan.md present
• story-tracker.md present
• continuation-runbook.md present
• Handoff explicitly says to read runbook first and execute from plan folder