dag

Plugin dag from marketplace dag-engineering in AaronAbuUsama/dag-engineering. Commands read from the repo's manifest — 1 month ago.

Skills (13)

• chart

  Internal planning move reached through dag:plan — turn a grilled or specced plan into a DAG of GitHub issues with native blocking edges. Do not invoke directly outside the planning router.

• diagnose

  Find the one design gap behind a cluster of review findings and return a consolidating fix or a pre-validated escalation. Use when a bug-class recurs, or when a fix needs a new mechanism rather than a tightened check.

• execute

  The execution door — walks a pre-flight-signed DAG or required Atlas portfolio, dispatching each node behind the merge gate, climbing the escalation ladder on findings, and driving every node to done-clean, wave by wave.

• feedback

  Capture a DAG Engineering workflow failure, wrong route, lost state, or contradicted contract with reproducible evidence and return it to the dag-plugin source repository. Use when the user asks to record feedback or an observed DAG failure should become an actionable upstream report.

• grill-deep

  Internal planning move reached through dag:plan — run the batched, code-grounded interview and record durable ADRs and glossary entries. Do not invoke directly outside the planning router.

• grill

  Internal planning move reached through dag:plan — sharpen a plan through a batched, code-grounded interview. Do not invoke directly outside the planning router.

• plan

  The planning door — reads Atlas and chart state from GitHub, resolves destination fog when necessary, and runs the next move through to the pre-flight signature that hands one expedition to execution.

• preflight

  Internal planning gate reached through dag:plan — validate every node's invariants, criteria, edges, and proof contract before dispatch. Do not invoke directly outside the planning router.

• prototype

  Build the throwaway spike that de-risks a DAG node. Use when a node's readiness is needs-prototype, or when another dag skill raises a spike against a node.

• prove

  Put the evidence in the pull request — what the surface calls for, a committed receipt, and a tier table a reviewer can check. Use when opening or updating a PR, when asked to fix something and report back, when about to say a change works, when a merged node owes its proof, or when screenshots or v

• replan

  Internal planning move reached through dag:plan when pre-flight or execution stops a chart — classify whether the node, validation method, or destination failed, then return the work to the correct planning level. Do not invoke as a public door.

• research

  Settle a DAG node's open fact against primary sources and capture the findings as a Markdown file in the repo. Use when a node's readiness is needs-research, or when another dag skill dispatches a research node.

• setup

  One-time repo configuration for the DAG suite — confirms GitHub native blocking, creates the label vocabulary chart and execute rely on, and lays out domain docs. Run once, before the planning door.

Similar plugins