agentleFS
pengasuziepengasuzie/claude-skills/skills/new-idea/SKILL.md

new-idea

Skill0 starsChanged 9 months agoMITView on GitHub

Scaffold a new idea directory with all the right files. Use when the user mentions "new idea," "new opportunity," "evaluate this," "I've been thinking about," or wants to capture a business idea for evaluation.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write a one-liner summary of the idea

    line 20
  2. Distinctive:

    If anything is unclear, confirm the name before creating.

    line 21
  3. Distinctive:

    Look back through the current conversation for anything relevant to this idea:

    line 24

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

New Idea

Capture a new idea while the context is fresh.

Instructions

  1. Ask "What's the idea?"

    "What's the idea? Just dump what you're thinking — a sentence, a paragraph, a link. I'll sort it out."

    STOP and wait.

  2. Extract a slug and one-liner from their response
    • Derive a short kebab-case slug for the directory name (e.g., book-to-audio, freight-ai-marketplace)
    • Write a one-liner summary of the idea
    • If anything is unclear, confirm the name before creating. Otherwise just go.
  3. Scan conversation for context Look back through the current conversation for anything relevant to this idea:

    • Links discussed (repos, articles, competitor sites)
    • Technical details or constraints mentioned
    • Inspiration or prior art referenced
    • Problems or opportunities identified

    Capture this as notes/initial-context.md — a raw dump of everything relevant from the conversation, with sources.

  4. Create the directory structure
    ideas/[idea-name]/
    ├── README.md              ← Overview, status, gut-check
    ├── notes/
    │   └── initial-context.md ← Auto-captured from conversation
    ├── research/              ← Market research outputs
    ├── competitors/           ← Competitor profiles and analysis
    ├── docs/                  ← Uploaded documents, pitch decks, financials
    └── notes/                 ← Meeting notes, strategy session outputs
  5. Create README.md with this template:

    # [Idea Name]
    
    **Status**: Evaluating
    **Created**: [date]
    **Tags**: [suggest 2-3 tags like #saas, #side-project, #tool, #content, #marketplace, #ai, #b2b, #b2c, #dev-tool]
    **Go/No-Go**: Pending
    
    ## One-liner
    [One sentence summary derived from their description]
    
    ## Why this is interesting
    - [Bullet 1]
    - [Bullet 2]
    
    ## What could kill it
    - [Bullet 1]
    - [Bullet 2]
    
    ## Key Links
    | Resource | URL |
    |----------|-----|
    | [any links from conversation] | |
    
    ## Key People
    | Name | Role | Notes |
    |------|------|-------|
    | | | |
    
    ## Evaluation Progress
    - [ ] Opportunity brief captured
    - [ ] Market research complete
    - [ ] Competitor landscape mapped
    - [ ] Strategy session done
    - [ ] Due diligence complete
    - [ ] Viability assessment scored
    - [ ] Go/No-Go decision made
    
    ## Decision Log
    | Date | Decision | Rationale |
    |------|----------|-----------|
    | | | |

    Fill in the one-liner and key links from conversation context.

  6. Ask for the gut-check

    "I've pre-filled what I could from our conversation. Two quick questions:

    Why is this interesting? What's the bet — why could this work?

    What could kill it? What's the biggest risk or reason this doesn't work?"

    STOP and wait. Fill in the gut-check sections with their answers.

  7. Set this as the active idea Create/update .claude/active-opportunity.md:
    # Active Idea
    Currently evaluating: [Idea Name]
    Path: ideas/[idea-name]/
  8. Suggest next step

    "You're set up. Next steps when you're ready:

    • /opportunity-brief — flesh out the full picture (model, people, risks)
    • /market-research — size the market and find demand signals
    • /competitor-landscape — see who else is playing here

    Or just keep chatting about it — I'll remember the context."

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.