New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Kickoff

by koolamusic in koolamusic/claudefiles

Initialize a new project with PROJECT.md + ROADMAP.md in .project/, set up jira and studio, and route to the first sprint.

MITAuto-check passedProduct & Project Management

Install Kickoff

skills CLI
$ npx skills add koolamusic/claudefiles --skill kickoff -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install koolamusic/claudefiles kickoff --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/koolamusic/claudefiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/kickoff .claude/skills/kickoff && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
kickoff
GitHub stars
130
Token cost
~1.2k tokens
SKILL.md length
490 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Initialize a new project with PROJECT.md + ROADMAP.md in .project/, set up jira and studio, and route to the first sprint.

  • Works in 6 steps: Understand the project → Set up infrastructure → Write PROJECT.md → …
  • Starting a new project
  • SKILL.md covers Input, Process, Legacy migration and Hard rules
  • Calls git

What it does

Kickoff is an agent skill from koolamusic/claudefiles. Initialize a new project with PROJECT.md + ROADMAP.md in .project/, set up jira and studio, and route to the first sprint. Use when starting a new project, onboarding a new codebase, or setting up workflow infrastructure for the first time.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management. It works with Jira. The repository describes itself as: A minimal catalog of my favourite skills for working with claude. The licence is MIT.

When your agent uses it

  • Starting a new project
  • Onboarding a new codebase
  • Setting up workflow infrastructure for the first time

Example prompts

  • “/kickoff”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Understand the project
  2. Set up infrastructure
  3. Write PROJECT.md
  4. Write ROADMAP.md
  5. Present and iterate
  6. Commit and route

What it can do on your machine

Read from SKILL.md and the folder at commit 297c432. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Kickoff loads about 1.2k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 490 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from koolamusic/claudefiles at commit 297c432, republished under its MIT licence (© koolamusic). 490 words, ~1,232 tokens.

