
Configure which agents run, which AI models they use, and how the workflow behaves. Use when the user wants to change DevFlow settings or configure workflow behavior. Triggers on: "change settings", "configure DevFlow", "update settings", "workflow settings"
Manage strategic initiative context — sync GitHub Epics to disk, list cached initiatives, or show a single initiative body. Planner reads these at plan time. Triggers on: "sync initiatives", "refresh initiatives", "show initiative", "what initiatives are loaded".
Reconcile ROADMAP.md checkbox state against on-disk SUMMARY.md presence. Default: silently corrects drift; --dry-run previews; --interactive prompts per change. Triggers on: "sync roadmap", "reconcile roadmap", "fix roadmap drift", "is the roadmap accurate".
Hand off a TTY-required or shell-env-dependent command to the user's shell. Use for auth flows (gh auth login, doctl auth init, npm login) or shell-init commands (nvm/mise/conda activate, direnv). Non-disruptive when devflow-watch is running. Triggers on: "auth init", "log in to", "needs my password", "needs my shell environment".
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). Triggers on: "sync to github", "push objectives to github", "github release notes", "sync objective".
Show available DevFlow commands and usage guide. Use when the user asks about DevFlow capabilities, available commands, or how to use the system. Triggers on: "what can you do?", "how do I use DevFlow?", "show commands", "devflow help", "what commands are available?"
Small features (single executor, no planner, no verifier) — between micro (1-line) and build (multi-subsystem). Cutoff: <5 files, <200 LOC, no new abstractions. Use when the change is too big for /devflow:micro but doesn't warrant full /devflow:build planning. Triggers on: "small change", "small feature", "5-file change", "isolated bug fix", "do this small task", "tackle this small change", "make a quick pass"
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. Triggers on: "open tui", "show tui", "what's running across sessions", "show org tree".
Consolidated status/resume/pause/health — `/devflow:status [resume|pause|check]`. Default: show progress + route to next action. Subcommands: check (integrity), pause (save context), resume (restore context). Both flag and bare forms accepted. Triggers on: "where are we?", "what's next?", "save my progress", "pick up where we left off".
Resolve a parked decision and resume autonomous execution. Use when you see a pending DECISION-NNN.md in .planning/decisions/pending/, when the user wants to choose an option for a blocked checkpoint:decision, or when you need to tell the executor which option to take. Triggers on: "resolve decision", "decide DECISION-", "pick option for DECISION-", "unblock DECISION-", "answer DECISION-", "choose option for decision", "I want option-a", "go with option-b", "my answer is".
Execute all planned tasks for an objective, running independent tasks in parallel for speed. Use when the user wants to run or execute an already-planned objective. Triggers on: "execute objective", "run objective", "run the jobs", "run the planned objective", "execute the plan"
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. Triggers on: "who else is working on this", "what's in flight", "show org progress", "what are teammates working on".
DEPRECATED — use `/devflow:objective add` instead. Will be removed in v3.0. This redirect logs a deprecation entry and forwards to the consolidated skill.
DEPRECATED — decimal objectives removed in v1.2 (TRD 12-06, I2 survey: 0% usage). Use `/devflow:objective add <description>` to append a new integer objective instead. This redirect logs a deprecation entry.
DEPRECATED — use `/devflow:status check` instead. Will be removed in v3.0. This redirect logs a deprecation entry and forwards to the consolidated skill.
DEPRECATED — use `/devflow:milestone new` instead. Will be removed in v3.0. This redirect logs a deprecation entry and forwards to the consolidated skill.
DEPRECATED — use `/devflow:status pause` instead. Will be removed in v3.0. This redirect logs a deprecation entry and forwards to the consolidated skill.
DEPRECATED — use `/devflow:status resume` instead. Will be removed in v3.0. This redirect logs a deprecation entry and forwards to the consolidated skill.
DEPRECATED — use `/devflow:todo list` instead. Will be removed in v3.0. This redirect logs a deprecation entry and forwards to the consolidated skill.
DEPRECATED — use `/devflow:milestone complete` instead. Will be removed in v3.0. This redirect logs a deprecation entry and forwards to the consolidated skill.
DEPRECATED — use `/devflow:milestone audit` instead. Will be removed in v3.0. This redirect logs a deprecation entry and forwards to the consolidated skill.
DEPRECATED — use `/devflow:todo add` instead. Will be removed in v3.0. This redirect logs a deprecation entry and forwards to the consolidated skill.
Manage milestones: start a new one, audit a finished one, complete it, or plan gap-closure objectives. Subcommand-style: /devflow:milestone new | audit | complete | gaps Use when explicitly requested.
DEPRECATED — use `/devflow:objective remove` instead. Will be removed in v3.0. This redirect logs a deprecation entry and forwards to the consolidated skill.
Research how to build something before planning it — discovers best practices, architecture patterns, and pitfalls for the domain. Use when the user wants to investigate, research, or explore options before planning an objective. Triggers on: "research objective", "investigate before planning", "look into how to build", "what's the best approach for objective"
DEPRECATED — use `/devflow:milestone gaps` instead. Will be removed in v3.0. This redirect logs a deprecation entry and forwards to the consolidated skill.
Add or remove an objective from the current milestone roadmap. Subcommand-style: /devflow:objective add | remove Use when explicitly requested. Note: 'insert' (decimal objectives) was removed in v1.2 — use 'add' instead.
Run independent objectives in parallel using git worktrees, then merge results back. Subcommand-style: /devflow:workstreams setup | status | merge | run Advanced parallel execution — use only when explicitly requested.
Manage todos: capture an idea/task or view the morning standup across local + GitHub + peer sources. Subcommand-style: /devflow:todo add | list Use when the user wants to save something for later, note an idea, or get a "what should I work on?" view. Triggers on: "remember to", "add a todo", "save this idea", "what should I work on?", "morning standup", "check todos".
DEPRECATED — use `/devflow:status` instead. Will be removed in v3.0. This redirect logs a deprecation entry and forwards to the consolidated skill.
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"). Triggers on: "ship X to Y", "build and X", "plan and X", "X then Y", "in one go", "as a chain", "all in sequence", "chain", "ship-and-sync", "research-plan-build"
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. Triggers on: "fix typo", "rename X to Y", "1-line fix", "single-file change", "tiny", "trivial"
Build a feature from start to finish — plans the work, executes it, and verifies the result in one command. Use when the user wants to build something, implement a feature, or work on an objective end-to-end. Triggers on: "build this", "build objective", "let's build", "implement this", "ship this", "make this work", "build the", "work on objective", "start building", "let's implement"
Investigate bugs using a structured approach that survives context resets. Tracks hypotheses, evidence, and progress across sessions. Use when the user reports a bug, error, or something not working as expected. Triggers on: "debug this", "something's broken", "fix this bug", "not working", "there's an error", "why isn't this working?"
See what Claude plans to do for an objective before it starts, so you can course-correct early. Shows the intended approach without creating any files.
Set up a new project from scratch — asks what you're building, researches the domain, defines requirements, and creates a development roadmap. Use when the user wants to start a new project or initialize DevFlow for the first time. Triggers on: "start a new project", "initialize project", "let's build something new", "set up a new project", "new project"
Create a detailed execution plan for an objective, breaking it into concrete tasks with success criteria. Use when the user wants to plan an objective, create execution plans, or prepare for building. Triggers on: "plan objective", "create plans", "plan the next objective", "let's plan", "prepare objective", "make plans for"
Switch between quality, balanced, and budget model profiles to control cost and capability. Use when the user wants to change the AI model tier for DevFlow agents. Triggers on: "change profile", "switch to quality", "switch to balanced", "switch to budget", "set profile"
Archive old objective directories from completed milestones to reduce clutter. Moves completed work to the milestones archive — use only when explicitly requested.
Join the DevFlow community. Community and meta information — not a workflow command.
Capture implementation decisions for an objective before planning — lock in preferences so research and planning don't drift into assumptions. Use when the user wants to shape how an objective gets built before tasks are generated. Triggers on: "discuss objective", "shape the objective", "lock in preferences", "before planning I want to discuss", "implementation decisions"
Analyze an existing codebase to understand its stack, architecture, conventions, and concerns before starting new work. Use when the user wants to understand, analyze, or map an existing codebase. Triggers on: "understand this codebase", "map the code", "analyze architecture", "what does this codebase look like?", "explore the code structure"
Test what was built by walking through expected behavior and checking it matches reality. Use when the user wants to test, verify, or validate what was built in an objective. Triggers on: "test what we built", "verify objective", "check the work", "UAT", "does it work?", "let's test", "validate the implementation"
Generate social media images and videos using HTML/CSS templates combined with AI-generated imagery. Use when the user asks to create social media posts, graphics, videos, stories, reels, quote graphics, promotional content, or any visual content for Facebook, Instagram, or Twitter/X. Triggers include "create a social media post", "make an Instagram graphic", "design a Facebook post", "generate a Twitter image", "create a promotional video", "make a quote graphic", "design content for [platform]", "create an ad for", "make promotional material".
Scan the codebase for security vulnerabilities — checks for secrets, auth flaws, dependency risks, and OWASP Top 10 issues. Standalone — works without project setup. Covers secrets, auth, dependencies, and code-level vulnerabilities. Triggers on: "security audit", "scan for vulnerabilities", "check for secrets", "security review", "find security issues"
Build, review, or visually inspect Flutter UI using eden-ui-flutter widgets and design tokens. Use when the user wants to create new screens, design widgets, audit existing UI, review Flutter code, or test rendered app output via flutter-skill. Triggers on: "build the UI", "design this screen", "create a view", "review the frontend", "audit the UI", "check UI consistency", "make it look good", "frontend review", "visual review", "check how it looks", "inspect the app"
Validate that a monorepo follows the AO Cyber Systems layout convention — root CLAUDE.md declares every area, every area has its own CLAUDE.md, no compiled binaries are tracked in git. Reads the root `CLAUDE.md` Layout table, walks the working tree, and reports drift in a single Markdown summary. Standalone — works on any repo. Triggers on: "audit monorepo layout", "monorepo doctor", "is this monorepo healthy?", "check the layout", "find binaries in the repo".
Stamp a new polyglot monorepo using the AO Cyber Systems scaffold — root CLAUDE.md with Layout table, per-area CLAUDE.md, path-filtered CI workflows, comprehensive .gitignore, and the no-binaries pre-commit hook config. Use this for new product monorepos (the 5-monorepo architecture: aodex, aosentry, eden-biz, politihub, aohealth, plus future ones). Triggers on: "new monorepo", "scaffold a monorepo", "set up a monorepo", "create a new product monorepo".
Build, review, or visually inspect web pages using Hugo templates, Tailwind CSS, and the project's brand design system. Use when the user wants to create new pages, design components, audit existing UI, review frontend code, or visually test rendered pages. Triggers on: "build the UI", "design this page", "create a page", "review the frontend", "audit the UI", "check UI consistency", "make it look good", "frontend review", "visual review", "check how it looks", "inspect the page"
Define or customize a brand design system for a web project. Creates design tokens, color palettes, typography, and component styles. Use when starting a new web project, switching brands, or defining a custom look and feel. Triggers on: "set up the brand", "define the design", "create a brand", "customize the look", "design tokens", "brand preset", "new brand", "theme setup"