devflow

Plugin devflow from marketplace devflow in FaerberK/devflow-mcp. Commands read from the repo's manifest — 1 month ago.

Skills (24)

• devflow-adr-compliance

  Use during the review state of a flow with file changes. Compares the diff against accepted ADRs' affects_paths globs, persists per-file violations, and emits a discipline-token only when every violation is either resolved or explicitly marked break-by-design with a reason ≥ 10 characters. Implement

• devflow-area-ideation

  Use when the user pasted an Area-Idea-Hunt-Prompt from the IdeasPage Garage. Drives a Wiki-grounded ideation routine — never out-of-thin-air-brainstorming, every idea must reference real wiki entries. Output is 3 Pick&Plan-ready proposals as JSON.

• devflow-collision-acknowledged

  Use during planning state to walk the user through the awareness list (pending_work + planning_context) so every in-flight flow, open intent, proposed ADR, and pending draft in the topic-scope receives an explicit user decision (✓ keep / ✗ irrelevant / ↺ later). Emits a discipline-token at the end a

• devflow-core

  Use whenever working in a DevFlow-managed project (CLAUDE.md contains devflow_init). Explains the flow-state machine, init requirements, and error recovery.

• devflow-debugging

  Use when an unexpected behavior, failing test, or production-error needs to be diagnosed. Walks through four phases — Investigation → Pattern → Hypothesis → Fix — with an explicit Knowledge-Hook 4 runbook-match before the Hypothesis phase to avoid double-debugging known incidents.

• devflow-error-investigator

  Use FIRST when you encounter an unexpected error / exception / failing test that's not immediately obvious. Calls `error_context_get` to pull all wiki signals relevant to the error (runbooks, ADRs touching the file, recent flows, patterns, similar past errors). Iron Law of compounding wikis: every n

• devflow-executing

  Use when the active DevFlow flow is in 'in_progress' state. Guides implementing the approved plan with tasks, commits, and TDD discipline.

• devflow-flow-display

  Use whenever listing flows, presenting flow status, or summarizing the flow backlog. Enforces a uniform Markdown-table format across MCP-tool, slash-commands, and free-form agent responses so the user gets a consistent view everywhere.

• devflow-idea-curator

  Use periodically (monthly cadence is plenty) to curate the project's idea backlog. Reads `GET /api/projects/:id/ideas` — five sources of organic ideas (intents, stale, orphans, contradictions, hotspots). For each item: pick & plan into a flow, defer with a substantive horizon, or reject with a reaso

• devflow-knowledge-completer

  Use during planning, before submitting to approval, and again before review→done. Walks the gaps from `wiki-context` and ensures each gap is closed with `extend` (preferred), a new entry, or a deferred intent — never `dismiss`. The wiki is a compounding artifact: knowledge is never thrown away.

• devflow-pattern-reuse

  Use during the planning state to surface existing project patterns that match the flow's tag-scope, so the implementation plan re-uses proven solutions instead of inventing parallel ones. Cites each accepted pattern via `[[pattern:slug]]` wiki-link in the plan.

• devflow-plan-reconciliation

  Use during the review state, before devflow-verification-gate, to reconcile the approved implementation_plan against what was actually implemented. Produces a per-AC and per-section table — done / partial / missing / extra — and forces the agent to address every gap (either fix it now, file an inten

• devflow-planning

  Use when the active DevFlow flow is in 'planning' state. Guides creating an implementation plan with acceptance criteria before submitting for approval.

• devflow-receiving-review

  Use when receiving a code-review (from a subagent dispatch or a human reviewer) to triage every finding into Critical / Important / Minor with a deliberate decision per item. Each finding is technically verified before accept-or-reject — never blind acceptance, never blind rejection.

• devflow-reviewing

  Use when the active DevFlow flow is in 'review' state. Guides self-review via diff analysis and writes the agent summary + testing instructions.

• devflow-tdd

  Use during implementation to drive every change through Test-Driven Development. Before writing production code, query existing test-patterns from the LLM-Wiki (Hook 3) for the relevant tag-scope, then write a failing test (RED), make it pass (GREEN), and refactor (REFACTOR). Emits a discipline-toke

• devflow-verification-gate

  Use during the review state to prove every acceptance criterion with a captured evidence command. No "should work" claims — each AC gets a real shell/test/curl invocation whose stdout is recorded into the flow's testingInstructions. Emits the discipline-token that makes review→done possible under ag

• devflow-wiki-lint

  Use periodically (or on demand from the Wiki page health-bar) to keep the LLM-Wiki clean. Reads `GET /api/projects/:id/wiki-lint` and addresses every reported stale, orphan, and contradiction — never let any of them linger. Iron Law: orphans get cross-linked or marked as `intent`, contradictions are

• devflow-worktrees

  Use at the start of implementation (or when picking up an existing flow) to set up a dedicated git-worktree under .claude/worktrees/<displayId>-<slug>. Each flow gets its own working directory — branch isolation prevents cross-flow contamination, and the path is predictable for re-init / cross-sessi

• devflow-code-critic

  Use during in_progress state, before submitting flow_update({currentState: 'review'}), to deeply review the implementation against 7 quality dimensions. The skill enforces a critic-persona — the agent steps out of "implementer" mode and into "reviewer" mode. Outputs a structured verdict (approved |

• devflow-draft-triage

  Use in the 'review' state to triage pending knowledge_drafts before review→done. Decides per draft: accept (new wiki entry) or reject (with substantive reason). Iron Law extend > dismiss applies — never wegklick a draft whose topic has an existing extend-target.

• devflow-flow-attachment

  Use when the user asks you to attach a file to a flow ("häng X an", "attach to DF-XXX", "save this to the flow", "upload this"). Picks the right MCP tool (flow_upload for text, flow_upload_file for binaries) and the right kind. Iron law — never silently compress or truncate, prefer fail loud over co

• devflow-plan-critic

  Use during planning state, before submitting flow_update({currentState: 'approval'}), to deeply review the plan against 7 quality dimensions. The skill enforces a critic-persona — the agent steps out of "author" mode and into "reviewer" mode. Outputs a structured verdict (approved | minor_issues | n

• devflow-subagent-driven-dev

  DRAFT-SKELETON. Tier-2 Pilot. Future skill for delegating in_progress tasks to per-task sub-agents in isolated worktrees. NOT YET ACTIVE — RFC sign-off via DF-427 closed Q1-Q7. Skill remains status:draft until the implementation roadmap (8 sub-flows, 3-4 weeks) lands.

Slash commands (8)

• /devflow:devflow-create

  Create a new flow with a one-line summary

• /devflow:devflow-list

  List open flows as a Markdown table (⭐ marks own flows)

• /devflow:devflow-loop

  Run a flow autonomously until every backend gate is green

• /devflow:devflow-next

  Show the next allowed action and step for the current flow

• /devflow:devflow-review

  Submit the current flow for review (transitions to 'review' state)

• /devflow:devflow-start

  Start a DevFlow session for a specific flow

• /devflow:devflow-status

  Show the current DevFlow status (state, tasks, next step)

• /devflow:devflow-tasks

  List tasks for the current DevFlow flow

MCP servers (1)

• devflow

  runs: node ${CLAUDE_PLUGIN_ROOT}/dist/index.js

Similar plugins