From ticket-flow
Document the codebase as it exists today to answer a research question, by spawning parallel read-only sub-agents and synthesizing their findings into thoughts/. Use before planning any non-trivial change, or via /ticket-flow:research.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ticket-flow:researchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build a factual map of the parts of the codebase relevant to: **$ARGUMENTS**
Build a factual map of the parts of the codebase relevant to: $ARGUMENTS
codebase-researcher sub-agent once per area, in parallel
(multiple Task calls in one turn). Give each a tight scope and ask it to return
file:line citations.thoughts/shared/research/<topic>.md, including:
path/to/file.ext:line references,The written research is the durable artifact the planning phase reads — it keeps context out of the live window and grounded in real code.
npx claudepluginhub alexanderop/ticket-flowCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.