Stats
Actions
Tags
From rpi-workflow
Research a feature and generate a file with hints for the planning agent
How this command is triggered — by the user, by Claude, or both
Slash command
/rpi-workflow:research-feature feature-idThe summary Claude sees in its command listing — used to decide when to auto-load this command
Read the initial research file in .claude/features/[$1].md that contains the feature description provided by the user. If you can't find the feature file, ask the user to provide the feature description. Then, research the codebase for usefull information about the feature: - If there are existing implementations, you can use them as a reference. - If there are libraries or frameworks that can be used, you can use them as a reference. - If there are README.md files that describe usefull information about the feature, you can use them as a reference. (Reference document pahts, don't copy...
Read the initial research file in .claude/features/[$1].md that contains the feature description provided by the user.
If you can't find the feature file, ask the user to provide the feature description.
Then, research the codebase for usefull information about the feature:
(Reference document pahts, don't copy over the code).
DON'T PROPOSE ANYTHING. NO ESTIMATES. NO PLANS. NO IMPLEMENTATIONS. NO CODE. JUST RESEARCH. DON'T TRY TO TELL THE NEXT AGENT WHAT TO DO, HE KNOWS. NO TODOs.
Once you have gathered all the information, return the research in a file called .claude/research/[$1].md.
npx claudepluginhub victor-barbera/cc-marketplace --plugin rpi-workflow/researchResearches features by discovering codebase patterns/gaps/errors/dependencies, recommending libraries/best practices; creates PRD folder with internal/external findings, summary, and metadata. Supports PRD-scoped iteration and refinement.
/flow-researchConducts pre-PRD research on <topic>: classifies type, explores codebase with Glob/Grep tools, maps patterns/dependencies with file:line refs, outputs structured markdown reports.
/planCreates detailed implementation plans interactively through research docs, file reads, and user dialog for features, refactors, or integrations.
/featureCreates detailed implementation spec in .claude/specs/*.md for given feature-description after deep codebase analysis.
/archStarts collaborative feature specification process: investigates codebase for patterns and constraints, proposes design with reasoning and file paths, resolves ambiguities via conversation, saves Markdown spec with behavior, architecture, constraints, and related files.
/sc-workflowGuides feature development via phases: codebase exploration with agents, clarifying questions, architecture design, and step-by-step implementation.