dev-flow-guide

Dev-Flow Delivery Pipeline Skill

You have access to the dev-flow plugin commands that cover the full feature delivery workflow. When a developer asks about any stage of the pipeline, identify which command applies and invoke it via the Skill tool.

Pipeline Overview

init-dev-flow          ← one-time repo setup
create-prd             ← interactive PRD interview
review-prd             ← validate PRD before speccing
create-spec            ← build spec directory from PRD
review-spec            ← validate spec before implementation
implm-frm-prd          ← full 13-step pipeline from PRD (create-spec → review-spec → implm-from-spec)
implm-from-spec        ← full 11-step orchestrated implementation from an existing spec
implm-frm-change-dtls  ← full 15-step pipeline from a Jira ticket or change description
create-review          ← produce a structured code review artifact for the branch
review-code            ← code review against spec or PRD
write-flow-analys      ← final process analysis report (part of implm-from-spec)
archive-spec           ← move completed spec to specs/archive/

Command Map

What the developer asks about	Command to invoke
Set up dev-flow in this repo for the first time	/dev-flow:init-dev-flow
Write / create a PRD for a new feature	/dev-flow:create-prd
Review a PRD	/dev-flow:review-prd
Create a spec from a PRD	/dev-flow:create-spec
Review a spec	/dev-flow:review-spec
Implement from a spec that already exists	/dev-flow:implm-from-spec
Implement starting from a PRD (no spec yet)	/dev-flow:implm-frm-prd
Implement from a Jira ticket or change request	/dev-flow:implm-frm-change-dtls
Create a code review for the current branch	/dev-flow:create-review
Review the code on the current branch	/dev-flow:review-code
Write a process analysis for a completed feature	/dev-flow:write-flow-analys
Archive a completed spec directory	/dev-flow:archive-spec

How to Respond

1. Identify which stage of the pipeline the developer is at.
2. If the request is unambiguous, invoke the matching command directly via the Skill tool.
3. If the developer is starting from scratch (no PRD, no spec), recommend: init-dev-flow (if first time) → create-prd → implm-frm-prd.
4. If they have a Jira ticket, invoke implm-frm-change-dtls directly.
5. For ambiguous requests, ask where they are in the pipeline before invoking anything.

Scope

All commands operate on local files in the current repository. Jira integration requires the Atlassian MCP server; fall back to asking the user to paste ticket details if it is unavailable.