caspar-kickoff

name	caspar-kickoff
description	Project kickoff — deep codebase + external research producing an evidence-backed kickoff doc, gap analysis, and MVP path before scoping. Use to start a fresh feature/project from an unclear problem, when the user wants research/options/an MVP recommendation before committing to scope or a plan. Do not trigger once scope is already defined (use /caspar:scope) or for a single targeted code question (use an analyst agent directly).
user-invocable	true

kickoff

Deep research entry point: investigate the codebase and external best practices, then hand off a written kickoff doc with a gap analysis and MVP path. Clear on WHAT to produce; the research method is yours.

Inputs

• $ARGUMENTS — the project/feature context (the current command arguments). If empty, ask the user for it before any tools.
• Any docs the user references — read them FULLY in main context (not via subagent): vision, constraints, decisions, open questions.

Working set (late-bound — read at runtime, never inline)

• Codebase, via read-only research agents (see Method).
• task_name derived from context (kebab-case); current git commit/branch for metadata + permalinks.

Method / guardrails

1. Acknowledge first. Open with a reply naming what we're exploring, the decision we're heading toward, and what success looks like. No tool calls in this first turn.

2. Decompose the project into research areas (components, dirs/files, patterns, data flows, code to extend); track them with TodoWrite.

3. Research in parallel, read-only — locator → analyzer-on-findings → breadth. Spawn follow-ups if a thread is shallow. Use Context7 MCP for central 3rd-party libs.