From devflow
Explains the DevFlow SDLC workflow — what commands are available, how they connect, and the recommended order of operations. Use this when the user asks things like "how does DevFlow work," "what's the workflow," "show me the DevFlow commands," "what should I run next," or "walk me through the SDLC process."
npx claudepluginhub joshuarweaver/cascade-code-general-misc-4 --plugin codingthefuturewithai-claude-code-primitivesThis skill is limited to using the following tools:
A streamlined development workflow broken into focused phases with human-in-the-loop decision points.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
A streamlined development workflow broken into focused phases with human-in-the-loop decision points.
Multi-Backend Support: DevFlow works with Jira or GitLab Issues, Confluence or Google Drive, and GitHub PRs or GitLab MRs.
Ask the user which scenario they're in:
When: Starting from zero, problem not fully defined, tech stack undecided
Workflow: Upstream SDLC → Scaffolding → Build Cycle
When: Already know what you're building (framework, architecture decided)
Workflow: Scaffolding → Documentation → Build Cycle
When: Codebase exists but lacks documentation
Workflow: Reverse Engineering → Build Cycle
Scan both build and pm directories to find all available commands.
[Use Glob to find all .md files in:
- ${CLAUDE_PLUGIN_ROOT}/commands/build/
- ${CLAUDE_PLUGIN_ROOT}/commands/pm/
]
[Exclude: workflow-guide.md (this file), reference/ subdirectories]
[For each file, read first 10 lines to extract frontmatter: description, argument-hint]
DevFlow has TWO main workflows depending on entry path:
discover → define-prd → define-architecture → plan-iterations → [scaffold] → build cycle
↓ ↓ ↓ ↓ ↓ ↓
Problem WHAT/WHY HOW/WHY Break into Setup Feature
Framing Requirements Tech Decisions Buildable Codebase Development
Issues
fetch-issue → plan-issue → implement-issue → security-review → complete-issue → post-merge
↓ ↓ ↓ ↓ ↓ ↓
Fetch & Branch + Execute Security PR/MR + Cleanup
Analyze Plan Mode Plan Scan Close Issue & Sync
(Recommended)
Build cycle phases:
Based on the user's entry path, show the appropriate workflow:
# 1. Create planning directory
mkdir my-project-planning
cd my-project-planning
git init
# 2. Run upstream SDLC
/devflow:pm:discover
# → Captures problem statement, stores in .devflow/
/devflow:pm:define-prd
# → Creates PRD from discovery, stores in .devflow/
/devflow:pm:define-architecture
# → Makes tech decisions (e.g., "Laravel + MySQL + Vue")
# → Tells you: "Scaffold Laravel at ../my-project"
# 3. Scaffold (following architecture decision)
cd ..
composer create-project laravel/laravel my-project
cd my-project
# 4. Move planning work into scaffolded repo
mv ../my-project-planning/.devflow .
# Now .devflow/ contains: problem statement, PRD, architecture.md, project.md
# 5. Create iterations and issues
/devflow:pm:plan-iterations
# → Breaks PRD into buildable issues
# → Creates milestones in GitLab (or sprints in Jira)
# → Creates issues linked to PRD requirements
# 6. Start build cycle
/devflow:build:fetch-issue PROJ-1
/devflow:build:plan-issue PROJ-1
/devflow:build:implement-issue PROJ-1
# ... continue with complete-issue, post-merge
# 1. Scaffold immediately (you already know the stack)
composer create-project laravel/laravel my-project
cd my-project
git init
# 2. Document decisions retroactively
/devflow:pm:discover
# → Records the problem (why this project exists)
/devflow:pm:define-prd
# → Documents requirements
/devflow:pm:define-architecture
# → Documents "why Laravel" and architecture decisions
# 3. Create iterations and issues
/devflow:pm:plan-iterations
# 4. Start build cycle
/devflow:build:fetch-issue PROJ-1
/devflow:build:plan-issue PROJ-1
# ... continue
# 1. Navigate to existing codebase
cd existing-laravel-app
# 2. Generate documentation for Claude
/devflow:foundation:generate-claude-md
# → Creates CLAUDE.md + .claude/rules/ based on what EXISTS
# → Does NOT enforce team conventions (documents reality)
# 3. (Optional) Document architecture decisions
/devflow:pm:define-architecture
# → Reverse engineers and documents existing architecture
# → Creates ADRs for major decisions already made
# 4. Create new issues as needed
/devflow:build:create-issue "Add compression feature"
# 5. Start build cycle
/devflow:build:fetch-issue PROJ-42
/devflow:build:plan-issue PROJ-42
# ... continue
Supported Backends:
| Component | Options |
|---|---|
| Issues | Jira, GitLab Issues |
| Documentation | Confluence, Google Drive, RAG Memory |
| VCS | GitHub (PRs), GitLab (MRs) |
Run /devflow-setup to configure your backends.
Present commands grouped by workflow phase:
| Command | Purpose | Next Step |
|---|---|---|
/devflow:pm:discover | Problem framing and prior art search | define-prd |
/devflow:pm:define-prd | Create/update Product Requirements Document | define-architecture |
/devflow:pm:define-architecture | Tech stack decisions and architecture design | plan-iterations or scaffold |
/devflow:pm:plan-iterations | Break PRD into buildable issues | fetch-issue (start build cycle) |
| Command | Purpose | Next Step |
|---|---|---|
/devflow:build:create-issue | Create new issue in tracker | fetch-issue |
/devflow:build:fetch-issue | Fetch and analyze issue feasibility | plan-issue |
/devflow:build:plan-issue | Create implementation plan | implement-issue |
/devflow:build:implement-issue | Execute approved plan | security-review or complete-issue |
/devflow:build:security-review | Security analysis (recommended) | complete-issue |
/devflow:build:complete-issue | Create PR/MR, close issue | post-merge (after merge) |
/devflow:build:post-merge | Cleanup after merge | Ready for next issue |
| Command | Purpose | When to Use |
|---|---|---|
/devflow-setup | Configure backends | First-time setup |
/devflow:foundation:generate-claude-md | Create CLAUDE.md for repo | Path C (legacy) or after scaffolding |
/devflow:foundation:capture-conventions | Capture team standards | Periodically to update conventions |
/devflow:foundation:audit-conventions | Compare repo vs conventions | Check alignment with team standards |
Generic & Pattern-Driven
Backend-Agnostic
Type-Aware Planning
Human-in-the-Loop
After Fetch:
After Planning:
After Implementation:
After Security Review:
After Complete:
First-time setup:
/devflow-setup
This wizard will:
View/change config:
~/.claude/plugins/config/devflow/config.md/devflow-setupThe references/ subdirectory contains example issues:
FEATURE-EXAMPLE.md - Example Feature/Executable Spec issueBUG-EXAMPLE.md - Example Bug issueREFERENCE.md - Issue standards reference