From research
Synthesize research findings into a clear problem statement and research plan
How this skill is triggered — by the user, by Claude, or both
Slash command
/research:defineThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Converge the broad discovery findings on "$ARGUMENTS" into a focused problem statement, "How Might We" questions, and a research plan for the solution phase.
Converge the broad discovery findings on "$ARGUMENTS" into a focused problem statement, "How Might We" questions, and a research plan for the solution phase.
Read .metapowers/research/$ARGUMENTS/01-discover.md. If this file does not exist, tell the user:
Phase 1 (Discover) has not been completed for "$ARGUMENTS". Run
/research:discover $ARGUMENTSfirst, or use--skip-checksto bypass.
If --skip-checks is present in $ARGUMENTS, skip this check and log to .metapowers/research/$ARGUMENTS/skip-log.md.
Read context files:
.metapowers/research/$ARGUMENTS/01-discover.md for discovery findingsplugins/research/shared/double-diamond-guide.md for methodology referenceplugins/research/shared/research-plan-template.md for output structureSynthesize findings:
Formulate the problem statement:
Generate "How Might We" questions:
Define success criteria and scope:
Write the artifact to .metapowers/research/$ARGUMENTS/02-define.md following the research plan template structure.
The problem definition written to .metapowers/research/$ARGUMENTS/02-define.md. Present a summary to the user highlighting:
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub bromso/metapowers --plugin research