Commands
Every skill, grouped by what you’re trying to get done. All tables on these pages are generated from the plugin source.
The complete surface
| Command | Arguments | What it does |
|---|---|---|
/devflow:awareness | [--peer-only|--org-only] [--quarter Q] [--product P] [--refresh [peer|org]] [--no-fetch] [--raw] | Show cross-repo awareness: peer view (who's working on what in this repo) and org-wide progress (Product Roadmap). Renders both views by default. |
/devflow:build | <objective-number-or-description> [--pause] [--skip-research] [--work TYPE] [--tdd POSTURE] [--depth LEVEL] [--model PROFILE] | Build a feature from start to finish — plans the work, executes it, and verifies the result in one command. |
/devflow:cleanuptype it yourself | — | Archive old objective directories from completed milestones to reduce clutter. |
/devflow:debug | [issue description] | Investigate bugs using a structured approach that survives context resets. Tracks hypotheses, evidence, and progress across sessions. |
/devflow:decide | [<decision-id> <choice>] | Resolve a parked decision and resume autonomous execution. |
/devflow:discuss-objective | <objective-number> | Capture implementation decisions for an objective before planning — lock in preferences so research and planning don't drift into assumptions. |
/devflow:execute-objective | <phase-number> [--gaps-only] | Execute all planned tasks for an objective, running independent tasks in parallel for speed. |
/devflow:flow | <description of the multi-step flow> | Orchestrate a multi-step DevFlow workflow by chaining skills. Use when the user wants to invoke a sequence of skills as one ask (e.g., "build and sync to github", "research, plan, then build", "ship and announce"). |
/devflow:gh-sync | [objectives|release <tag>|status|<objective_id>] | Sync DevFlow planning state to GitHub — create/update objective issues, generate release notes, or push a single objective's state (body + sticky comment + Project v2 fields). |
/devflow:handoff | <command to run interactively or via user shell> | Hand off a TTY-required or shell-env-dependent command to the user's shell. |
/devflow:help | — | Show available DevFlow commands and usage guide. |
/devflow:initiatives | [sync [--initiative <slug>] [--project-id <id>] [--force]] | [list [--home <path>]] | [show <slug>] | Manage strategic initiative context — sync GitHub Epics to disk, list cached initiatives, or show a single initiative body. Planner reads these at plan time. |
/devflow:list-objective-assumptionstype it yourself | [objective] | See what Claude plans to do for an objective before it starts, so you can course-correct early. |
/devflow:map-codebase | [optional: specific area to map, e.g., 'api' or 'auth'] | Analyze an existing codebase to understand its stack, architecture, conventions, and concerns before starting new work. |
/devflow:micro | <description> | Sub-30-LOC, single-file changes. The cheapest DevFlow path (~2k tokens). Use for typo fixes, single-line bug fixes, prop renames, dependency bumps, missing semicolons. |
/devflow:milestonetype it yourself | <new|audit|complete|gaps> [args...] | Manage milestones: start a new one, audit a finished one, complete it, or plan gap-closure objectives. |
/devflow:new-project | [--auto] | Set up a new project from scratch — asks what you're building, researches the domain, defines requirements, and creates a development roadmap. |
/devflow:objective | <add|remove> [args...] | Add or remove an objective from the current milestone roadmap. |
/devflow:plan-objective | [objective] [--auto] [--research] [--skip-research] [--gaps] [--skip-verify] [--work TYPE] [--tdd POSTURE] [--depth LEVEL] [--model PROFILE] | Create a detailed execution plan for an objective, breaking it into concrete tasks with success criteria. |
/devflow:quick | [--full] | Small features (single executor, no planner, no verifier) — between micro (1-line) and build (multi-subsystem). Cutoff: <5 files, <200 LOC, no new abstractions. |
/devflow:research-objective | [objective] | Research how to build something before planning it — discovers best practices, architecture patterns, and pitfalls for the domain. |
/devflow:security-audit | [optional: path scope like 'src/api' or focus filter like 'secrets-only', 'auth-only', 'deps-only'] | Scan the codebase for security vulnerabilities — checks for secrets, auth flaws, dependency risks, and OWASP Top 10 issues. |
/devflow:set-profiletype it yourself | <profile> | Switch between quality, balanced, and budget model profiles to control cost and capability. |
/devflow:settingstype it yourself | — | Configure which agents run, which AI models they use, and how the workflow behaves. |
/devflow:status | [check | pause | resume] | Consolidated status/resume/pause/health — `/devflow:status [resume|pause|check]`. |
/devflow:sync-roadmap | [--dry-run] [--interactive] [--raw] | Reconcile ROADMAP.md checkbox state against on-disk SUMMARY.md presence. Default: silently corrects drift; --dry-run previews; --interactive prompts per change. |
/devflow:todo | <add|list> [args...] | Manage todos: capture an idea/task or view the morning standup across local + GitHub + peer sources. |
/devflow:tui | [--once] [--raw] [--no-color] [--reset-only] | Open the program-aware TUI viewer — read-only terminal UI showing parallel sessions, org tree, and active initiatives in three stacked panels. tmux-safe; reflows narrow terminals. |
/devflow:ui-eval | [objective number or manifest path] | Run the UI visual-evaluation pipeline on a Flutter surface or objective: capture each declared UI state, score it through the offline visual-eval engine, and write machine-judged evidence the verifier consumes. |
/devflow:verify-work | [objective number, e.g., '4'] | Test what was built by walking through expected behavior and checking it matches reality. |
/devflow:workstreamstype it yourself | <setup|status|merge|run> [args...] | Run independent objectives in parallel using git worktrees, then merge results back. |
A note on who can invoke what
Six skills carry disable-model-invocation: true. Claude cannot fire them —
you must type them yourself. They all mutate planning state in ways that are
annoying to undo:
| Command | Why it’s user-only |
|---|---|
/devflow:objective | remove cascade-renumbers every objective above it |
/devflow:milestone | archives and transitions milestone state |
/devflow:workstreams | creates and merges git worktrees |
/devflow:cleanup | moves objective directories out of the working tree |
/devflow:settings | rewrites config.json |
/devflow:set-profile | changes the model tier for every agent |
If Claude needs the equivalent operation it uses df-tools directly, or asks you
to type the command.
Core workflow
The commands that plan, build and verify. These are the ones you use daily.
Status and navigation
Finding out where you are, what's next, and what everyone else is doing.
Managing the plan
Changing scope mid-milestone: adding objectives, auditing, archiving, and fixing drift.
Advanced execution
Parallel worktrees, chained skills, and handing TTY-bound commands to your own shell.
Integrations and analysis
GitHub sync, strategic initiatives, UI evaluation, security auditing and codebase mapping.
Settings
Changing which agents run, which models they use, and how much the workflow asks you.