Skill

capture-idea

Capture a new business idea from text input into a structured workspace. Always preserves the raw input verbatim and offers optional formatted versions — executive summary, elevator pitch, technical deep-dive, and timeline/project plan. Use when the user wants to start a new idea workspace from a written description, brain-dump, or pasted text.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin business-idea-eval

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Creates a new idea workspace under `<workspace_path>/ideas/<idea-slug>/` and lays down the raw input plus any formatted variants the user requests.

SKILL.md

Similar Skills

skill-lookup

159.9k

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

next-compile

139.2k

Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.

1 file

vercel-next-js-2

angular-new-app

100.1k

Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.

angular-angular-1

Stats

Stars0

Forks0

Last CommitApr 28, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

capture-idea

Capture Idea (text)

Creates a new idea workspace under <workspace_path>/ideas/<idea-slug>/ and lays down the raw input plus any formatted variants the user requests.

Steps

Read $CLAUDE_USER_DATA/business-idea-eval/config.json for workspace_path. If absent, run onboard.

Take the raw idea text from the user (paste, file, or dictation that's already been transcribed).

Derive an idea slug — short, kebab-case, descriptive. Confirm with the user before creating the directory.

Scaffold:

<workspace_path>/ideas/<idea-slug>/
  idea.md              # raw input, verbatim, with frontmatter (created date, source)
  versions/            # formatted variants
  analysis/            # lens outputs
  council/             # council deliberation outputs
  synthesis/           # consolidated assessments
  exports/             # rendered PDFs

Write idea.md with frontmatter:

---
slug: <idea-slug>
captured: YYYY-MM-DD
source: text | voice | imported
---

<verbatim raw input>

Offer the user a menu of formatted variants (any combination):

Executive summary — 150–250 words, one-pager-style, problem/solution/market/why-now
Elevator pitch — three options: 30-second, 60-second, 2-minute
Technical deep-dive / spec outline — architecture sketch, key components, build phases, hard problems
Timeline & project plan — milestone-based, MVP → public launch, with rough effort estimates and dependencies

For each variant requested, write to versions/<variant>.md. Keep them clearly labelled as derived/edited so the raw stays canonical.

Print the new directory path and the list of files written.

Notes

Never edit idea.md after creation — it's the source of truth. Formatted variants live in versions/.

If the user only wants raw capture, skip the menu.

Idea slug should be unique within the workspace; if a collision exists, append a short suffix and confirm.