Download SKILL.mdSave it as .claude/skills/kickoff/SKILL.md (or your agent's skills folder).
name
kickoff
description
Initialize a new project with PROJECT.md + ROADMAP.md in .project/, set up jira and studio, and route to the first sprint. Use when starting a new project, onboarding a new codebase, or setting up workflow infrastructure for the first time.
argument-hint
<project description or goal>

Kickoff

One command to go from empty repo (or unfamiliar codebase) to a working project with full workflow infrastructure. Produces .project/PROJECT.md + ROADMAP.md, initializes jira and studio, and points you at the first sprint.

Input

$ARGUMENTS:

  • Free text — a description of what this project is and what you're trying to build
  • Empty — start with adaptive questioning to understand the project

Process

1. Understand the project

If the user provided a description, use it as the seed. Either way, explore:

  • Codebase scan — ls, package.json, Cargo.toml, go.mod, README.md, CLAUDE.md, recent git history. What exists already?
  • Stack detection — language, framework, database, deployment target
  • Existing workflow state — .jira/, .project/, .planning/ (legacy), .workspacerc

Then ask focused questions via AskUserQuestion (max 4 questions, bundled):

  • What is this project? (one sentence)
  • Who uses it and what problem does it solve?
  • What are the hard constraints? (stack, timeline, compliance, team size)
  • What does "done" look like for the first milestone?

Skip questions the codebase already answers.

2. Set up infrastructure

Run these in sequence:

a. Studio — if no .workspacerc exists, invoke /studio:setup semantics (create workspace, symlinks, gitignore block, hook wiring). If .workspacerc already exists, skip.

b. Jira — if no .jira/ exists, invoke /jira:init semantics (bootstrap .jira/ with STATE.md, sprints/). If .jira/ already exists, skip.

c. Create .project/ — mkdir -p .project/. If studio is active, this will be a symlink into the workspace.

3. Write PROJECT.md

Write .project/PROJECT.md:

markdown
---
name: <project name>
created: <YYYY-MM-DD>
stack: <detected stack summary>
status: active
---

# <Project Name>

## Purpose
<2-3 sentences: what this project is and why it exists>

## Constraints
<bulleted list of hard constraints — technical, timeline, compliance, team>

## Success criteria
<what "done" looks like — measurable where possible>

## Stack
<language, framework, database, deployment, key dependencies>

## Team
<who's working on this — roles, not names if unknown>

## Decisions
<significant architectural or product decisions already made — reference CLAUDE.md, ADRs, or CONTEXT.md entries>
4. Write ROADMAP.md

Break the project into phases. Each phase is a milestone-level chunk that maps to one or more jira sprints.

markdown
---
project: <project name>
created: <YYYY-MM-DD>
phases: <count>
---

# Roadmap

## Phase 1: <name>
**Goal:** <one sentence>
**Sprints:** <estimated count>
**Depends on:** —
**Status:** not-started

### Deliverables
- <deliverable 1>
- <deliverable 2>

### Success criteria
- [ ] <criterion 1>
- [ ] <criterion 2>

## Phase 2: <name>
...

Scale the roadmap to the project. A weekend hack gets 2-3 phases. A production app gets 5-10. Don't over-plan — the roadmap is a compass, not a GPS route.

Show full SKILL.md (212 more words)Show less
5. Present and iterate

Show the user:

  • PROJECT.md summary
  • ROADMAP.md phase breakdown
  • Infrastructure status (studio, jira)

Ask: "Does this capture the project? Should any phases merge, split, or reorder?"

Iterate until approved.

6. Commit and route
bash
git add .project/PROJECT.md .project/ROADMAP.md
git commit -m "kickoff: initialize project — <project name>"

Then suggest the next step:

  • If Phase 1 is clear enough to sprint on: "Ready for /jira:research <phase 1 goal>"
  • If Phase 1 needs shaping first: "Ready for /grill shape to refine Phase 1 before sprinting"
  • If the user wants to decompose Phase 1 into issues first: "Ready for /jira:to-issues after planning"

Legacy migration

If .planning/ exists (from GSD or older workflows):

  1. Note its contents to the user
  2. Offer to migrate relevant artifacts (PROJECT.md, ROADMAP.md equivalents) into .project/
  3. Don't delete .planning/ — that's a studio:migrate concern

Hard rules

  • Never skip the user conversation. Even if the codebase is obvious, confirm with the user. Kickoff is alignment, not automation.
  • Infrastructure is idempotent. Re-running kickoff on an initialized project updates PROJECT.md and ROADMAP.md but doesn't re-init jira or studio.
  • Roadmap phases are NOT jira sprints. A phase may require multiple sprints. The mapping is: phase = milestone, sprint = one research→plan→execute cycle within a phase.
  • Don't start a sprint. Kickoff ends at the roadmap. The user decides when to start the first sprint.
  • Never push. Commit locally only.

© koolamusic, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/kickoff of koolamusic/claudefiles.

Open the folder on GitHubat commit 297c432

Compare with similar skills

Kickoff next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Kickoff compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Kickoff this skillkoolamusic/claudefiles130—~1.2kAutomated safety check: PassMIT
Jira Natural Language Interfacejjmartres/opencode1333 repos~1.7kAutomated safety check: PassMIT
Tidycroffasia/itsaplan903—~2.8kAutomated safety check: PassAGPL-3.0
Jirakv0906/pm-kit138—~4.2kAutomated safety check: NotesMIT
Jira CLICode-and-Sorts/awesome-copilot-agents5791 repos~1.7kAutomated safety check: PassMIT
JiraVixenLights/Vixen114—~3.4kAutomated safety check: PassCustom licence

Similar skills

  • Jira Natural Language Interface

    jjmartres/opencode

    Lets an agent view, create, update and transition Jira issues in natural language, automatically choosing between the jira CLI and Atlassian MCP tools.

    133 GitHub starsUsed in 3 repos~1.7k tokens
    Product & Project ManagementAuto-check passed

  • Tidy

    croffasia/itsaplan

    Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality.

    903 GitHub stars~2.8k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Jira

    kv0906/pm-kit

    Jira integration via acli CLI. An agent skill from kv0906/pm-kit.

    138 GitHub stars~4.2k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check: notes

  • Jira CLI

    Code-and-Sorts/awesome-copilot-agents

    Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows.

    579 GitHub starsUsed in 1 repo~1.7k tokens
    Product & Project ManagementAuto-check passed

  • Jira

    VixenLights/Vixen

    Manages JIRA issues, projects, and workflows using Atlassian MCP.

    114 GitHub stars~3.4k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Run Parallel Tasks

    LIDR-academy/AI4Devs-LTI-extended

    Run N feature tasks in parallel, each in its own worktree, following the full specboot pipeline (enrich → new → ff → apply → verify).

    278 GitHub stars~1.5k tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed

More from koolamusic/claudefiles

All 13 skills in this repo

  • Explainer Formats

    koolamusic/claudefiles

    A skill your agent uses when asked to explain a topic, codebase, process, or document in a specific output format — plain language or Simplified Technical English (STE, in the style of ASD-STE100…

    130 GitHub stars~1.7k tokensUpdated 3 days ago
    Auto-check passed

  • Breadboarding

    koolamusic/claudefiles

    Transform a workflow description into affordance tables showing UI and Code affordances with their wiring.

    130 GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed

  • Orchestrator

    koolamusic/claudefiles

    Turn the current session into a chief-of-staff thread that runs a war room of three role slots — surveyor, executor, auditor — and routes per-branch work to durable, reusable child agents.

    130 GitHub stars~1.7k tokensUpdated 3 days ago
    Auto-check passed

  • Retro

    koolamusic/claudefiles

    A skill your agent uses when a user completes a phase, sprint, milestone, or meaningful unit of work and needs a retrospective.

    130 GitHub stars~2.8k tokensUpdated 3 days ago
    Auto-check passed

  • Skill Creator

    koolamusic/claudefiles

    Guide for creating effective skills. An agent skill from koolamusic/claudefiles.

    130 GitHub stars~1.7k tokensUpdated 3 days ago
    Auto-check passed

  • Debug

    koolamusic/claudefiles

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework with built-in backward tracing for deep-stack failures…

    130 GitHub stars~3.1k tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Kickoff

What does Kickoff do?

Initialize a new project with PROJECT.md + ROADMAP.md in .project/, set up jira and studio, and route to the first sprint. Kickoff is an agent skill from koolamusic/claudefiles.project/, set up jira and studio, and route to the first sprint.

When should I use Kickoff?

Kickoff fits situations like: starting a new project; onboarding a new codebase; setting up workflow infrastructure for the first time.

How do I install Kickoff in Claude Code?

Run `npx skills add koolamusic/claudefiles --skill kickoff -a claude-code`. Or copy the skill folder (skills/kickoff in koolamusic/claudefiles) into .claude/skills/kickoff in your project. Claude Code loads it when a task matches its description.

How do I install Kickoff in Codex?

Run `npx skills add koolamusic/claudefiles --skill kickoff -a codex`. Or copy the skill folder (skills/kickoff in koolamusic/claudefiles) into .agents/skills/kickoff in your project. Codex loads it when a task matches its description.

Can I use Kickoff in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add koolamusic/claudefiles --skill kickoff -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kickoff, .gemini/skills/kickoff, .github/skills/kickoff and .opencode/skills/kickoff in your project.

What does Kickoff need to run?

Going by SKILL.md and its folder, Kickoff needs the command-line tools its instructions call (git).

Does Kickoff access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Kickoff safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Kickoff use?

Kickoff is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Kickoff use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Kickoff?

Skills that share tags, products or a category with Kickoff: Jira Natural Language Interface (jjmartres/opencode, 133 stars), Tidy (croffasia/itsaplan, 903 stars), Jira (kv0906/pm-kit, 138 stars) and Jira CLI (Code-and-Sorts/awesome-copilot-agents, 579 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Kickoff?

koolamusic (a GitHub user) maintains it in koolamusic/claudefiles, which has 130 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 5, 2026.

Source: koolamusic/claudefiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.