← ClaudeAtlas

biz-plannerlisted

Turn a raw business/project idea into a decision-locked execution plan. Use when the user starts a NEW idea, says 'plan this idea', 'biz plan', 'new project idea', 'hackathon project', or wants tech-stack selection, mindmapping, and a final approval-gated plan for any new venture.
Tariq-himself/opencode-maker-kit · ★ 0 · AI & Automation · score 70
Install: claude install-skill Tariq-himself/opencode-maker-kit
# Biz Planner — Idea → Decision-Locked Execution Plan A proven ideation workflow, distilled from real-world planning sessions. Run it on ANY new business/project idea: `<IDEA>` = the idea text from $ARGUMENTS or conversation. ## Stage 0 — Context Ingestion (if provided) If the user pasted emails, links, rules, competitor material, or requirements: 1. Analyze each source separately first: what it is, hard requirements (table), signals between the lines. 2. Then cross-analyze all sources together: conflicts, changed assumptions, combined implications. 3. Surface the single most important signal before moving on. ## Stage 0.5 — Existing Tools Auto-Discovery (always run) Before asking decision questions, check what the user ALREADY has that this idea can reuse: 1. Look for a cached inventory at `~/.config/opencode/maker-kit/inventory.local.md` (Windows: `%USERPROFILE%\.config\opencode\maker-kit\inventory.local.md`). 2. If missing/stale, scan `~/.config/opencode/agent(s)/`, `~/.config/opencode/command(s)/`, `~/.config/opencode/skills/**/SKILL.md`, and `~/.claude/skills/`. 3. List tools relevant to THIS idea (e.g., UI work → installed design/UI skill suites; project tracking → workflow frameworks; screenshots/desktop automation → utility skills). 4. Report in 3–6 lines: "You already own: X, Y — I've factored them into the plan below" and weave them into Architecture/Schedule sections instead of planning to build equivalents from scratch. 5. If a needed capability is missing enti