devflow

Devflow Plugin

Comprehensive feature development workflows with specialized agents for codebase exploration, architecture design, test planning, security auditing, and quality review.

Overview

This plugin provides four development workflow commands:

• /feature - 9-phase implementation-first workflow
• /tdd - 9-phase Test-Driven Development workflow with Red-Green-Refactor cycles
• /architect - 7-phase architecture design workflow (no implementation)
• /code-review - Standalone code review with parallel agents and confidence-based filtering

The full workflows ensure deep codebase understanding before implementation. All commands use specialized agents powered by different models for optimal results.

Agents

Agent	Model	Color	Purpose	Used By
code-explorer	Sonnet	Yellow	Analyzes codebase, traces execution paths, maps architecture	/feature, /tdd, /architect
code-architect	Opus	Yellow	Designs feature architectures with comprehensive blueprints	/feature, /tdd, /architect
test-analyzer	Opus	Green	Analyzes existing code and proposes test plans	/feature
tdd-test-planner	Opus	Green	Designs tests from requirements before code exists	/tdd
test-runner	Haiku	Green	Executes tests and reports structured results	/feature, /tdd
code-reviewer	Opus	Red	Reviews code for bugs, security, and convention adherence	All
issue-verifier	Opus	Yellow	Validates review findings, filters false positives	All
security-auditor	Opus	Red	Deep security analysis (optional, on request)	All

Agent Triggering

Agents include enhanced descriptions for automatic triggering:

• code-explorer: Triggers when exploring unfamiliar code or tracing existing features
• code-architect: Triggers when designing new features or planning implementations
• test-analyzer: Triggers when analyzing existing code to propose test cases
• tdd-test-planner: Triggers when designing tests from requirements (TDD workflow)
• test-runner: Triggers when executing tests and reporting results
• code-reviewer: Triggers after code changes or on review requests
• issue-verifier: Triggers after initial review to validate findings (automatic in review phase)
• security-auditor: Triggers only on explicit user request (optional)

Commands

/feature <feature-description>

Launches the guided 9-phase implementation-first workflow:

1. Discovery - Understand requirements
2. Codebase Exploration - Select exploration focuses (interactive), launch parallel agents
3. Clarifying Questions - Iterative dialogue to resolve all ambiguities
4. Architecture Design - Select architecture perspectives (interactive), user selects from proposals
5. Planning - Create implementation plan with task-level tracking (user approval required)
6. Implementation - Build following approved plan, update task progress in plan file
7. Testing - Select test focuses (interactive), get user approval, create TEST-NNN tasks, write tests
8. Quality Review - Select review focuses (interactive), present findings for user selection
9. Summary - Document completion, clean up state file (plan file kept if incomplete)

/tdd <feature-description>

Launches the guided 9-phase test-first TDD workflow:

1. Discovery - Understand requirements
2. Codebase Exploration - Select exploration focuses (interactive), launch parallel agents
3. Clarifying Questions - Iterative dialogue to resolve all ambiguities
4. Test Planning - Select test focuses (interactive), design tests from requirements
5. Architecture Design - Select architecture perspectives (interactive), design code to pass tests
6. Planning - Create TDD task list with Red/Green/Refactor substeps (user approval required)
7. TDD Implementation - Per-task Red-Green-Refactor cycles:
   • RED: Write failing test, verify it fails
   • GREEN: Write minimal code to pass (max 3 retries)
   • REFACTOR: Optional cleanup while keeping tests green
8. Quality Review - Select review focuses (interactive), present findings for user selection
9. Summary - Document completion, report test coverage

Key Difference: In TDD, tests are designed BEFORE architecture, and implementation is interleaved with testing per-task.

/architect <feature-description>

Launches the guided 7-phase architecture design workflow (no implementation):