gadd-research
/gadd:research
Gather PM-grade inputs before PRD scoping and write a sanitized research.md artifact.
This command is a standalone, agent-agnostic GADD command. Follow this file directly; do not require any other installed skill.
Input
/gadd:research [new|draft-id|work-item-id] [trigger or context]
This is a Product Requirement lane command. It accepts direct PM-led product discovery or Work Items routed from triage with state: needs_prd. Reject bug_fix, task, and engineering_change Work Items with a clear route back to /gadd:next <work-item-id> or /gadd:triage <work-item-id>.
If no trigger, draft, Work Item, or context source is provided, ask one direct question for the source product trigger or context. Do not invent a product problem from repository structure alone.
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-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.
2