[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PAGAABHPJX5Z6YZPVG0WS4":3,"skill-same:01M6PAGAABHPJX5Z6YZPVG0WS4":89},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":36,"commitSha":69,"skillDirectory":70,"forksCount":71,"repositoryHtmlUrl":72,"repositoryHomepageUrl":6,"ownerHtmlUrl":73,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":74,"install":75,"resources":88},"01M6PAGAABHPJX5Z6YZPVG0WS4","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.","clodoaldoperito-droid\u002FARQUITETURA_JARVIS","clodoaldoperito-droid","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F259241428?v=4","01M6P1D7567KGD4J875631AZDY","01M6P1D7A0ZZDC72AG333YNZ7E",1,"MIT","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fagent_skills\u002Fidea-os\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"idea os","os","idea","files","phase","mvp","deep","journey","main","community","safe","jtbd","market-research","clarify","plan","analysis","pipeline","deep research","product","mermaid","2026-11-10 10:12:30",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":38,"tags":53,"tools":61,"author":65,"source":37,"license":14,"category":54,"date_added":66,"description":7,"source_repo":67,"source_type":37,"license_source":68},[54,55,40,33,56,39,57,58,59,60],"product-management","prd","idea-validation","swot","competitor-analysis","founder","non-technical",[62,63,64],"claude","cursor","gemini","Slashworks-biz","2026-04-18","Slashworks-biz\u002Fidea-os","https:\u002F\u002Fgithub.com\u002FSlashworks-biz\u002Fidea-os\u002Fblob\u002Fmain\u002FLICENSE","cd2930847fb1ada3557e9207d3be0a1a1ed08f24","agent_skills\u002Fidea-os",0,"https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid","2026-07-22 10:13:36",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add clodoaldoperito-droid\u002FARQUITETURA_JARVIS --skill idea-os",{"tool":81,"command":82},"bunx","bunx skills add clodoaldoperito-droid\u002FARQUITETURA_JARVIS --skill idea-os",{"tool":84,"command":85},"pnpm","pnpm dlx skills add clodoaldoperito-droid\u002FARQUITETURA_JARVIS --skill idea-os","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fagent_skills\u002Fidea-os\u002FSKILL.md",true,[],[90,117,149,169,184,208],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":99,"publishedAt":48},"01M6Q6BV6JFVC1CHDVW58F63AB","plotly","Interactive visualization library. Use when you need hover info, zoom, pan, or web-embeddable charts. Best for dashboards, exploratory analysis, and presentations. For static publication figures use matplotlib or scientific-visualization.","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fskills_extracted\u002Fskills\u002Fskills\u002Fplotly\u002FSKILL.md",[96],{"categoryNo":97,"categoryName":98,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",[92,100,101,102,103,104,105,106,107,108,109,110,111,43,112,113,114,115,116],"static","Charts","for","you","figures","zoom","scientific","info","use","interactive","dashboards","matplotlib","library","visualization","presentations","hover","web",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":129,"publishedAt":48},"01M6Q5YRJC1RTZ8A8FK6Q80SH1","native-data-fetching","Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, and Expo Router data loaders (useLoaderData).","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fskills_extracted\u002Fskills\u002Fskills\u002Fnative-data-fetching\u002FSKILL.md",[123,126],{"categoryNo":124,"categoryName":125,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":127,"categoryName":128,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000033","数据分析师",[130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,108,145,146,147,148],"native","data fetching","data","native data fetching","react","fetch","debugging","error","caching","error handling","query","call","router","swr","api","expo router","request","implementing","support",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":48},"01M6Q4PFYVRE7AE05V883QFD55","expo-tailwind-setup","Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fskills_extracted\u002Fskills\u002Fskills\u002Fexpo-tailwind-setup\u002FSKILL.md",[155],{"categoryNo":124,"categoryName":125,"taxonomyType":20,"taxonomyTypeDesc":21},[157,158,159,160,134,102,161,162,130,163,164,165,166,167,168],"setup","expo tailwind setup","Tailwind","expo","with","nativewind","Tailwind CSS","react-native","styling","up","SET","css",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":48},"01M6Q4PD3AAXFEKXEW225X0K00","expo-dev-client","Build and distribute Expo development clients locally or via TestFlight","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fskills_extracted\u002Fskills\u002Fskills\u002Fexpo-dev-client\u002FSKILL.md",[],[176,177,160,178,179,180,181,182,183],"expo dev client","dev","client","clients","via","distribute","build","development",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":193,"publishedAt":48},"01M6Q4P6HYVP8WJK2YTSHDZGWB","expo-cicd-workflows","Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI\u002FCD or workflows in an Expo or EAS context, mentions .eas\u002Fworkflows\u002F, or wants help with EAS build pipelines or deployment automation.","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fskills_extracted\u002Fskills\u002Fskills\u002Fexpo-cicd-workflows\u002FSKILL.md",[190],{"categoryNo":191,"categoryName":192,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[160,194,195,196,197,198,199,182,31,108,200,201,202,203,161,204,205,206,102,207],"cicd","expo cicd workflows","workflows","help","about","CI\u002FCD","read","projects","Bash","ci","deployment","automation","workflow","deployment automation",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":220,"publishedAt":48},"01M6Q4P2ZHG9BFXPT680RJ6ZVG","expo-api-routes","Guidelines for creating API routes in Expo Router with EAS Hosting","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fskills_extracted\u002Fskills\u002Fskills\u002Fexpo-api-routes\u002FSKILL.md",[214,217],{"categoryNo":215,"categoryName":216,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":218,"categoryName":219,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师",[221,144,160,222,102,223,161,145,224,142],"expo api routes","guidelines","eas hosting","hosting"]