| name | idea-os |
| description | Five-phase pipeline (triage → clarify → research → PRD → plan) that turns a raw idea into four linked files: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with mermaid user journey and kill criteria. |
| category | product-management |
| risk | safe |
| source | community |
| source_repo | Slashworks-biz/idea-os |
| source_type | community |
| date_added | 2026-04-18 |
| author | Slashworks-biz |
| tags | ["product-management","prd","market-research","mvp","idea-validation","jtbd","swot","competitor-analysis","founder","non-technical"] |
| tools | ["claude","cursor","gemini"] |
| license | MIT |
| license_source | https://github.com/Slashworks-biz/idea-os/blob/main/LICENSE |
idea-os
An operating system for turning a raw idea into a build-ready plan. Takes a rough problem statement and produces four files: clarifying questions, deep research, a PRD, and a phased execution plan with platform/stack picks, a user-journey diagram, and kill criteria.
Overview
idea-os is a 5-phase sequential pipeline where each phase's output feeds the next — research shapes the PRD, PRD shapes the plan, plan's kill criteria tie back to research insights. Unlike single-command PRD generators, idea-os refuses to write a PRD until research is done, and refuses to write a plan until the PRD is stable. Depth and vocabulary adapt to a two-axis classification (complexity × builder sophistication) so a first-time builder isn't drowning in jargon and a founder gets full rigor.
Source: https://github.com/Slashworks-biz/idea-os — full skill, 11 reference files, 4 asset templates, and a 590-line worked example.
When to Use
- Use when a user shares a raw product idea or problem statement and wants a structured pipeline from clarifying questions through deep research, PRD, and a phased execution plan.
- Use when the user says "I have an idea for…", "help me build X", "validate and plan this concept", or "what should I build?" — and wants files they can take forward, not a one-shot answer.
- Use when a non-technical founder, PM, or hobbyist needs structure to bridge the gap between "idea" and "Monday morning's build queue".
- Do not use for quick sanity-check feedback on a half-formed idea (use
idea-refine instead) or for editing an existing PRD (use product-management instead).
How It Works
Phase 1 — Triage
Classify the idea on two axes before anything else. Depth of research/PRD/plan and question count scale with complexity; vocabulary scales with sophistication.
- Idea tier (T1/T2/T3) — T1 = weekend utility, T2 = SaaS MVP or AI wrapper, T3 = marketplace / B2B SaaS / regulated.
- Sophistication (S1/S2/S3) — S1 = non-technical, no framework names; S2 = hobbyist, introduce frameworks with definitions; S3 = founder/senior PM, full vocabulary.
State the classification in one line (e.g. "T2 · S2 — moderate SaaS, builder has shipped before") before proceeding.
Phase 2 — Clarify
Write questions.md with 4–18 questions (count scales with complexity), grouped: Who and Pain · Scope and Wedge · Constraints and Goals. Every question must be actionable — the answer has to change what you build. Generic questions are rejected.
After writing, stop and wait for answers. Do not proceed to research until answered or autonomous-mode assumptions are declared.
