Frame Opportunities

Name: Frame Opportunities
Author: tomzx

ASecurity

Convert discovery inputs into a scored opportunity-solution tree. Produces the artifact the first PDLC gate evaluates.

10 stars

0 votes

0 copies

0 views

Added 10/6/2026

testinggotesting

Security Analysis

A100/100

Scanned 10/6/2026

$npx -y skills add tomzx/agents --skill frame-opportunities --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Frame Opportunities?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Frame Opportunities

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tomzx-frame-opportunities/badge)](https://www.skillsdirectory.com/skills/tomzx-frame-opportunities)

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

Download with Pro

Files

SKILL.md

---
name: frame-opportunities
description: Convert discovery inputs into a scored opportunity-solution tree. Produces the artifact the first PDLC gate evaluates.
argument-hint: "[initiative-id]"
---

# Frame Opportunities

The final step of Discover. This skill takes `problems.md`, `market.md`, and `competitors.md` and builds an opportunity-solution tree: the desired outcome at the top, opportunities beneath, and candidate solutions under each, scored so the gate can decide what to pursue.

This is the artifact the **Discover gate** evaluates. A low score here should route back to discovery, not forward to validation.

## Prerequisites

- Apply the shared PDLC conventions in `skills/pdlc/references/shared.md`.
- `problems.md`, `market.md`, and `competitors.md` from the other Discover skills.

## Steps

1. State the desired outcome (the customer/business result), not a feature.
2. Branch into 3-7 opportunities that could move that outcome. Each opportunity is a change you can make, not a solution.
3. Under each opportunity, list 2-4 candidate solutions (these are provisional — Validate will test the riskiest assumptions, not pick a solution yet).
4. Score each opportunity on a transparent rubric: customer value, strategic fit (to `goals.md`), reach, and confidence. Record the score, not just a gut ranking.
5. Recommend the opportunity (or two) to carry into Validate, with the one or two riskiest assumptions called out for testing.
6. Write `opportunity-tree.md` to the initiative directory.

## Output Format

Use the template at `skills/pdlc/templates/initiatives/opportunity-tree.md`. Carry the standard initiative frontmatter with `phase: discover`.

## Outcome

If `$OUTCOME_YAML` is set, emit `verdict: drafted` plus `reason`.

## Completion Checklist

- [ ] Desired outcome stated as a result, not a feature
- [ ] Each opportunity is a change you can make, distinct from the others
- [ ] Each opportunity scored on a stated rubric (not just ranked)
- [ ] The riskiest assumptions to test are explicitly named for Validate

## Next Step

Run the **Discover gate** via `make-decision`. On `proceed`, load `map-assumptions` to begin Validate. On `pivot`, return to `discover-problems` or `research-market` in revision mode.

Attribution

tomzx

View source See grades on GitHub More from tomzx →

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 (0)

No comments yet. Be the first to comment!

--- name: frame-opportunities description: Convert discovery inputs into a scored opportunity-solution tree. Produces the artifact the first PDLC gate evaluates. argument-hint: "[initiative-id]" --- # Frame Opportunities The final step of Discover. This skill takes `problems.md`, `market.md`, and `competitors.md` and builds an opportunity-solution tree: the desired outcome at the top, opportunities beneath, and candidate solutions under each, scored so the gate can decide what to pursue. This is the artifact the **Discover gate** evaluates. A low score here should route back to discovery, not forward to validation. ## Prerequisites - Apply the shared PDLC conventions in `skills/pdlc/references/shared.md`. - `problems.md`, `market.md`, and `competitors.md` from the other Discover skills. ## Steps 1. State the desired outcome (the customer/business result), not a feature. 2. Branch into 3-7 opportunities that could move that outcome. Each opportunity is a change you can make, not a solution. 3. Under each opportunity, list 2-4 candidate solutions (these are provisional — Validate will test the riskiest assumptions, not pick a solution yet). 4. Score each opportunity on a transparent rubric: customer value, strategic fit (to `goals.md`), reach, and confidence. Record the score, not just a gut ranking. 5. Recommend the opportunity (or two) to carry into Validate, with the one or two riskiest assumptions called out for testing. 6. Write `opportunity-tree.md` to the initiative directory. ## Output Format Use the template at `skills/pdlc/templates/initiatives/opportunity-tree.md`. Carry the standard initiative frontmatter with `phase: discover`. ## Outcome If `$OUTCOME_YAML` is set, emit `verdict: drafted` plus `reason`. ## Completion Checklist - [ ] Desired outcome stated as a result, not a feature - [ ] Each opportunity is a change you can make, distinct from the others - [ ] Each opportunity scored on a stated rubric (not just ranked) - [ ] The riskiest assumptions to test are explicitly named for Validate ## Next Step Run the **Discover gate** via `make-decision`. On `proceed`, load `map-assumptions` to begin Validate. On `pivot`, return to `discover-problems` or `research-market` in revision mode.