[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HJB11N8F5RTPHC14YM2PS":3,"skill-same:01M71HJB11N8F5RTPHC14YM2PS":69},{"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":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M71HJB11N8F5RTPHC14YM2PS","elaborate-spec",null,"Refine a rough idea into a clear, detailed specification through dialogue. Does not produce code. Use when user has a vague idea, wants to think through a feature before planning, or needs to turn \"I want X\" into a concrete spec.","danielvm-git\u002Fbigpowers","danielvm-git","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1020864?v=4","01M71H1N1CTQ529S0KN7KETVG6","Daniel V M","01M71H1N218Y3S8WHCJ58NPRSW",289,"MIT","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Felaborate-spec\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"spec","elaborate spec","user","think","clear","use","produce","planning","feature","dialogue","idea","opus","refine","specification","vague","code","when","2026-11-10 10:12:30",false,"---\nname: elaborate-spec\nmodel: opus\ndescription: \"Refine a rough idea into a clear, detailed specification through dialogue. Does not produce code. Use when user has a vague idea, wants to think through a feature before planning, or needs to turn \\\"I want X\\\" into a concrete spec.\"\n---\n\n# Elaborate Spec\n\nTurn a rough idea into a clear specification through focused dialogue. No code is written during this skill — the output is shared understanding and a refined problem statement.\n\n> **HARD GATE** — Do NOT proceed with planning or implementation until the problem space is clearly understood. Success criteria, actors, and scope must be explicit before drafting a plan.\n\n## Process\n\n### 1. Listen first\n\nLet the user describe their idea in their own words. Do not interrupt or redirect. Take notes on:\n- The core problem they're trying to solve\n- Who is affected (actors)\n- What success looks like to them\n- Any constraints they've already identified\n\n### 2. Ask clarifying questions\n\nAsk one question at a time. Work through these areas:\n\n**Problem clarity**\n- What is the current behavior (or lack of behavior) that prompted this?\n- Who experiences this problem? How often?\n- What's the cost of not solving it?\n\n**Solution boundaries**\n- What is explicitly IN scope?\n- What is explicitly OUT of scope?\n- Are there existing solutions (internal or external) this replaces or integrates with?\n\n**Success criteria**\n- How will you know this is done?\n- What does the happy path look like end-to-end?\n- What are the key failure modes to handle?\n\n**Constraints**\n- Any performance requirements?\n- Any compatibility constraints (existing APIs, data formats)?\n- Any non-negotiable implementation decisions already made?\n\n### 2.5. Multiple Interpretations (HARD GATE)\n\n> **HARD GATE** — If the request admits ≥2 valid interpretations, do NOT guess. You must list them and ask the user to choose before proceeding. Proceeding with unresolved ambiguity is a failure of integrity.\n\nPresent the options clearly:\n> \"I see two ways to read this:\n> 1. [Interpretation A] — my recommendation because [reason]\n> 2. [Interpretation B]\n> Which is closer to what you mean?\"\n\n### 3. Surface hidden assumptions\n\nOnce the user has answered the main questions, probe for assumptions:\n- \"You mentioned X — does that mean Y is also true?\"\n- \"What happens when Z fails?\"\n- \"Is this for internal users, external users, or both?\"\n\n### 4. Synthesize and confirm\n\nSummarize your understanding in 3–5 bullet points aligned with [countable-story-format.md](..\u002F..\u002Fdocs\u002Fcountable-story-format.md):\n- The problem (feeds into §1 Business narrative)\n- The solution and main flow (feeds into §5)\n- The key constraints and alternative flows (feeds into §6)\n- The success criteria (feeds into §17 Gherkin)\n- What's out of scope (feeds into §18)\n\nAsk: \"Is this an accurate summary? Anything missing or wrong?\"\n\n### 5. Write specs\u002Fplanning-context.yaml\n\nAfter the user confirms the summary in step 4, persist the key decisions:\n\n```yaml\n# specs\u002Fplanning-context.yaml — written by elaborate-spec; consumed by scope-work and slice-tasks\nfeature_name: \"\u003Cfrom step 1>\"\nproblem_statement: \"\u003Cone paragraph>\"\nconstraints:\n  - \"\u003Cconstraint 1>\"\nout_of_scope:\n  - \"\u003Cexcluded item 1>\"\nkey_decisions:\n  - decision: \"\u003Cwhat was decided>\"\n    rationale: \"\u003Cwhy>\"\n```\n\nIf `specs\u002Fplanning-context.yaml` already exists, ask: `\"Planning context from a prior session exists. Update it? [Y\u002Fn]\"`. Overwrite on Y; leave unchanged on N.\n\n### 6. Suggest next skill\n\nOnce the spec is clear, recommend the next step:\n- If domain model needs work → `model-domain`\n- If ready to plan → `plan-release` (creates epic capsules with `epic.yaml` + story `.md` + `-tasks.yaml`) then `plan-work` per story\n- If a spike is needed first → `spike-prototype`\n- If architecture decisions are needed → `deepen-architecture` or `grill-me`\n- If the plan depends on a specific library or API → `grill-me` in docs mode\n","# Elaborate Spec\n\nTurn a rough idea into a clear specification through focused dialogue. No code is written during this skill — the output is shared understanding and a refined problem statement.\n\n> **HARD GATE** — Do NOT proceed with planning or implementation until the problem space is clearly understood. Success criteria, actors, and scope must be explicit before drafting a plan.\n\n## Process\n\n### 1. Listen first\n\nLet the user describe their idea in their own words. Do not interrupt or redirect. Take notes on:\n- The core problem they're trying to solve\n- Who is affected (actors)\n- What success looks like to them\n- Any constraints they've already identified\n\n### 2. Ask clarifying questions\n\nAsk one question at a time. Work through these areas:\n\n**Problem clarity**\n- What is the current behavior (or lack of behavior) that prompted this?\n- Who experiences this problem? How often?\n- What's the cost of not solving it?\n\n**Solution boundaries**\n- What is explicitly IN scope?\n- What is explicitly OUT of scope?\n- Are there existing solutions (internal or external) this replaces or integrates with?\n\n**Success criteria**\n- How will you know this is done?\n- What does the happy path look like end-to-end?\n- What are the key failure modes to handle?\n\n**Constraints**\n- Any performance requirements?\n- Any compatibility constraints (existing APIs, data formats)?\n- Any non-negotiable implementation decisions already made?\n\n### 2.5. Multiple Interpretations (HARD GATE)\n\n> **HARD GATE** — If the request admits ≥2 valid interpretations, do NOT guess. You must list them and ask the user to choose before proceeding. Proceeding with unresolved ambiguity is a failure of integrity.\n\nPresent the options clearly:\n> \"I see two ways to read this:\n> 1. [Interpretation A] — my recommendation because [reason]\n> 2. [Interpretation B]\n> Which is closer to what you mean?\"\n\n### 3. Surface hidden assumptions\n\nOnce the user has answered the main questions, probe for assumptions:\n- \"You mentioned X — does that mean Y is also true?\"\n- \"What happens when Z fails?\"\n- \"Is this for internal users, external users, or both?\"\n\n### 4. Synthesize and confirm\n\nSummarize your understanding in 3–5 bullet points aligned with [countable-story-format.md](..\u002F..\u002Fdocs\u002Fcountable-story-format.md):\n- The problem (feeds into §1 Business narrative)\n- The solution and main flow (feeds into §5)\n- The key constraints and alternative flows (feeds into §6)\n- The success criteria (feeds into §17 Gherkin)\n- What's out of scope (feeds into §18)\n\nAsk: \"Is this an accurate summary? Anything missing or wrong?\"\n\n### 5. Write specs\u002Fplanning-context.yaml\n\nAfter the user confirms the summary in step 4, persist the key decisions:\n\n```yaml\n# specs\u002Fplanning-context.yaml — written by elaborate-spec; consumed by scope-work and slice-tasks\nfeature_name: \"\u003Cfrom step 1>\"\nproblem_statement: \"\u003Cone paragraph>\"\nconstraints:\n  - \"\u003Cconstraint 1>\"\nout_of_scope:\n  - \"\u003Cexcluded item 1>\"\nkey_decisions:\n  - decision: \"\u003Cwhat was decided>\"\n    rationale: \"\u003Cwhy>\"\n```\n\nIf `specs\u002Fplanning-context.yaml` already exists, ask: `\"Planning context from a prior session exists. Update it? [Y\u002Fn]\"`. Overwrite on Y; leave unchanged on N.\n\n### 6. Suggest next skill\n\nOnce the spec is clear, recommend the next step:\n- If domain model needs work → `model-domain`\n- If ready to plan → `plan-release` (creates epic capsules with `epic.yaml` + story `.md` + `-tasks.yaml`) then `plan-work` per story\n- If a spike is needed first → `spike-prototype`\n- If architecture decisions are needed → `deepen-architecture` or `grill-me`\n- If the plan depends on a specific library or API → `grill-me` in docs mode\n",{"name":5,"model":35,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".codex\u002Fskills\u002Felaborate-spec",24,"https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers","https:\u002F\u002Fdanielvm-git.github.io\u002Fbigpowers\u002F","https:\u002F\u002Fgithub.com\u002Fdanielvm-git","danielvm.net","2026-11-10 01:18:54",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add danielvm-git\u002Fbigpowers --skill elaborate-spec",{"tool":61,"command":62},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill elaborate-spec",{"tool":64,"command":65},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill elaborate-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Felaborate-spec\u002FSKILL.md",true,[],[70,91,98,126,149,170],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":81,"publishedAt":41},"01M71KBG9F8X644MJB16H4V8M7","skill-verify-fail-open-fixture","Negative-path fixture for run-skill-verify.sh — must never PASS.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fskill-verify-fail-open\u002FSKILL.md",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[82,83,84,85,86,87,88,89,90],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run","for","never",{"skillNo":92,"name":93,"nameZh":6,"description":6,"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":41},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[97,87],"negative path",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":107,"publishedAt":41},"01M71KBBGF7Y4EB4AMHBZ8CJFC","write-document","Write, organize, and sync high-integrity technical documents using the BMAD methodology. Ensures every document is Bold, Minimal, Actionable, and Durable. Use when creating architectural docs, technical guides, or organizing the specs\u002F directory.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-document\u002FSKILL.md",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000002","文档处理",[108,109,110,111,112,113,114,115,116,117,29,40,118,119,120,121,122,123,124,125],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","minimal","bold","sonnet","integrity","organize","sync","directory","guides",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":41},"01M71KB8TM089JJD5AY5KAFSDM","wire-observability","Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwire-observability\u002FSKILL.md",[],[133,134,135,117,136,29,137,138,139,140,120,141,142,143,144,145,146,40,147,148],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":41},"01M71KB6CNRANP449DQA3NJZ96","wire-ci","CI pipeline setup with bundled, forge-neutral templates and local validation. Detects the forge from the git remote, generates workflows for supported forges, and skips honestly for the rest. The CI equivalent of wire-observability.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwire-ci\u002FSKILL.md",[],[156,157,158,159,160,161,162,163,164,165,166,117,167,89,133,120,168,169],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","with","ci pipeline setup","git","workflows",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":183,"publishedAt":41},"01M71KB2ZV98P03X88QR8MT9F1","visual-dashboard","Start a browser-based dashboard that visualizes architecture, implementation plans, and project status. Persists artifacts in .bigpowers\u002Fdashboard\u002F. Reads specs\u002Fstate.yaml, release-plan.yaml, epics, and planning-status via HTTP API or opencode panel.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-dashboard\u002FSKILL.md",[176,179,180],{"categoryNo":177,"categoryName":178,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":181,"categoryName":182,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[184,185,186,187,188,189,190,31,191,120,192,193,194,195,196,197,198,147,199,200],"dashboard","visual","visual dashboard","status","artifacts","http","plans","panel","start","release","opencode","plan","browser","api","architecture","project status","http api"]