kickoff

Overview of kickoff skill

What kickoff does

The kickoff skill turns a rough idea or an inbox note into a structured Project Note for Project Management. Instead of writing everything in one long response, kickoff uses a two-step flow: a planning pass first, then an execution pass after review. That makes it more useful than a generic “plan this project” prompt when you want cleaner handoffs and less context drift.

Who kickoff is best for

This kickoff skill fits users who already keep idea notes, especially in an inbox-style folder such as 00_Inbox/, and want a repeatable way to promote them into actionable project documents. It is most useful for operators, founders, and builders who want a lightweight project-start ritual without setting up a full PM tool.

Why users choose kickoff

The main differentiator is orchestration. kickoff does not just draft a note once; it explicitly separates planning from execution and asks for confirmation between them. That review gate is valuable if you care about scope, naming, structure, or language before the final Project Note is created.

What to know before installing kickoff

This repository evidence shows a single SKILL.md with no helper scripts, rule packs, or resource files. That keeps kickoff easy to inspect, but it also means output quality depends heavily on your input and on whether your environment supports the multi-agent flow described in the skill. If you want a zero-review, one-shot generator, kickoff may feel more structured than necessary.

How to Use kickoff skill

Install context and what to read first

For kickoff install, add the skill from the repository and read EN/.agents/skills/kickoff/SKILL.md first because that file contains the full workflow, role definition, and language rule. There are no supporting README.md, metadata.json, or helper folders in this skill path, so nearly all behavior is defined in that one file. Before relying on it, confirm your agent environment supports invoking a subagent via a task-style tool.

What input kickoff needs

kickoff usage supports three starting points:

• a file path such as 00_Inbox/MyIdea.md
• inline text such as “Build a habit tracker app”
• no input, in which case the skill is designed to list 00_Inbox/ and ask you to choose

The strongest inputs include problem, audience, desired outcome, constraints, and any deadline or delivery format. Weak input: “make this into a project.” Stronger input: “/kickoff Build a habit tracker app for iOS freelancers; MVP in 3 weeks; needs reminders, streaks, and CSV export; keep scope solo-developer friendly.”

A practical kickoff workflow

A reliable kickoff guide is:

1. Invoke /kickoff with a note path or concise brief.
2. Let the planning agent produce a plan file.
3. Review the plan before approving it.
4. Confirm only after fixing scope, naming, assumptions, and missing constraints.
5. Let the execution agent create the final Project Note from the plan file alone.

That “plan file only” handoff is the key design choice. It reduces accidental carryover from the original long conversation, but it also means omissions in the plan become omissions in the output. Review matters.

Prompt patterns that improve output quality

For kickoff for Project Management, write prompts that are specific enough to shape a project note, not just brainstorm ideas. Good pattern:

• source: where the idea came from
• objective: what success looks like
• scope: must-have vs later
• constraints: time, tools, budget, team size
• deliverable: what document or project artifact you expect

Example:
/kickoff 00_Inbox/ClientPortal.md
Then, during review, add corrections like:

• “Use English for the project note.”
• “Scope MVP to authentication, dashboard, and billing history only.”
• “Target a 2-person team and a 6-week timeline.”

Also note the built-in language rule: kickoff should match the language of the user input or inbox file content.

kickoff skill FAQ

Is kickoff better than a normal planning prompt?

Usually yes, if you want a reviewed, staged workflow. A normal prompt can generate a project plan faster, but kickoff adds a deliberate checkpoint between planning and final note creation. That is useful when errors in scope or structure would be costly downstream.

Is kickoff beginner-friendly?

Yes, if you already understand your idea well enough to describe it. The kickoff skill is simple to inspect because everything is in one SKILL.md. The harder part for beginners is not installation; it is giving enough context for the planning agent to create a solid plan file.

When is kickoff not a good fit?

Skip kickoff if you need deep task automation, integrations, or rigid templates enforced by scripts. The repository does not include helper code, validation logic, or external resources. It is also a poor fit if you do not want the review step and only need a quick one-pass note.

Does kickoff depend on the OrbitOS folder layout?

Partly. The skill explicitly references 00_Inbox/ when no input is provided, so it fits best in a note system that follows a similar convention. You can still use kickoff with inline text or a direct file path, but the default discovery flow assumes that inbox structure exists.

How to Improve kickoff skill

Give kickoff richer project inputs

The fastest way to improve kickoff results is to front-load decision-making context. Include:

• target user
• problem statement
• constraints
• timeline
• success criteria
• known dependencies

This makes the planning agent produce a plan file that the execution agent can reliably expand. If your first prompt lacks these, expect a generic Project Note.

Review the plan like a handoff document

Do not treat the plan review as optional. Because the execution agent reads only the plan file, check for missing assumptions, vague milestones, and unclear scope boundaries. If a human teammate could not execute from the plan, the second phase probably cannot either.

Watch for common failure modes

The main failure cases with kickoff usage are predictable:

• idea is too vague
• inbox note is noisy or unstructured
• constraints are missing
• language expectations are unclear
• users approve the plan too quickly

A practical fix is to normalize messy notes before kickoff: add a title, one-sentence objective, intended audience, and a short “must include” list.

Iterate after the first output

If the final Project Note is close but not usable, improve kickoff by revising the plan, not by only editing the final note. Ask for a narrower scope, clearer milestones, or a different project structure, then rerun from the planning stage. In this skill, better intermediate structure usually matters more than a longer initial prompt.