gadd-triage
/gadd:triage
Normalize unclassified intake into a GADD Work Item and route it to implementation, SDD-only design, PRD discovery, or a terminal state.
This command is a standalone, agent-agnostic GADD command. Follow this file directly; do not require brainstorming, grill-me, issue-generation, or external triage skills.
Inputs
/gadd:triage [new|work-item-id|external-ref] [context]
/gadd:triage <free-form intake prompt>
Use /gadd:triage for unclassified incoming work: external issues, bug reports, engineer tasks, support reports, ambiguous requests, and "what should we do with this?" items. It also accepts a plain-language prompt as the source intake, for example /gadd:triage create a new release of this package. Treat that prompt as incoming work to normalize, not as a subcommand. Do not require triage before deliberate PM-led Product Requirement discovery; /gadd:research and /gadd:scope remain valid direct entry points.
When both a Work Item ID and a free-form prompt are supplied (/gadd:triage <work-item-id> <prompt>), treat the free-form prompt as additional triage context for the existing Work Item. Do not replace the existing triage narrative or approved outcome without explicit human confirmation.
Reads
More from awjreynolds/gadd
find-skills
>-
2gadd-implement
Run /gadd:implement to execute one ready GADD Work Item or every ready Work Item under an approved boundary, with built-in Test-Driven Development. Use when the user says /gadd:implement, /gadd:implement <work-item-id>, or /gadd:implement ALL, asks to build, code, test, or ship the next approved Work Item, asks to implement an approved plan slice or vertical slice, or asks to work the child Work Items created by /gadd:decompose. Phrasings to recognize include "build the next approved Work Item", "code and test the ready slice", "implement everything that is ready", and "work the decomposed children". This is the Software Engineering lane gate after /gadd:approve and /gadd:decompose; it hands off to /gadd:verify <work-item-id> and does not close or archive Work Items.
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-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