AI-driven feature lifecycle management for Claude Code. Tracks features through a structured lifecycle — from requirements through design, implementation, and shipping — using .supercrew/tasks/ directories.
Register the SuperCrew marketplace and install the plugin:
/plugin marketplace add steins-z/supercrew
/plugin install supercrew@supercrew
To install from a local directory (for development or testing):
/plugin marketplace add /absolute/path/to/supercrew
/plugin install supercrew@supercrew
Start a new session. Claude will proactively announce which supercrew skill it is invoking before taking any action related to features. No manual skill invocation needed.
SuperCrew injects context at session start via a SessionStart hook that:
- Embeds skill routing guidance directly into session context
- Scans
.supercrew/tasks/for tracked features - Auto-loads the active feature based on your current git branch
- Provides a summary table of all features and their statuses
SuperCrew uses user-namespaced branches for better team collaboration:
| Stage | Branch Pattern | Example |
|---|---|---|
| Backlog | user/<username>/backlog-<feature-id> |
user/steins-z/backlog-dark-mode |
| Active work | user/<username>/<feature-id> |
user/steins-z/dark-mode |
Username is derived from git config user.name, converted to lowercase with hyphens (e.g., "Steins Z" → steins-z).
Skills activate using the 1% rule: if there is even a 1% chance a skill applies, Claude invokes it before responding — including before clarifying questions. When a skill fires, Claude announces it:
"Using supercrew:create-task to set up the new feature directory..."
This means you never need to call skills manually. Just describe what you want.
todo → doing → ready-to-ship → shipped
↑ │
└──────┘
Each feature lives in .supercrew/tasks/<id>/ with files:
| File | Contents | When Created |
|---|---|---|
meta.yaml |
id, title, status, priority, owner | Feature creation (todo) |
prd.md |
background, requirements, out of scope | Feature creation (todo) |
dev-design.md |
design decisions, architecture, implementation notes | Work starts (doing) |
dev-plan.md |
task checklist with progress tracking | Work starts (doing) |
dev-log.md |
chronological development log | Work starts (doing) |
| Skill | When it activates |
|---|---|
create-task |
User wants to create a new feature — creates backlog branch, meta.yaml, and prd.md with real content |
do-task |
Status transitions — starting work, marking done, shipping. Creates dev-* files on todo → doing |
sync-supercrew |
Syncing design iterations, task updates, and progress logging during development |
| Command | Description |
|---|---|
/supercrew:create |
Create a new feature in the backlog |
/supercrew:start <id> |
Start working on a feature (creates work branch and dev-* files) |
/supercrew:sync |
Sync all .supercrew updates (design, plan, log) |
/supercrew:status |
Show all features in a status table |
Just talk naturally — SuperCrew skills activate automatically based on context.
"I want to add dark mode support"
"Let's create a new feature for user authentication"
"Start tracking a caching layer feature"
"/supercrew:start dark-mode"
"Start working on the auth feature"
"Begin implementation of dark-mode"
"I finished the theme toggle component"
"Update the plan - task 3 is done"
"Sync my progress"
"/supercrew:sync"
"This feature is ready to ship"
"Ship it!"
"We need to go back to requirements"
"/supercrew:status"
"Show me all features"
"What's the status of our features?"
.supercrew/
└── features/
└── <feature-id>/
├── meta.yaml # Feature metadata (always present)
├── prd.md # Product requirements (always present)
├── dev-design.md # Technical design (created when work starts)
├── dev-plan.md # Task breakdown (created when work starts)
└── dev-log.md # Development log (created when work starts)
/plugin update supercrew
MIT License — see LICENSE for details.