Design
Generate and evaluate multiple solution concepts for the defined problemFrom its SKILL.md
npx -y skills add bromso/metapowers --skill designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.7 KB, 637 tokens by cl100k_base, as published. Nobody here has run it
Design
Diverge on solutions for "$ARGUMENTS". Generate multiple solution concepts, evaluate feasibility, and prioritize the most promising approaches.
Prerequisites
Read .metapowers/research/$ARGUMENTS/01-discover.md and .metapowers/research/$ARGUMENTS/02-define.md.
If 02-define.md does not exist, tell the user:
Phase 2 (Define) has not been completed for "$ARGUMENTS". Run
/research:define $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.
Process
-
Read context files:
- Read
.metapowers/research/$ARGUMENTS/01-discover.mdfor research findings - Read
.metapowers/research/$ARGUMENTS/02-define.mdfor problem statement, HMW questions, and success criteria - Read
plugins/research/shared/double-diamond-guide.mdfor methodology reference
- Read
-
Research existing solutions:
- Use WebSearch to find case studies, best practices, and proven approaches related to each HMW question
- Use WebFetch to read detailed implementations or methodologies
- Note what worked, what failed, and why
-
Generate solution concepts:
- Create 3-5 distinct solution concepts, each addressing the problem statement from a different angle
- For each concept: describe the approach, key components, and how it addresses the HMW questions
- Include at least one unconventional or contrarian approach
-
Evaluate each concept:
- Feasibility: How realistic is implementation? What resources are needed?
- Impact: How well does it address the problem statement and success criteria?
- Effort: What's the relative effort to implement?
- Risk: What could go wrong? What assumptions are being made?
-
Prioritize and recommend:
- Rank concepts by impact/feasibility balance
- Recommend top 1-2 concepts for validation in the Deliver phase
- Explain trade-offs between the top options
-
Write the artifact to
.metapowers/research/$ARGUMENTS/03-design.mdwith sections:- Problem Recap — one-paragraph summary from Define
- Solution Concepts — each concept with description and rationale
- Evaluation Matrix — feasibility, impact, effort, risk per concept
- Recommendations — top concepts with reasoning
- Validation Plan — what to test in the Deliver phase
Output
The solution concepts written to .metapowers/research/$ARGUMENTS/03-design.md. Present a summary to the user highlighting:
- Number of concepts generated
- Top recommendation and why
- Key trade-offs between top options
- What needs validation in the Deliver phase
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.