Dev Flow Pro Development Workflow

Problem

When a coding agent is asked to modify a complex repository directly, it may skip planning, patch code before adding tests, omit review, or lose progress when context expires. dev-flow turns these risks into explicit workflow constraints, requiring scenario routing, pre-checks, and stage-level traceability.

How It Works

It routes tasks into A new feature, B bug fix, C rework, D refactor, E assessment, F hotfix, or G dependency upgrade, then loads the matching flow file. Execution enforces rules such as no coding without a plan, no code changes without tests, no release without review. If optional tooling is unavailable, it falls back to manual task_plan.md, progress.md, and findings.md. It also requires updating progress before context exhaustion, isolating tests or subagent experiments in git worktree, and handling repeated failures, blocked test suites, or missing plan details.

Boundaries

Use it for multi-step, multi-file engineering changes that need review and recovery. It is not intended for one-line fixes, configuration changes, or copy edits. If the repository lacks a passing test baseline, installed dependencies, or is not at the repo root, fix those prerequisites first.