Understand the project
Clarify the problem, who it is for, and what success looks like. For an existing project, inspect the code and identify gaps.
Project Kickoff · 0.6.0
Turn your idea into a buildable plan.
Project Kickoff helps you decide what to build and saves a plan. You can use it alone. You can later use the approved artifacts with Agent-Team or Lanes. Agent-Team adopts selected Beads task IDs through its optional handoff. Lanes uses the plan and current tracker to prepare its own task briefs. After installing, type $project-kickoff start "your project idea" in Codex chat, or /project-kickoff start "your project idea" in Claude Code chat.
Clear directionAgree on the problem and what success looks like
Practical tasksTurn decisions into work agents can carry out
Saved contextResume without repeating the whole conversation
Get clear on the project before building.
Avoid vague requirements, repeated explanations, and agents making conflicting assumptions. Project Kickoff asks focused questions, saves your decisions, and turns the answers into a practical plan.
Agree on a plan
Choose what to build first, how it should work, and the technical approach. You approve the important decisions.
Prepare the workspace
Set up approved project instructions, the selected task tracker, and starter files.
Get ready to build
Check that tasks have clear outcomes and that the plan is ready. You can stop here or later use the saved plan with Agent-Team or Lanes.
How they fit together
Project Kickoff saves the approved plan and project rules. Agent-Team and Lanes are separate execution skills. Start the chosen workflow when you are ready to implement.
Clear decisions, useful tasks, saved context.
Work through the choices that matter to your project. Save the answers once so you and your agents can pick up later without repeating the whole conversation.
ProductWho it helps and what it solves
First releaseWhat to build first and what can wait
ExperienceHow people will use it
TechnicalTools, structure, and how to run it
ExecutionTasks and checks for success
What gets recorded
- Your decisions and the reasons behind them.
- The scope you approved and questions still open.
- Actionable tasks with a clear definition of done.
- Project documents describing the requirements, design, and implementation plan.
What remains yours
- Choose the tools, task tracker, scope, and design direction.
- Approve decisions and any proposed installations before setup.
- Keep existing work and decide what should change.
- Resume later without reconstructing the interview.
Use the approved plan with Agent-Team or Lanes.
Both skills can reuse PRD.md, DESIGN.md, and PLAN.md, along with the project instructions and saved context. Keep one live task tracker and choose the execution workflow that fits your project.
Adopt the Beads handoff
Ask Agent-Team to adopt .project-kickoff/AGENT_TEAM_HANDOFF.json. It verifies the selected existing Beads IDs and uses them for native host coordination. If kickoff used TASKS.md, follow Agent-Team's approved one-time import procedure.
Prepare lanes from the plan
With Lanes installed, invoke lanes start and ask it to use the approved kickoff documents and current tracker. Lanes assigns task tiers and creates bounded briefs with exact file ownership. It prepares its own worktrees and runtime records.
Two ways to reuse the planning work
The Agent-Team handoff is schema-valid-unverified with runtimeVerified set to false. Lanes reuses the documents; Project Kickoff 0.6.0 has no Lanes JSON handoff or runtime validation. Start either workflow separately after kickoff. Use one orchestrator for each task and reconcile unfinished work before switching.
Read the Agent-Team and Lanes comparison or follow the continuation steps.
# Codex
$project-kickoff start "your project idea"
$project-kickoff status
$project-kickoff resume
# Claude Code
/project-kickoff start "your project idea"
$project-kickoff start "your project idea"
$project-kickoff status
$project-kickoff resume
# Claude Code
/project-kickoff start "your project idea"