gadd-implement
/gadd:implement
Execute one ready Work Item, or every ready Work Item under an approved boundary.
This command is a standalone, agent-agnostic GADD command. Follow this file directly; do not require any other installed skill.
Input
/gadd:implement <work-item-id>
/gadd:implement ALL
The <work-item-id> form selects exactly that Work Item. The ALL form selects every ready Work Item under the current approved boundary and implements them in dependency-safe order. If neither form is provided, stop and ask which target the user wants.
Reads
More from awjreynolds/gadd
find-skills
>-
2gadd-archive
Run /gadd:archive to move already-closed GADD Work Item packages into the local archive directory after /gadd:close. Use when the user says /gadd:archive, asks for cleanup after close, asks to move closed Work Items out of the active tree, asks to tidy gadd/work-items, or says things like "archive this closed Work Item", "clean up after close", or "shrink the active Work Item list". Archive is optional storage hygiene; it never decides closure readiness and never mutates external trackers.
2gadd-next
Run /gadd:next for a GADD Work Item. Use when the user says /gadd:next, asks for the next GADD command, or wants to diagnose workflow state from repo-local ledgers.
2gadd-approve
Run /gadd:approve for a GADD Work Item. Use when the user says /gadd:approve or wants to approve a PRD, SDD, or plan from repo-local ledger state.
2gadd-triage
Run /gadd:triage for unclassified GADD intake. Use when the user says /gadd:triage, provides a free-form work prompt or external issue, reports a bug, asks what to do with an issue, or wants to route a task, bug, engineering change, or ambiguous request into GADD.
2gadd-research
Run /gadd:research before GADD scoping when inputs are weak, sensitive, or need codebase investigation. Use when the user says /gadd:research or wants to gather PM-grade inputs before a PRD.
2