Skip to content
Back to skills

Define

ASecurity

Synthesize research findings into a clear problem statement and research plan

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
ai-agents

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add bromso/metapowers --skill define --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Define?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Define
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bromso-define/badge)](https://www.skillsdirectory.com/skills/bromso-define)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: Synthesize research findings into a clear problem statement and research plan
---

# Define

Converge the broad discovery findings on "$ARGUMENTS" into a focused problem statement, "How Might We" questions, and a research plan for the solution phase.

## Prerequisites

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 $ARGUMENTS` first, or use `--skip-checks` to bypass.

If `--skip-checks` is present in $ARGUMENTS, skip this check and log to `.metapowers/research/$ARGUMENTS/skip-log.md`.

## Process

1. **Read context files:**
   - Read `.metapowers/research/$ARGUMENTS/01-discover.md` for discovery findings
   - Read `plugins/research/shared/double-diamond-guide.md` for methodology reference
   - Read `plugins/research/shared/research-plan-template.md` for output structure

2. **Synthesize findings:**
   - Review all themes from the Discover phase
   - Identify the core tension or unmet need
   - Distinguish root causes from symptoms
   - Map relationships between themes

3. **Formulate the problem statement:**
   - Write a clear, specific, actionable problem statement
   - Avoid solution-language (the problem, not the answer)
   - Ensure it's scoped enough to be solvable

4. **Generate "How Might We" questions:**
   - Create 3-5 HMW questions that reframe the problem as opportunities
   - Each HMW should open a different solution direction
   - Avoid HMW questions that are too broad or too narrow

5. **Define success criteria and scope:**
   - What does "solved" look like? Specify measurable criteria
   - What's in scope and out of scope for the Design phase?
   - Identify constraints and assumptions

6. **Write the artifact** to `.metapowers/research/$ARGUMENTS/02-define.md` following the research plan template structure.

## Output

The problem definition written to `.metapowers/research/$ARGUMENTS/02-define.md`. Present a summary to the user highlighting:
- The problem statement
- Top HMW questions
- Key scope decisions
- Recommended focus for the Design phase

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.