[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CKHSC1BAWC7VSW6TPXNMNZ":3,"skill-same:01M7CKHSC1BAWC7VSW6TPXNMNZ":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":50,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M7CKHSC1BAWC7VSW6TPXNMNZ","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.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\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","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fidea-os",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill idea-os",{"tool":60,"command":61},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill idea-os",{"tool":63,"command":64},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill idea-os","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fidea-os\u002FSKILL.md",true,[],[69,76,83,90,97,104],{"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},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\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},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\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},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\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},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\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":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]