[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78QCJYJM2P08FCSCCSSWQ22":3,"skill-same:01M78QCJYJM2P08FCSCCSSWQ22":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M78QCJYJM2P08FCSCCSSWQ22","idea-os",null,"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.","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fidea-os\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: idea-os\ndescription: \"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.\"\ncategory: product-management\nrisk: safe\nsource: community\nsource_repo: Slashworks-biz\u002Fidea-os\nsource_type: community\ndate_added: \"2026-04-18\"\nauthor: Slashworks-biz\ntags: [product-management, prd, market-research, mvp, idea-validation, jtbd, swot, competitor-analysis, founder, non-technical]\ntools: [claude, cursor, gemini]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002FSlashworks-biz\u002Fidea-os\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# idea-os\n\nAn 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\u002Fstack picks, a user-journey diagram, and kill criteria.\n\n## Overview\n\nidea-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.\n\nSource: https:\u002F\u002Fgithub.com\u002FSlashworks-biz\u002Fidea-os — full skill, 11 reference files, 4 asset templates, and a 590-line worked example.\n\n## When to Use\n\n- 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.\n- 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.\n- Use when a non-technical founder, PM, or hobbyist needs structure to bridge the gap between \"idea\" and \"Monday morning's build queue\".\n- 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).\n\n## How It Works\n\n### Phase 1 — Triage\n\nClassify the idea on two axes before anything else. Depth of research\u002FPRD\u002Fplan and question count scale with complexity; vocabulary scales with sophistication.\n\n- **Idea tier (T1\u002FT2\u002FT3)** — T1 = weekend utility, T2 = SaaS MVP or AI wrapper, T3 = marketplace \u002F B2B SaaS \u002F regulated.\n- **Sophistication (S1\u002FS2\u002FS3)** — S1 = non-technical, no framework names; S2 = hobbyist, introduce frameworks with definitions; S3 = founder\u002Fsenior PM, full vocabulary.\n\nState the classification in one line (e.g. \"T2 · S2 — moderate SaaS, builder has shipped before\") before proceeding.\n\n### Phase 2 — Clarify\n\nWrite `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.\n\nAfter writing, stop and wait for answers. Do not proceed to research until answered or autonomous-mode assumptions are declared.\n\n### Phase 3 — Research\n\nWrite `research.md` using WebSearch + WebFetch. Minimum: 5 WebSearches, 2 WebFetches on named competitors, 1 source per TAM number, date on every source. Anything unsourced gets flagged `[assumption]`.\n\nRequired sections: problem validation, JTBD, market (TAM\u002FSAM\u002FSOM top-down + bottom-up), competitors (direct\u002Findirect\u002Fsubstitutes + positioning map), SWOT, distribution (first-100-users channel fit), risks, and 3–7 non-obvious insights.\n\n### Phase 4 — PRD\n\nWrite `PRD.md` with: falsifiable problem statement, named personas, ranked JTBD, non-goals (mandatory — it's where bad PRDs die), leading and lagging metrics.\n\n### Phase 5 — Plan\n\nWrite `plan.md` with: user journey (text + mermaid), platform recommendation tied to research findings, stack in conservative\u002Fmodern\u002Fcutting-edge matrix, phased build (MVP → v1 → target) with kill criteria per phase and first-100-users distribution per phase, metrics per phase, and 3–5 immediate next actions.\n\n## Limitations\n\n- Requires user input between phases for best results; if answers are missing, outputs depend on explicit assumptions.\n- Produces planning artifacts (`questions.md`, `research.md`, `PRD.md`, `plan.md`) but does not execute build or deployment work.\n- Source quality determines output quality; weak or outdated references can reduce recommendation accuracy.\n- Better suited to new-idea validation and early planning than late-stage optimization of an existing shipped product.\n\n## Examples\n\n### Example 1: Non-technical founder with a consumer-app idea\n\nUser: \"I want to build a habit tracker for people with ADHD.\"\n\nidea-os classifies T2 · S1, writes 8 plain-language clarifying questions, runs research with sourced competitor pricing and community signal from ADHD subreddits, produces a PRD with ADHD-specific non-goals (no streaks, no punishment mechanics), and a plan with a single-screen MVP and a kill criterion tied to 14-day retention.\n\n### Example 2: Founder with a B2B SaaS idea\n\nUser: \"I'm thinking about procurement software for mid-market manufacturers.\"\n\nidea-os classifies T3 · S3, writes 18 questions including procurement-cycle specifics, runs research with Wardley-map option and Porter 5 forces, produces a PRD with tiered personas (buyer\u002Fapprover\u002FIT), and a plan with a phase-1 kill criterion tied to paid-pilot close rate.\n\n## Full source\n\nFull 11-reference skill, 4 asset templates, worked example, and MIT license at https:\u002F\u002Fgithub.com\u002FSlashworks-biz\u002Fidea-os. This antigravity entry is a reference copy — the upstream repo is where ongoing development lives.\n","# idea-os\n\nAn 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\u002Fstack picks, a user-journey diagram, and kill criteria.\n\n## Overview\n\nidea-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.\n\nSource: https:\u002F\u002Fgithub.com\u002FSlashworks-biz\u002Fidea-os — full skill, 11 reference files, 4 asset templates, and a 590-line worked example.\n\n## When to Use\n\n- 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.\n- 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.\n- Use when a non-technical founder, PM, or hobbyist needs structure to bridge the gap between \"idea\" and \"Monday morning's build queue\".\n- 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).\n\n## How It Works\n\n### Phase 1 — Triage\n\nClassify the idea on two axes before anything else. Depth of research\u002FPRD\u002Fplan and question count scale with complexity; vocabulary scales with sophistication.\n\n- **Idea tier (T1\u002FT2\u002FT3)** — T1 = weekend utility, T2 = SaaS MVP or AI wrapper, T3 = marketplace \u002F B2B SaaS \u002F regulated.\n- **Sophistication (S1\u002FS2\u002FS3)** — S1 = non-technical, no framework names; S2 = hobbyist, introduce frameworks with definitions; S3 = founder\u002Fsenior PM, full vocabulary.\n\nState the classification in one line (e.g. \"T2 · S2 — moderate SaaS, builder has shipped before\") before proceeding.\n\n### Phase 2 — Clarify\n\nWrite `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.\n\nAfter writing, stop and wait for answers. Do not proceed to research until answered or autonomous-mode assumptions are declared.\n\n### Phase 3 — Research\n\nWrite `research.md` using WebSearch + WebFetch. Minimum: 5 WebSearches, 2 WebFetches on named competitors, 1 source per TAM number, date on every source. Anything unsourced gets flagged `[assumption]`.\n\nRequired sections: problem validation, JTBD, market (TAM\u002FSAM\u002FSOM top-down + bottom-up), competitors (direct\u002Findirect\u002Fsubstitutes + positioning map), SWOT, distribution (first-100-users channel fit), risks, and 3–7 non-obvious insights.\n\n### Phase 4 — PRD\n\nWrite `PRD.md` with: falsifiable problem statement, named personas, ranked JTBD, non-goals (mandatory — it's where bad PRDs die), leading and lagging metrics.\n\n### Phase 5 — Plan\n\nWrite `plan.md` with: user journey (text + mermaid), platform recommendation tied to research findings, stack in conservative\u002Fmodern\u002Fcutting-edge matrix, phased build (MVP → v1 → target) with kill criteria per phase and first-100-users distribution per phase, metrics per phase, and 3–5 immediate next actions.\n\n## Limitations\n\n- Requires user input between phases for best results; if answers are missing, outputs depend on explicit assumptions.\n- Produces planning artifacts (`questions.md`, `research.md`, `PRD.md`, `plan.md`) but does not execute build or deployment work.\n- Source quality determines output quality; weak or outdated references can reduce recommendation accuracy.\n- Better suited to new-idea validation and early planning than late-stage optimization of an existing shipped product.\n\n## Examples\n\n### Example 1: Non-technical founder with a consumer-app idea\n\nUser: \"I want to build a habit tracker for people with ADHD.\"\n\nidea-os classifies T2 · S1, writes 8 plain-language clarifying questions, runs research with sourced competitor pricing and community signal from ADHD subreddits, produces a PRD with ADHD-specific non-goals (no streaks, no punishment mechanics), and a plan with a single-screen MVP and a kill criterion tied to 14-day retention.\n\n### Example 2: Founder with a B2B SaaS idea\n\nUser: \"I'm thinking about procurement software for mid-market manufacturers.\"\n\nidea-os classifies T3 · S3, writes 18 questions including procurement-cycle specifics, runs research with Wardley-map option and Porter 5 forces, produces a PRD with tiered personas (buyer\u002Fapprover\u002FIT), and a plan with a phase-1 kill criterion tied to paid-pilot close rate.\n\n## Full source\n\nFull 11-reference skill, 4 asset templates, worked example, and MIT license at https:\u002F\u002Fgithub.com\u002FSlashworks-biz\u002Fidea-os. This antigravity entry is a reference copy — the upstream repo is where ongoing development lives.\n",{"name":5,"risk":24,"tags":25,"tools":36,"author":40,"source":41,"license":15,"category":26,"date_added":42,"description":7,"source_repo":43,"source_type":41,"license_source":44},"safe",[26,27,28,29,30,31,32,33,34,35],"product-management","prd","market-research","mvp","idea-validation","jtbd","swot","competitor-analysis","founder","non-technical",[37,38,39],"claude","cursor","gemini","Slashworks-biz","community","2026-04-18","Slashworks-biz\u002Fidea-os","https:\u002F\u002Fgithub.com\u002FSlashworks-biz\u002Fidea-os\u002Fblob\u002Fmain\u002FLICENSE","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fidea-os",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill idea-os",{"tool":60,"command":61},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill idea-os",{"tool":63,"command":64},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill idea-os","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fidea-os\u002FSKILL.md",true,[],[69,76,83,90,97,105],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]