dag-workflow

Plugin dag-workflow from marketplace claude-dag-workflow in HyunjunJeon/claude-workflow-mods. Commands read from the repo's manifest — 4 days ago.

Skills (8)

• anti-slop

  Discipline that keeps meaningless code out of a change in any language - dead weight whose removal changes no behavior, types and casts that throw away what the code knows, module-patching tests, and Clean Code readability calls - loaded through load_skills by nodes that write code and by review-sta

• debugging

  Discipline for DAG nodes that diagnose or fix a failing behavior, loaded through load_skills. A node prompt asks the worker to find the cause of a bug, a failing test or a performance regression, or to fix one using a reproduction command produced by an earlier node.

• interview

  User-invoked only; aligns on a vague request through rounds of numbered questions with recommended answers before a DAG is planned, and ends with a confirmed goal and acceptance criteria.

• planning

  Mandatory planning doctrine for dag-workflow. Load it BEFORE the first mcp__dag-workflow__dag start or amend in a session - the plugin refuses that start until this skill is loaded. Covers turning a task into a dependency-ordered DAG of subagent nodes, how results flow along dependsOn, the node prom

• pm

  User-invoked only; interviews the user as product owner, sorts every question into product decision, technical decision or unknown, and has a one-node DAG write the PRD.

• review-standards

  Standards-axis review discipline for DAG review nodes, loaded through load_skills - pin the diff, find the documented coding standards, apply a Fowler smell baseline as labelled judgment calls, and report a PASS or FAIL standards verdict. A DAG node, typically named review-standards, whose prompt as

• secure-coding

  Security-axis discipline for DAG nodes, loaded through load_skills - lens nodes find candidate breaches of the chosen guides (KISA, OWASP with CWE Top 25, or agent trust boundaries), one verifier node per candidate tries to refute it, and review-security compiles the PASS or FAIL verdict. A DAG node

• testing

  How DAG nodes prove code changes through public interfaces - red before green for new behavior and bug fixes, preservation checks for refactors, and mocks at system boundaries - loaded through load_skills. A DAG node writes or changes code and has to prove the change with tests, so its prompt lists