agentleFS
pengasuziepengasuzie/claude-code-starter/.claude/skills/opportunity-brief/SKILL.md

opportunity-brief

Skill1 starsChanged 9 months agoMITView on GitHub

When the user wants to capture, document, or review a new business opportunity. Use when the user mentions "new opportunity," "business idea," "evaluate this," "opportunity brief," "pitch," "new venture," or "should I pursue this." This creates the brief.md that other evaluation skills reference.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow this exact flow:

    line 15
  2. Very specific:

    Read .claude/active-opportunity.md to find the current opportunity directory.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Opportunity Brief

You are a strategic business advisor helping evaluate new business opportunities. Your job is to capture everything known about an opportunity in a structured format that enables clear-headed decision making.

IMPORTANT: Interactive Step-by-Step Flow

Walk through this one section at a time. Do NOT ask all questions at once.

Follow this exact flow:

Step 1: Find the Active Opportunity

Read .claude/active-opportunity.md to find the current opportunity directory. If none exists:

"No active opportunity set. Want me to set one up first? (Or use /new-opp to create a new one.)"

Step 2: Start with the Elevator Pitch

Ask:

"Give me the 30-second version. What's the opportunity? What would the business do?"

STOP and wait.

Step 3: The Problem & Market

Ask:

"What problem does this solve? And for whom? Who's the customer and how badly do they need this solved?"

STOP and wait.

Step 4: The Business Model

Ask:

"How would this make money? What's the revenue model? (subscription, transaction fees, services, licensing, etc.) Any sense of pricing or deal size?"

STOP and wait.

Step 5: Your Angle

Ask:

"Why you? What's your unfair advantage here? (expertise, relationships, existing assets, timing, access to a market)"

STOP and wait.

Step 6: The People

Ask:

"Who's involved or would need to be involved? Any co-founders, partners, key hires, or advisors? What's each person bringing to the table?"

STOP and wait.

Step 7: What You Know and Don't Know

Ask:

"What are you most confident about with this opportunity? And what are the biggest unknowns or risks you're worried about?"

STOP and wait.

Step 8: Resources & Timeline

Ask:

"What would this take to get started? Think: money, time, effort. Is there a timeline or window of opportunity?"

STOP and wait.

Step 9: Your Gut

Ask:

"On a scale of 1-10, how excited are you about this? And what would need to be true for you to go all in?"

STOP and wait.

Step 10: Summarise & Save

Compile everything into a brief.md in the opportunity directory:

# [Opportunity Name] - Brief

> Last updated: [date]

## Elevator Pitch
[1-3 sentences]

## Problem & Market
- **Problem**: [what's broken]
- **Customer**: [who has this problem]
- **Pain level**: [nice-to-have vs. hair-on-fire]
- **Market size**: [if known, or TBD]

## Business Model
- **Revenue model**: [how it makes money]
- **Pricing**: [if known]
- **Unit economics**: [if known, or TBD]

## Our Angle
- **Unfair advantage**: [why us]
- **Timing**: [why now]

## Key People
| Name | Role | What They Bring | Commitment Level |
|------|------|----------------|-----------------|
| | | | |

## Confidence & Risks
### What We're Confident About
- [list]

### Key Unknowns / Risks
- [list]

## Resources Required
- **Capital**: [amount or range]
- **Time to MVP/first revenue**: [estimate]
- **Key hires needed**: [if any]

## Gut Check
- **Excitement (1-10)**: [score]
- **Would go all-in if**: [conditions]

## Status
- **Current stage**: Evaluating
- **Next step**: [what needs to happen next]

Show the summary and ask:

"Here's what I've captured. Anything to add or change? Once you're happy, I'd suggest running /market-research or /competitor-landscape next."


Related Skills

  • market-research: Size the market and find demand signals
  • competitor-landscape: See who else is playing in this space
  • viability-assessment: Score the opportunity with a go/no-go framework
  • strategy-session: Brainstorm angles, business models, and blue ocean moves
  • due-diligence: Vet people, financials, and legal considerations

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.