BRD customer-package workflow (PM phase, fifth command of the BRD-to-PRD route). Gates on the BRD's decisions being merged and on every interview question carrying a terminal disposition or the held-for-the-customer holding state, then runs an adversarial self-review through brd-package-reviewer and refuses to build a…
BRD reconciliation workflow (PM phase, sixth and last command of the BRD-to-PRD route). Takes the customer's returned review from anywhere, copies it into the BRD folder under the canonical name and commits it before anything reads it, then dispatches customer-review-reader in schema or free-text mode. Confirms every…
BRD-splitting workflow (PM phase, third command of the BRD-to-PRD route). Gates on every grounding finding carrying a verifier verdict, proposes candidate slices from the grounded picture (buildable now, blocked, or dependent), keys and nests a child BRD folder per confirmed slice with its own brd-link.md, inherited…
Architecture-authoring workflow (Product Architect phase, sub-project 3 of the PRD-creation flow). Grounds on the mounted implementation repos (architect-driven discovery — no PRs) and authors an ARD for a PRD (/create-ard ) or an Epic (/create-ard , inheriting the PRD-level ARD), against references/ard-format.md…
PRD-creation workflow (PM phase, sub-project 2 of the PRD-creation flow). Turns a refined idea.md + a user-supplied JIRA-KEY into a high-quality Product Requirements Document document (spine + adapt-in profiles --lean|--hybrid|--full), authored via a relentless grill against references/prd-format.md, gated by the Opus…
Jira-driven engineering-design workflow (Dev phase). Takes over a merged specification.md from the specs repo's main branch, grounds strictly in the fully-mounted implementation code, and authors a reviewed engineering design.md through a relentless one-question-at-a-time grill that challenges the spec and designs the…
Scan a documentation repository and write/refresh a machine-readable docs-profile (.dev-workflows/docs-profile.yml) plus complementary CLAUDE.md guidance, as a reviewable PR. Captures content roots, per-space dev-servers and lint/build/format commands, templating tokens, links, announcement pages, branch-naming…
Jira-driven feature-documentation workflow. Phase 0 preflight-discovers the docs repo + profile (in-repo → built-in example-docs default → on-demand /docs-profile) and the PRD's specs dir under /workspace. Reads a Product Requirements Document hierarchy from exported markdown, resolves PR diffs in parallel…
Jira-driven Epic-writing workflow. Reads a Product Requirements Document and existing Epics from exported markdown, optionally scans code repos, drafts child Epic definitions, and gates on prose-style-checker and Opus epic-reviewer.
Log a manual note about the dev-workflows plugin itself — friction you hit or an improvement you want — to the per-PRD feedback file in the specs repo, for the plugin maintainer to aggregate. Tied to no command; run any time.
Review app code and UI for compliance with public UI design-system and accessibility standards. Checks app header, data table, filter field, connections, permissions, settings, dashboards, accessibility, and data naming.
Idea-refinement workflow (PM phase, front of the PRD-creation flow). Takes one source — an inline prompt, a markdown file (with wikilinks/images), a community post, or an exported Jira ticket (product feedback, or an existing Product Requirements Document the idea extends, parallels, or rewrites) — and, through a…