kickoff

Full Project Kickoff — Interactive Guided Sprint Lifecycle

Run the complete scrum lifecycle from product vision through sprint rest. Use native question UI for every structured choice, render server-built cards verbatim, enforce all QA gates and the planning gate.

Step 0 — Load Context (2 calls)

index_directory({ freshness_check: true })   # skip if <5 min old
get_resume_state()                           # single-call resume detection

That's it. get_resume_state() returns vision, sprints, discoveries, milestones, epics, agents, and next_phase in ~150 tokens.

Phase context — load with load_phase_context() when entering each phase

Phase	Call
Phase 2	load_phase_context({ phase: "discovery" })
Phase 4	load_phase_context({ phase: "epics" })
Phase 5+5b	load_phase_context({ phase: "tickets" }) — includes the planning-gate blocks
Phase 7	load_phase_context({ phase: "implementation", sprint_id, ticket_id })
Phase 8	load_phase_context({ phase: "retro", sprint_id })

Display summary

Render the resume state as a phase banner + yaml data card:

◈ Context Loaded

vision:      set                  # from get_resume_state()
sprints:     21 completed · none active
discoveries: 9 active
milestone:   "#21 Process 2.0"    # [active] 40%
skill_sets:  fe ✓ · la ✗ · wf ✗   # "(defaults — not configured yet)" → Phase 1b will ask
next_phase:  tickets

---

Output Contract — Design Language 2.0

1. Server cards are verbatim. Tools called with format: "card" (update_ticket, advance_sprint, start_sprint, get_sprint_playbook, get_burndown) return pre-rendered card lines. Print them unchanged inside a ```diff fence. Never redraw, restyle, re-align, or wrap them.
2. Phase banners are a ## ◈ <Phase Title> markdown heading followed by a ```yaml data card (keys lowercase, aligned values, # comments for context). Never hand-draw ASCII boxes.
3. Use format: "card" on every status-changing call during ceremonies — each card includes compact state, so skip follow-up get_ticket/get_sprint calls.