Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework with built-in backward tracing for deep-stack failures, ensuring root-cause understanding before implementation
Turn the current session into a coordination thread that routes per-branch implementation work to durable, reusable child agents. Use when the user says 'orchestrator on', wants this session to act as chief-of-staff across branches, or asks to route work without implementing locally.
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Adversarial questioning and collaborative shaping in one skill. Two modes: stress-test (challenge a plan/design until gaps surface) and shape (iterate on requirements and solution options until alignment). Use when user says 'grill me', 'stress-test this', 'challenge this plan', 'shape this', 'let's explore options', or wants to pressure-test any design before committing.
Compact the current session into a handoff document for another agent or future session to pick up. Captures mission, repo state, role, scope, locked decisions, dispatch sequence, and a pickup checklist. Studio-aware. Use when pausing work, ending a session, switching contexts, or preparing for a fresh agent to continue.
Use when a user completes a phase, sprint, milestone, or meaningful unit of work and needs a retrospective. Also triggers on `/retro` command. Generates honest, structured retrospectives from available project data (GSD planning files, git history, GitHub PRs/issues, user input). Adapts to any project — GSD-managed, plain git repos, GitHub-heavy workflows, or unstructured projects. Jira-aware: detects `.jira/` and redirects per-sprint retros to `/jira:retro` (the plugin owns the tight coupling to CONTEXT.md/VERIFICATION.md). Produces phase retrospectives, cumulative summaries, and stakeholder reports.
Based on SOC occupation classification
| 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> |
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.
$ARGUMENTS:
If the user provided a description, use it as the seed. Either way, explore:
ls, package.json, Cargo.toml, go.mod, README.md, CLAUDE.md, recent git history. What exists already?.jira/, .project/, .planning/ (legacy), .workspacercThen ask focused questions via AskUserQuestion (max 4 questions, bundled):
Skip questions the codebase already answers.
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.
Write .project/PROJECT.md:
---
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>
Break the project into phases. Each phase is a milestone-level chunk that maps to one or more jira sprints.
---
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 the user:
Ask: "Does this capture the project? Should any phases merge, split, or reorder?"
Iterate until approved.
git add .project/PROJECT.md .project/ROADMAP.md
git commit -m "kickoff: initialize project — <project name>"
Then suggest the next step:
/jira:research <phase 1 goal>"/grill shape to refine Phase 1 before sprinting"/jira:to-issues after planning"If .planning/ exists (from GSD or older workflows):
.project/.planning/ — that's a studio:migrate concern