kickoff-prompt

Defines the format and quality bar for cold-start Kickoff sections in spec files.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/astroville/sprout --skill kickoff-prompt-astroville
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kickoff-prompt
Source: https://github.com/astroville/sprout/tree/main/.claude/skills/kickoff-prompt
Command: npx skills add https://github.com/astroville/sprout --skill kickoff-prompt-astroville

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you return to a spec after a context break, a fresh AI session has no idea what the spec is, where work stands, or which files to open first. This Skill defines a terse, paste-ready ## Kickoff section that lives inside every spec so a cold session becomes productive in seconds. ## Core Features & Use Cases - Standardized Kickoff Format: Defines the exact structure of the ## Kickoff section — a one-line summary, Status, Pick up at, a runnable pointer, Files, and an optional Skip line. - Lifecycle Guidance: Specifies when workflows like /design, /deliver, and /diagnose should write or rewrite the kickoff as spec status changes. - Quality Bar with Examples: Enforces a 60–120 token target (200 hard cap) and provides good and anti-pattern examples so kickoffs stay actionable instead of becoming spec summaries. - Use Case: After a weekend break, you paste a spec's kickoff into a fresh session and the model immediately knows the spec's purpose, current status, the exact next step, and the 2–5 files to open first. ## Quick Start Ask the agent to write or refresh the ## Kickoff section of your spec following the kickoff-prompt format so a fresh session can resume work instantly.

Frequently Asked Questions about kickoff-prompt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a kickoff prompt for a spec file?▼

Write a `## Kickoff` section with a one-line summary in the user's vocabulary, a Status line, a concrete Pick up at next step, a runnable pointer such as a spec path or slash command, and 2–5 file references. Keep the body between 60 and 120 tokens with a hard cap of 200.

What is the difference between a kickoff prompt and a spec summary?▼

A kickoff is a prompt, not documentation. It contains only what a fresh session needs to act within 30 seconds: status, next step, pointer, and key files. The spec body holds the full documentation; the kickoff references it rather than repeating it.

When should the Kickoff section be updated?▼

Update it when the spec's status flips between planning, delivering, blocked, or in-review, or when a meaningful chunk of work lands. The Pick up at line must always reflect the current state, not work completed commits ago.

What are common mistakes when writing cold-start prompts?▼

Common mistakes include writing prose paragraphs instead of pointers, listing every changed file instead of the 2–5 load-bearing ones, omitting the runnable pointer line, and leaving stale next steps after work has shipped.

How long should a spec kickoff prompt be?▼

Target 60–120 tokens with a hard cap of 200 tokens. If the kickoff runs longer, the spec body is doing the kickoff's job and the content should be trimmed to pointers and essentials.