Slashworks-biz

Idea OS — Development skill for Claude Code

Development community

Operating system for turning raw ideas into build-ready plans — a Claude Code skill.

How to install Idea OS

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Slashworks-biz/idea-os and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Idea OS does

Operating system for turning raw ideas into build-ready plans — a Claude Code skill.

Alternatives in Development

LifeOS — ⛰️ The Life Operating System — an intent engineering platform that moves you from your current state to your i 18.7k ★
Fable OS — An agentic operating system where the kernel is controlled directly by Claude 324 ★
Obsidian Init — Scan your vault and generate a _CLAUDE.md operating manual, index.md catalog, and log.md 277 ★

README

idea-os

An **operating system for turning raw ideas into build-ready plans** — as a Claude Code / Claude-compatible skill.

You drop in a rough problem statement or idea. It runs a five-phase pipeline (clarify → research → PRD → plan) and writes four files you can take straight to building:

questions.md — sharp, tier-adapted clarifying questions
research.md — market, competitors, SWOT, JTBD, distribution, trends, insights
PRD.md — problem, users, scope, non-goals, metrics
plan.md — user journey (mermaid), platform/stack recommendations, phased build with kill criteria

Why this exists

Coding is having a moment. Non-developers are opening terminals. Experienced PMs are shipping side projects. The hard part isn't the code anymore — it's the gap between "I have an idea" and "I know exactly what to build, for whom, how, and how I'll know it's working."

Most PRD tools stop at the document. `idea-os` goes further — it ties research to PRD to phased plan, with opinionated platform/stack recommendations, a mermaid user-journey diagram, kill criteria per phase, and first-100-users distribution. It adapts depth to the idea's complexity and the builder's experience so a first-time builder isn't buried in jargon and a founder gets full rigor.

What you get

Clarifying questions (4–18, complexity-adjusted) that actually change the answer
Deep research — TAM/SAM/SOM (top-down + bottom-up), segmentation, competitor matrix with positioning map, SWOT, JTBD, distribution strategy, why-now, 3–7 non-obvious insights
PRD — falsifiable problem statement, named personas, ranked JTBD, leading/lagging metrics, explicit non-goals
Execution plan with:
- User journey (text walkthrough + mermaid diagram that renders on GitHub)
- Platform recommendation (web / mobile / desktop / CLI / extension / hybrid) tied to research findings
- Stack recommendation (conservative / modern / cutting-edge matrix)
- Phased build (MVP → v1 → target s