Commands on DevFlow

Core workflow

Mon, 01 Jan 0001 00:00:00 +0000

Command	Arguments	What it does
`/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: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:research-objective`	`[objective]`	Research how to build something before planning it — discovers best practices, architecture patterns, and pitfalls for the domain.
`/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:execute-objective`	`<phase-number> [--gaps-only]`	Execute all planned tasks for an objective, running independent tasks in parallel for speed.
`/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:verify-work`	`[objective number, e.g., '4']`	Test what was built by walking through expected behavior and checking it matches reality.
`/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: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:debug`	`[issue description]`	Investigate bugs using a structured approach that survives context resets. Tracks hypotheses, evidence, and progress across sessions.

Choosing a tier

The single biggest cost lever in DevFlow is picking the right entry point.

Status and navigation

Mon, 01 Jan 0001 00:00:00 +0000

Command	Arguments	What it does
`/devflow:status`	`[check \| pause \| resume]`	Consolidated status/resume/pause/health — `/devflow:status [resume\|pause\|check]`.
`/devflow:help`	—	Show available DevFlow commands and usage guide.
`/devflow:todo`	`<add\|list> [args...]`	Manage todos: capture an idea/task or view the morning standup across local + GitHub + peer sources.
`/devflow:decide`	`[<decision-id> <choice>]`	Resolve a parked decision and resume autonomous execution.
`/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: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:status

The consolidated status command. Four behaviours, one entry point.

Managing the plan

Mon, 01 Jan 0001 00:00:00 +0000

Command	Arguments	What it does
`/devflow:objective`	`<add\|remove> [args...]`	Add or remove an objective from the current milestone roadmap.
`/devflow:milestone` type 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:list-objective-assumptions` type it yourself	`[objective]`	See what Claude plans to do for an objective before it starts, so you can course-correct early.
`/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:cleanup` type it yourself	—	Archive old objective directories from completed milestones to reduce clutter.

Most of these are user-typed only

Advanced execution

Mon, 01 Jan 0001 00:00:00 +0000

Command	Arguments	What it does
`/devflow:workstreams` type it yourself	`<setup\|status\|merge\|run> [args...]`	Run independent objectives in parallel using git worktrees, then merge results back.
`/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: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:workstreams

Runs independent objectives in parallel using git worktrees, then merges them back. This is a level above wave parallelism — waves parallelise jobs inside one objective; workstreams parallelise whole objectives.

Integrations and analysis

Mon, 01 Jan 0001 00:00:00 +0000

Command	Arguments	What it does
`/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: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: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: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: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:gh-sync

Pushes planning state to GitHub. One-way: planning files stay authoritative, GitHub is derivative.

Settings

Mon, 01 Jan 0001 00:00:00 +0000

Command	Arguments	What it does
`/devflow:settings` type it yourself	—	Configure which agents run, which AI models they use, and how the workflow behaves.
`/devflow:set-profile` type it yourself	`<profile>`	Switch between quality, balanced, and budget model profiles to control cost and capability.

Both are user-typed only — Claude cannot fire them, because they rewrite config.json and change cost characteristics for everything downstream.

/devflow:set-profile

/devflow:set-profile quality
/devflow:set-profile balanced
/devflow:set-profile budget

Switches the model tier for every agent at once. The mapping is not uniform — each agent has its own per-profile assignment, so budget does not simply mean “Haiku everywhere”: