Getting started on DevFlow

Installation

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

Install

In Claude Code, add the marketplace and install the plugin:

/plugin marketplace add AO-Cyber-Systems/devflow-claude
/plugin install devflow@aocyber

You can do the same thing through the Claude Desktop plugin UI: open the plugins panel, add the AO-Cyber-Systems/devflow-claude marketplace, then install devflow.

Verify it took:

/devflow:help

What installation registers

Enabling the plugin wires up four things automatically. You do not edit settings.json by hand.

Thing	Count	Where it lives
Skills (slash commands)	31	`plugins/devflow/skills/<name>/SKILL.md`
Subagents	13	`plugins/devflow/agents/*.md`
Hooks	15 files, 12 registered	`plugins/devflow/hooks/hooks.json`
Status line	1	declared in `plugin.json`

The runtime mirror

Skills and agents reference shared files with @~/.claude/devflow/... paths. Those @path references are resolved by Claude Code and do not interpolate ${CLAUDE_PLUGIN_ROOT}, so the plugin cannot reference its own bundled runtime directly.

Quickstart

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

This walks the shortest path that still exercises the whole loop. Use a scratch directory — you are going to let agents write code.

1. Initialise

mkdir hello-devflow && cd hello-devflow && git init
claude --dangerously-skip-permissions

In the session:

/devflow:new-project

DevFlow asks what you’re building, researches the domain, scopes requirements into v1 and v2, and writes a roadmap. You will be asked to confirm at three gates (project, requirements, roadmap) — that is gates.confirm_* doing its job.

Your first project

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

/devflow:new-project is the only command that creates .planning/ from nothing. Everything downstream reads what it writes, so it is worth understanding what comes out.

The interview

DevFlow asks what you’re building. Answer in prose — a paragraph is plenty. It uses your answer to decide how much research it needs and what kind the project is.

You can skip the interview entirely with --auto, which makes reasonable assumptions and moves straight to research. Use it when you already know exactly what you want and would rather correct a draft than answer questions.

Existing codebases

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

DevFlow’s default assumption is a greenfield project. On an existing codebase, the roadmapper needs to know what is already there or it will plan work that duplicates or contradicts it.

Map first

/devflow:map-codebase

This dispatches codebase-mapper agents in parallel, each analysing a different angle:

Stack — languages, frameworks, build tooling, dependency posture.
Architecture — module boundaries, data flow, entry points.
Quality — test coverage shape, conventions actually followed (not the ones in the style guide).
Concerns — things that will bite: coupling, dead code, risky patterns.

Findings land in .planning/codebase/.