milestone-seedlisted

Stand up a NEW milestone: ground in the prior milestone's real state and the live dispatch switches, audit the Future Scope deferral list, frame and lock a charter with the operator, create the milestone board, and seed it with decision-shaped 📐 Design (and 🔎 Investigation) tasks grounded in real code. Use when the user says "let's start planning milestone X", "seed milestone X", "let's seed M15", or opens a session to stand up the next milestone. Ends with the board SEEDED AND REGISTERED (a `milestones` row + grooming-manifest entry) but NOT ACTIVATED — that belongs to /milestone-wrap. Distinct from /groom and /design, which work an EXISTING milestone's backlog.
phahadek/claude-orchestrator · ★ 1 · AI & Automation · score 74

Install: claude install-skill phahadek/claude-orchestrator

# Milestone Seed Standing up a milestone is **framing work with a persistence tail**. The framing — what this milestone is *for*, and what it deliberately is not — is the hard part and the part that decays if it lives only in chat. The tail is mechanical: a board, a charter, a seed set, four homes updated. ``` /milestone-seed ──▶ board + charter + seed tasks + milestones row (REGISTERED, NOT ACTIVE) │ ├──▶ /design (works the 📐 Design tasks) ├──▶ /groom (brings 🔲 Backlog to 🗂️ Ready) └──▶ /milestone-wrap (activates it, when the prior one closes) ``` > **You do not activate the milestone.** `/milestone-wrap` Steps 4–5 own marking the > next milestone active — repointing `projects.auto_launch_milestone_id`, the Notion > "Active Task Board" callout, the phase line. This skill registers the milestone (a > `milestones` row + grooming-manifest entry, via `POST /api/projects/<id>/milestones` > in Step 4) but stops short of activating it. Every flow's arm defaults to > `armed=false` (`DEFAULT_ARM`), so a registered-but-unactivated milestone is still > inert — nothing on it can be groomed or dispatched. That boundary is what makes it > safe to seed while the prior milestone is still running. > **Not `/groom` or `/design`.** Those work an existing milestone's backlog. This > creates the milestone. Don't conflate them. ## Doctrine - **Ground in the record, never in memory.