From devflow
Use when starting any conversation — establishes the unified development workflow combining superpowers discipline with dotcontext agents and PREVC workflow
npx claudepluginhub nexuz-sys/devflow --plugin devflowThis skill uses the workspace's default tool permissions.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
DevFlow bridges superpowers (discipline, TDD, brainstorming, code review) with dotcontext (agents, PREVC workflow, project context, multi-tool sync).
<EXTREMELY-IMPORTANT> If you think there is even a 1% chance a DevFlow skill might apply to what you are doing, you ABSOLUTELY MUST invoke it.This is not negotiable. This is not optional. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT>
DevFlow detects your environment at session start and operates in the highest available mode:
| Mode | What's available | Capabilities |
|---|---|---|
| Full | superpowers + dotcontext MCP | PREVC workflow, 15 agents via MCP, semantic context, multi-tool sync |
| Lite | superpowers + .context/ dir | PREVC workflow, agent playbooks (read directly), plans — no semantic/sync |
| Minimal | standalone | Brainstorming, TDD, SDD, code review — linear flow without PREVC phases |
The current mode is injected by the SessionStart hook. All skills adapt their behavior to the active mode.
In Claude Code: Use the Skill tool with the devflow: prefix.
In Cursor: Skills activate via the Skill tool.
In other environments: Check references/tool-mapping.md for platform-specific instructions.
| Skill | When to use |
|---|---|
devflow:project-init | Initialize DevFlow in a new project — scaffolds .context/ (se já existe, delega para context-sync) |
devflow:context-sync | Update existing .context/ docs, agents, and skills with current project state |
devflow:prevc-flow | Start or continue a PREVC workflow — the main orchestrator |
| Skill | PREVC Phase | What it does |
|---|---|---|
devflow:prevc-planning | P | Brainstorming socrático + plan writing, enriched with project context |
devflow:prevc-review | R | Design/code review with agent orchestration |
devflow:prevc-execution | E | Subagent-driven development + TDD + agent handoffs |
devflow:prevc-validation | V | Verification + test/security agents |
devflow:prevc-confirmation | C | Branch finishing + documentation + sync |
| Skill | When to use |
|---|---|
devflow:agent-dispatch | Discover, select, and invoke agents by role for the current task |
devflow:context-awareness | Enrich any task with project context (codebase map, semantic analysis) |
devflow:parallel-dispatch | Coordinate parallel execution of independent tasks |
devflow:autonomous-loop | Story-by-story autonomous execution with specialist agents and escalation |
devflow:napkin | Persistent learning memory — curated runbook of mistakes, corrections, and patterns. Always active. |
| Skill | When to use |
|---|---|
devflow:language | Set conversation language (en-US, pt-BR, es-ES) — all responses switch to selected language |
devflow:config | Configure git strategy and generate .context/.devflow.yaml |
| Command | Action |
|---|---|
/devflow update | Update marketplace, DevFlow, superpowers, and dotcontext in sequence |
| Skill | When to use |
|---|---|
devflow:api-design | Designing, modifying, or reviewing APIs (REST, GraphQL, RPC) |
devflow:bug-investigation | Triaging bugs, investigating unexpected behavior, root cause analysis |
devflow:commit-message | Writing clear conventional commit messages |
devflow:documentation | Writing, updating, or reviewing documentation |
devflow:feature-breakdown | Decomposing large features into implementable chunks |
devflow:git-strategy | Selecting git workflow (branch-flow, worktree, trunk-based), branch protection |
devflow:prd-generation | Generating Product Requirements Documents with phased roadmap |
devflow:pr-review | Creating or reviewing pull requests |
devflow:refactoring | Restructuring code without changing behavior |
devflow:security-audit | OWASP-based security assessment |
devflow:test-generation | Designing test suites, generating test cases, reviewing coverage |
devflow:skill-creation | Creating new DevFlow skills with TDD-for-docs methodology |
devflow:memory-recall | Searching MemPalace for project memories, agent diaries, and historical decisions |
For the complete skills map across all three systems, see references/skills-map.md.
When starting a workflow, DevFlow auto-detects or accepts explicit scale:
| Scale | Phases | Example |
|---|---|---|
| QUICK | E → V | Bug fix, typo, config change |
| SMALL | P → E → V | Simple feature, single component |
| MEDIUM | P → R → E → V → C | Multi-component feature |
| LARGE | P → R → E → V → C + checkpoints | System-wide change, new subsystem |
Control how much human involvement each workflow requires:
| Mode | Syntax | Human Involvement |
|---|---|---|
| supervised | /devflow <desc> (default) | Human approves every phase |
| assisted | /devflow autonomy:assisted <desc> | Human in P+R+V+C, autonomous E |
| autonomous | /devflow auto <desc> | Fully autonomous, escalates on failure |
For existing projects with PRD: Use /devflow auto --from-prd to convert PRD phases into stories.yaml without brainstorming. Stories are enriched with existing .context/docs/ (codebase map, project overview, conventions).
Mid-workflow upgrade: Run /devflow autonomy:autonomous during an active workflow to upgrade. All progress (completed stories, attempts, stats) is preserved — only the execution mode changes.
Autonomy modes feature bidirectional escalation:
| Command | Action |
|---|---|
/devflow [description] | Start a new PREVC workflow (auto-scales) |
/devflow scale:X [description] | Start with explicit scale (QUICK/SMALL/MEDIUM/LARGE) |
/devflow language | Set conversation language interactively |
/devflow language <code> | Set language directly (en-US, pt-BR, es-ES) |
/devflow config | Configure git strategy and generate .context/.devflow.yaml |
/devflow prd | Generate or update product PRD with phased roadmap |
/devflow-status | Show current phase, progress, and available actions |
/devflow-next | Attempt to advance to next phase (checks gates) |
/devflow-dispatch | List available agents for current phase and mode |
/devflow-dispatch <role> | Dispatch a specific agent |
/devflow-sync [scope] | Update .context/ with current project state (docs/agents/skills) |
/devflow auto [description] | Start fully autonomous workflow with smart escalation |
/devflow auto --from-prd | Autonomous from existing PRD (skip brainstorming) |
/devflow autonomy:X [description] | Start with explicit autonomy (supervised/assisted/autonomous) |
/devflow autonomy:X (no desc) | Upgrade/downgrade active workflow's autonomy mode |
/devflow-sync workflow | Validate/scaffold .context/workflow/ directory |
/devflow-recall <query> | Search MemPalace for project memories |
/devflow configdevflow:config skill.context/.devflow.yamlDevFlow invokes superpowers skills when discipline enforcement is needed. These are called automatically by phase skills:
superpowers:brainstorming — via prevc-planningsuperpowers:writing-plans — via prevc-planningsuperpowers:executing-plans — via prevc-execution (when no subagents)superpowers:subagent-driven-development — via prevc-executionsuperpowers:test-driven-development — via prevc-executionsuperpowers:systematic-debugging — via bug-investigationsuperpowers:requesting-code-review — via prevc-review, pr-reviewsuperpowers:receiving-code-review — processing review feedbacksuperpowers:dispatching-parallel-agents — via parallel-dispatchsuperpowers:finishing-a-development-branch — via prevc-confirmationsuperpowers:using-git-worktrees — via prevc-executionsuperpowers:verification-before-completion — via prevc-validationsuperpowers:writing-skills — via skill-creationInvoke devflow:prevc-flow BEFORE any implementation work. Even a 1% chance that a workflow applies means invoke it.
| Thought | Reality |
|---|---|
| "This is just a quick fix" | Use /devflow scale:QUICK — it skips to E→V |
| "I don't need agents for this" | The skill decides that based on mode. Invoke it. |
| "Let me just write the code" | TDD iron law: no production code without failing test first |
| "I'll brainstorm in my head" | No. Brainstorming produces a spec. Specs prevent wasted work. |
| "dotcontext isn't installed" | Lite/Minimal mode handles this. Skills degrade gracefully. |
| "superpowers handles this already" | DevFlow adds PREVC phases, agents, and context. Use both. |