Repo inventory is handled by this skill in a customer-readable, reusable workflow.
Baseline state is handled by this skill in a customer-readable, reusable workflow.
What is this?
Starting in an unfamiliar repository without a baseline makes the agent likely to touch the wrong files, trust stale assumptions, or skip the real blocker. Project Kickoff inventories structure, active tasks, governance files, requirements clues, architecture clues, runtime signals, and risk points before feature work begins. It creates the first startup map so the project starts from observed evidence instead of a blind coding attempt.

When this helps
- Project inventory
- Baseline status
- Startup plan
- Execution handoff
- You want AI to run a structured project startup instead of doing isolated coding tasks without a clear system map.
- You need the agent to inspect the project, identify the real starting point, and build the first action plan before implementation begins.
- You want a higher-standard launch pass that turns scattered repo context into a governed baseline, next actions, and safer execution path.
- It does not solve the whole project. It establishes the baseline needed to start safely.
Safer project start -> Less wrong context -> Clearer next work
Dropping AI into an unknown repo can waste hours because the agent guesses the stack, ignores existing governance, or edits before understanding the project. Project Kickoff is stronger because it creates the initial inventory, baseline status, risk notes, and startup plan before feature work begins. The buyer gets a safer first operating state for future agents. Boundary: It does not solve the whole project; it establishes the baseline needed to start safely.
Included interface patterns
Reusable guided kickoff intake workflow support.
one-click-kickoff-intake.mdReusable master task register workflow support.
master-task-register.mdReusable kickoff readiness report workflow support.
kickoff-readiness-report.md