dev-workflows

A set of slash commands and review agents for moving a software product from an idea through requirements, design, implementation, documentation, and release. It also turns business requirements documents into product and engineering documents.

In plain words
What is it for?
Use it to create and update product requirements, architecture decisions, specifications, designs, implementation plans, documentation, security reviews, and release notes.
Why use it?
Product work can become fragmented when plans, specifications, code, and release preparation are handled separately. The workflow connects these stages and checks each handoff before the next one begins.

Plugin for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Claude Code
/plugin marketplace add ihudak/ihudak-claude-plugins
agentmods
npx agentmods add plugins/ihudak/ihudak-claude-plugins/dev-workflows
Clone the repo
git clone --depth 1 https://github.com/ihudak/ihudak-claude-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

dev-workflows scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/dev-workflows/.claude-plugin/plugin.json · 28 lines

What it actually says

{
  "name": "dev-workflows",
  "version": "3.3.1",
  "description": "Twenty-seven slash commands for the product lifecycle — /idea → /create-prd → /create-ard → /specify → /design → /epics → /implement → /document → /release-notes → /ready — plus a BRD-to-PRD route (/brd-intake → /brd-ground → /brd-split → /brd-interview → /brd-package → /brd-reconcile) that grounds a customer BRD, decides it with the customer, and seeds /create-prd, /create-ard and /specify via --from-brd. Also /vuln, /upgrade, /update-prd, /docs-profile, /api-guideline-reviewer, /guideline-reviewer, /statusline, /feedback and /prompt. Thirty-nine subagents, four hooks. Opus-backed gates review every artifact — plans, code, docs, Epics, specs, designs, ARDs, PRDs, readiness. Each phase hands its artifact to the next on the specs repo's default branch: the producer opens a PR; the consumer refuses to start until it lands. Optional read-only grounding on product docs, prior art and code.",
  "author": {
    "name": "Ivan Gudak",
    "email": "[email protected]"
  },
  "homepage": "https://github.com/ihudak/ihudak-claude-plugins/tree/main/plugins/dev-workflows",
  "repository": "https://github.com/ihudak/ihudak-claude-plugins",
  "license": "MIT",
  "keywords": [
    "implement",
    "document",
    "vuln",
    "upgrade",
    "development",
    "workflow",
    "security",
    "dependencies",
    "guidelines",
    "api-review",
    "value-increment",
    "update-prd",
    "brd"
  ]
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 28 lines scan A 71913ec0b829

Subscribe to this mod's changes

dev-workflows is a plugin published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.