Skills / Skills / Generate Plan
All skills

/ skill

generate-plan

Skills/generate-plan.md

Turn one Goal into a draft Plan — 1–5 steps, each with an assigned agent + skill + inputs, sequenced with dependencies. The Plan lands as Wiki/Plans/{date}-{goal-slug}.md with status=draft, awaiting Adam's review/approve/reject.

Open as raw file

Run this skill

Runs with bypassPermissions — local dev only.

Skill: generate-plan

Goal → reviewable Plan, with every step routed to a specialist. Owned by the Architect agent.

When to use

  • A Goal exists in Wiki/Goals/ and you want to see what executing it would look like
  • After /decompose-priority, when ratifying a candidate Goal
  • When a draft Plan exists but needs re-routing because team / agent registry changed

Procedure

  1. Load the Goal: read Wiki/Goals/{slug}.md. Extract priority, horizon, suggested_template, suggested_agents, linked_artifacts, body charter + DoD.

  2. Load the parent priority for strategic alignment context.

  3. Pick a template (override > goal.suggested_template > auto-detect):

    • rmbc2: 4 steps — Research / Mechanism / Brief / Copy — for marketing creative work
    • decision-memo: 3 steps — Steelman / Devil's Advocate / Synthesis — for trade-off decisions
    • phased-build: N phases of 1–4 weeks each — for software/product builds
    • freeform: arbitrary 1–5 steps — for everything else

  4. Generate steps (max max_steps, default 5):

    • Each step has: id, title, agent, skill, inputs, status (todo), depends_on (list of step ids), estimated_minutes
    • Each step must reference an EXISTING agent + skill from the registry — don't invent
    • When a step needs a skill that doesn't exist, mark agent: architect and skill: research (a synthetic placeholder); flag the gap in the Plan body so Adam knows
    • Dependency-order the steps; parallel steps share the same depends_on

  5. Write Wiki/Plans/{YYYY-MM-DD}-{goal-slug}.md:

---
type: plan
goal: <a class="wikilink wikilink-broken" href="#">Wiki/Goals/<slug></a>
priority: <a class="wikilink wikilink-broken" href="#"><priority wikilink></a>
status: draft                       # draft → approved → in-progress → done | rejected
template: <rmbc2 | decision-memo | phased-build | freeform>
created: YYYY-MM-DD
approved: ?                         # filled by approval action
target_completion: YYYY-MM-DD
estimated_minutes_total: <sum>
steps:
  - id: 1
    title: "<step title>"
    agent: <agent-slug>
    skill: <skill-slug>
    inputs:
      <key>: <value>
      <key>: <value>
    status: todo
    depends_on: []
    estimated_minutes: <int>
    run_id: ?
  - id: 2
    ...
---

# Plan: <Goal display name>

## Why this plan
(1 paragraph: how the chosen template fits the Goal, why this sequence, what's deliberately scoped out.)

## Step rationale
- **Step 1**: why it's first, what it produces, what it unblocks
- **Step 2**: ...

## Risks / blockers
- (anything that could derail execution)

## Review checklist (for Adam)
- [ ] Steps in the right order
- [ ] Right agents assigned
- [ ] Inputs are specific enough to run without follow-up questions
- [ ] No conflict with Hard Avoids (compliance, fitness sensitivities, family-first)
- [ ] Total estimate fits this week's energy budget

## How to approve
Open this file in `/plans/<id>` (Phase 4d) and click Approve. The Plan moves to `status: approved` and its steps appear on the kanban (`/board`, Phase 4e). Each step's Run button dispatches via the Phase 3 run system.

For now (pre-Phase 4d/e): edit the frontmatter `status: draft` → `status: approved` manually, then run each step's skill from `/skills/<skill>` with the inputs listed in the step.

  1. Surface to Adam: return the path + a one-paragraph summary including total estimated time and any flagged gaps (e.g., "Step 3 needs a skill that doesn't exist yet").

  2. Append an entry to Wiki/Log.md (agent: architect, skill: generate-plan).

Hard rules

  • Status starts at draft. Always. Plans never auto-approve, never auto-execute.
  • Every step must have a real agent + skill OR be flagged as a research gap. No placeholder names.
  • Every step's inputs must be specific enough that the structured form would auto-fill without follow-up questions. This is the Phase 3.1 lesson — pre-flight decisions, not mid-flight prompts.
  • Don't propose more than 5 steps. If a Goal needs more, the answer is "decompose into sub-Goals first."
  • Read the parent priority's section. Weekly plans should be doable this week. MIT plans should fit 90 days. Don't propose a 6-month plan against a weekly priority.
  • Slug collision: if Wiki/Plans/{date}-{slug}.md already exists for today, append -v2, -v3 etc.

Cross-links