AO Cyber Systems · Claude Code plugin v2.5.0

Ship features,
not context windows.

DevFlow is a meta-prompting, context engineering and spec-driven development system for Claude Code. It breaks work into objectives, plans each one in a fresh context, and executes in parallel waves with atomic commits. Then it verifies the result against the goal, not against a checklist of finished tasks.

Install DevFlow Read the docs

/plugin marketplace add AO-Cyber-Systems/devflow-claude

/plugin install devflow@aocyber

The problem

Long sessions get worse, not better

A single Claude Code session that plans, builds and verifies a feature accumulates every file it read, every command it ran and every dead end it explored. By the time it writes the code that matters, the signal it needs is buried. Quality drops, the model repeats itself, and work silently degrades.

DevFlow's answer is structural rather than advisory. Planning artifacts live on disk in .planning/ instead of in the conversation. Each job is dispatched to a subagent with a fresh window and only the context that job needs. State survives /clear, context resets and machine reboots, because it was never in the context window to begin with.

Skills

Agents

Hooks

CLI commands

The loop

Six commands, one direction

Each step writes files the next step reads. You can stop after any of them.

new-project

Researches the domain, scopes requirements, produces a roadmap.

discuss-objective

Locks in your implementation preferences before anything is planned.

plan-objective

Breaks an objective into atomic jobs with success criteria.

execute-objective

Runs independent jobs in parallel waves, one commit per task.

verify-work

Tests the result against the goal and records the evidence.

milestone complete

Audits the milestone, archives it, opens the next.

How the loop works →

Why it holds up

Enforcement, not etiquette

Rules that actually bind

Hooks block raw git commit, deny ambient edits outside a skill, and refuse a release tag with no changelog entry. Every gate has a documented escape hatch.

Parallel where it's safe

The planner marks job dependencies. Independent jobs run concurrently in separate context windows; dependent ones wait.

Rigor matched to the work

A (kind, work) table derives TDD posture, planning depth, model tier and verification rigor. A spike is not tested like a payments API.

One task, one commit

Atomic commits with objective scope and task IDs, so a bad objective is a clean git revert rather than an archaeology project.

Memory that outlives context

Decisions, blockers and position live in .planning/STATE.md. Resume a week later with /devflow:status resume.

Cost you choose

Quality, balanced and budget profiles map each of the 13 agents to a model tier. Switch with one command.

Get started

Install in two lines

DevFlow ships as a Claude Code plugin. It works on macOS, Windows and Linux, and installs from the /plugin command or the Claude Desktop plugin UI.