kickoff

name	kickoff
description	Project planning skill. Creates a comprehensive BLUEPRINT.md so any agent can implement without asking questions. Use when no BLUEPRINT.md exists yet and you need to plan a new project or feature. Invoke for project kickoff, planning, architecture design, or roadmap creation.
license	MIT
metadata	{"author":"local","version":"1.0.0","domain":"workflow","triggers":"kickoff, plan, new project, no blueprint, architecture, roadmap, design","role":"architect","scope":"planning","output-format":"markdown","related-skills":"execute, handoff"}

Kickoff

Principal engineer role. Delivers a blueprint so complete that any agent can implement it without asking questions. Does not write code.

Core Workflow

1. Clarify -- Ask 5 or fewer clarifying questions (all at once). Skip anything inferable.
2. Design -- Bounded modules, build order, shared primitives, constraints.
3. Write -- Create .agents/BLUEPRINT.md using the template below.
4. Update -- Set .agents/CONTEXT.md status to "Kickoff complete".
5. Report -- Tell user: "Blueprint ready. [N] phases. Start next session with the execute skill."

BLUEPRINT.md Template

# BLUEPRINT

## Stack & Patterns
- **Errors:** [e.g., anyhow::Result everywhere]
- **Async:** [e.g., tokio for sync, blocking for DB]
- **Config:** [e.g., TOML via config.rs]
- **Tests:** [co-located #[cfg(test)] mod tests]

## Roadmap

### Phase 0 -- Foundation
| # | Task | File(s) | Status |
|---|------|---------|--------|
| 0.1 | [task] | [file] | [ ] |
**Gate:** `cargo test` passes

### Phase N -- [Name]
**Depends on:** Phase N-1
| # | Task | File(s) | Status |
|---|------|---------|--------|
| N.1 | [task] | [file] | [ ] |
**Gate:** [condition]

## Contracts
### [Module]
// exact signatures -- locked, do not change without planning session

## Constraints
- [hard rules agents must never violate]

## Decisions
| Date | Decision | Why |
|------|----------|-----|

Addendum (New Scope Mid-Project)

When a user requests a feature not in the blueprint:

1. Insert a new phase in the roadmap
2. Write new contracts for it
3. Flag if it changes existing phases
4. Create a handoff if needed

Constraints

MUST DO

• Ask all clarifying questions at once (max 5)
• Design for testability from the start
• Lock contracts with exact signatures
• Include phase gates that are automatable

MUST NOT DO

• Write implementation code
• Leave ambiguous contracts
• Create phases without gates
• Skip the constraints section