[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71KA7M5YWK2SZRYC6WESEJS":3,"skill-same:01M71KA7M5YWK2SZRYC6WESEJS":63},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M71KA7M5YWK2SZRYC6WESEJS","slice-tasks",null,"PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs\u002Fepics\u002F. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.","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\u002Fskills\u002Fslice-tasks\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"slice","slice tasks","tasks","planning","scope","for","scoped","use","standard","stories","work","plan","spine","break","prd","sonnet","2026-11-10 10:12:30",false,"---\nname: slice-tasks\ndescription: \"PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs\u002Fepics\u002F. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.\"\nmodel: sonnet\neffort: standard\n---\n\n\u003C!-- story: e45s29 -->\n\n# Slice Tasks\n\n> **Spine position:** Step 2 — scope-work → slice-tasks → plan-work.\n\nProduce **epic capsule story tasks** in `specs\u002Fepics\u002FeNN-slug\u002F` — vertical slices, each independently deliverable and testable. Output: decoupled `eNNsYY-tasks.yaml` files with runnable verify commands. Legacy `specs\u002Fepics\u002F (see slice-tasks)` is deprecated; use capsule dirs + `execution-status.yaml`.\n\n## Pre-flight\n\n- [ ] Does `specs\u002Fproduct\u002FSCOPE_LATEST.yaml` exist? If not, run `scope-work` first — you can't slice what you haven't bounded.\n- [ ] Is the `release-plan.yaml` populated with the epics you're slicing? Epic IDs (e01, e02…) should exist before you create stories.\n- [ ] Do you understand the difference between a horizontal layer and a vertical slice? (See anti-patterns below.)\n\n## Process\n\n0. **Read planning-context.yaml** — If `specs\u002Fplanning-context.yaml` exists, read it first:\n   ```bash\n   test -f specs\u002Fplanning-context.yaml && echo \"Context found\" || echo \"No context — starting fresh\"\n   ```\n   Use `feature_name`, `constraints`, and `out_of_scope` to inform slice boundaries. `key_decisions` in the file may constrain how stories are cut (e.g., \"no external deps\" constrains slice 2). If absent, proceed normally.\n\n1. **Read context** — Read `specs\u002Fproduct\u002FSCOPE_LATEST.yaml` and\u002For `specs\u002Frelease-plan.yaml`. Understand what the epic delivers end-to-end.\n\n2. **Cut tracer-bullet slices** — Identify the thinnest possible vertical path through the stack that delivers user value. Start with this slice; it will catch integration issues first. For example:\n   - A search feature: first slice is \"user types query → API returns results\" (no filters, no pagination, no ranking — just the plumbing working end-to-end).\n   - A checkout flow: first slice is \"user clicks buy → order created\" (no payment, no inventory, no email).\n\n3. **Assign BCPs** — For each story, estimate Business Complexity Points (1–13). A 1-BCP story is a trivial change (one file, one concept). A 13-BCP story is a major feature across multiple modules. If a story exceeds 8 BCPs, consider splitting it.\n\n4. **Each story** writes:\n   - `eNNsYY-tasks.yaml` with `story_id`, `title`, `status`, `bcps`, `tasks[]` (each with `id`, `description`, `verify`, `status`)\n   - Story spec `.md` files are written by `plan-work` and follow countable-story-format.md\n   - The epic capsule manifest (`epic.yaml`) is updated to list the story ID and BCPs\n   - **Requirement deltas (e45s29):** Stories that alter existing behavior MUST carry `delta:` in `epic.yaml` (`ADDED` | `MODIFIED` | `REMOVED` | `RENAMED`). `plan-work` expands deltas into full before\u002Fafter requirement text.\n\n5. **Order by WSJF** in `release-plan.yaml` epic list — highest WSJF first. Weight-shortest-job-first ensures the highest value arrives earliest.\n\n6. **Validate slices** — Every slice must answer: \"If this story ships, does a user get new value?\" If the answer is \"no, they need a later story too\", the slice is too horizontal — cut vertically deeper.\n\n> **HARD GATE** — No horizontal-only slices (\"add all models\") without a vertical path that proves integration. Every story must be independently demonstrable, even if it only handles the happy path.\n\n> **HARD GATE** — Each task's `verify:` field must contain a runnable command (not \"manually check\" or \"review visually\"). If verification requires manual steps, prefix with `verify-script:` and write the steps in the story file.\n\n## Anti-Patterns\n\n- **Layer cakes** — \"Week 1: all models. Week 2: all controllers. Week 3: all views.\" This hides integration risk until the end. Every story must cut through all layers.\n- **Too-small slices** — If a slice takes \u003C 30 minutes to implement, it's probably noise. Combine with adjacent slices.\n- **Too-large slices** — If a slice takes > 3 days, it's an epic, not a story. Split further.\n\n## Output\n\n- `specs\u002Fepics\u002FeNN-slug\u002FeNNsYY-tasks.yaml` — per-story task breakdown with verify commands\n- `specs\u002Fepics\u002FeNN-slug\u002Fepic.yaml` — updated with story list and BCPs\n- `specs\u002Frelease-plan.yaml` — updated WSJF ordering (if needed)\n\n## Verify\n\n→ verify: `[ \"$(find specs\u002Fepics -name '*-tasks.yaml' 2>\u002Fdev\u002Fnull | wc -l | tr -d ' ')\" -gt 0 ]`\n\n\n\u003C!-- story: e03s01 -->\n","\u003C!-- story: e45s29 -->\n\n# Slice Tasks\n\n> **Spine position:** Step 2 — scope-work → slice-tasks → plan-work.\n\nProduce **epic capsule story tasks** in `specs\u002Fepics\u002FeNN-slug\u002F` — vertical slices, each independently deliverable and testable. Output: decoupled `eNNsYY-tasks.yaml` files with runnable verify commands. Legacy `specs\u002Fepics\u002F (see slice-tasks)` is deprecated; use capsule dirs + `execution-status.yaml`.\n\n## Pre-flight\n\n- [ ] Does `specs\u002Fproduct\u002FSCOPE_LATEST.yaml` exist? If not, run `scope-work` first — you can't slice what you haven't bounded.\n- [ ] Is the `release-plan.yaml` populated with the epics you're slicing? Epic IDs (e01, e02…) should exist before you create stories.\n- [ ] Do you understand the difference between a horizontal layer and a vertical slice? (See anti-patterns below.)\n\n## Process\n\n0. **Read planning-context.yaml** — If `specs\u002Fplanning-context.yaml` exists, read it first:\n   ```bash\n   test -f specs\u002Fplanning-context.yaml && echo \"Context found\" || echo \"No context — starting fresh\"\n   ```\n   Use `feature_name`, `constraints`, and `out_of_scope` to inform slice boundaries. `key_decisions` in the file may constrain how stories are cut (e.g., \"no external deps\" constrains slice 2). If absent, proceed normally.\n\n1. **Read context** — Read `specs\u002Fproduct\u002FSCOPE_LATEST.yaml` and\u002For `specs\u002Frelease-plan.yaml`. Understand what the epic delivers end-to-end.\n\n2. **Cut tracer-bullet slices** — Identify the thinnest possible vertical path through the stack that delivers user value. Start with this slice; it will catch integration issues first. For example:\n   - A search feature: first slice is \"user types query → API returns results\" (no filters, no pagination, no ranking — just the plumbing working end-to-end).\n   - A checkout flow: first slice is \"user clicks buy → order created\" (no payment, no inventory, no email).\n\n3. **Assign BCPs** — For each story, estimate Business Complexity Points (1–13). A 1-BCP story is a trivial change (one file, one concept). A 13-BCP story is a major feature across multiple modules. If a story exceeds 8 BCPs, consider splitting it.\n\n4. **Each story** writes:\n   - `eNNsYY-tasks.yaml` with `story_id`, `title`, `status`, `bcps`, `tasks[]` (each with `id`, `description`, `verify`, `status`)\n   - Story spec `.md` files are written by `plan-work` and follow countable-story-format.md\n   - The epic capsule manifest (`epic.yaml`) is updated to list the story ID and BCPs\n   - **Requirement deltas (e45s29):** Stories that alter existing behavior MUST carry `delta:` in `epic.yaml` (`ADDED` | `MODIFIED` | `REMOVED` | `RENAMED`). `plan-work` expands deltas into full before\u002Fafter requirement text.\n\n5. **Order by WSJF** in `release-plan.yaml` epic list — highest WSJF first. Weight-shortest-job-first ensures the highest value arrives earliest.\n\n6. **Validate slices** — Every slice must answer: \"If this story ships, does a user get new value?\" If the answer is \"no, they need a later story too\", the slice is too horizontal — cut vertically deeper.\n\n> **HARD GATE** — No horizontal-only slices (\"add all models\") without a vertical path that proves integration. Every story must be independently demonstrable, even if it only handles the happy path.\n\n> **HARD GATE** — Each task's `verify:` field must contain a runnable command (not \"manually check\" or \"review visually\"). If verification requires manual steps, prefix with `verify-script:` and write the steps in the story file.\n\n## Anti-Patterns\n\n- **Layer cakes** — \"Week 1: all models. Week 2: all controllers. Week 3: all views.\" This hides integration risk until the end. Every story must cut through all layers.\n- **Too-small slices** — If a slice takes \u003C 30 minutes to implement, it's probably noise. Combine with adjacent slices.\n- **Too-large slices** — If a slice takes > 3 days, it's an epic, not a story. Split further.\n\n## Output\n\n- `specs\u002Fepics\u002FeNN-slug\u002FeNNsYY-tasks.yaml` — per-story task breakdown with verify commands\n- `specs\u002Fepics\u002FeNN-slug\u002Fepic.yaml` — updated with story list and BCPs\n- `specs\u002Frelease-plan.yaml` — updated WSJF ordering (if needed)\n\n## Verify\n\n→ verify: `[ \"$(find specs\u002Fepics -name '*-tasks.yaml' 2>\u002Fdev\u002Fnull | wc -l | tr -d ' ')\" -gt 0 ]`\n\n\n\u003C!-- story: e03s01 -->\n",{"name":5,"model":34,"effort":27,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa","skills\u002Fslice-tasks",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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add danielvm-git\u002Fbigpowers --skill slice-tasks",{"tool":55,"command":56},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill slice-tasks",{"tool":58,"command":59},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill slice-tasks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fslice-tasks\u002FSKILL.md",true,[],[64,84,91,118,141,162],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":75,"publishedAt":35},"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",[70],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[76,77,78,79,80,81,82,24,83],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run","never",{"skillNo":85,"name":86,"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":87,"categories":88,"keywords":89,"publishedAt":35},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[90,81],"negative path",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":100,"publishedAt":35},"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",[97],{"categoryNo":98,"categoryName":99,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000002","文档处理",[101,102,103,104,105,106,107,108,109,27,26,110,111,112,34,113,114,115,116,117],"write","write document","document","documents","actionable","technical","methodology","high","bmad","when","minimal","bold","integrity","organize","sync","directory","guides",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":35},"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",[],[125,126,127,27,128,26,129,130,131,132,34,133,134,135,136,137,138,110,139,140],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":35},"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",[],[148,149,150,151,152,153,154,155,156,157,158,27,159,24,125,34,160,161],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","with","ci pipeline setup","git","workflows",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":179,"publishedAt":35},"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",[168,171,176],{"categoryNo":169,"categoryName":170,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":172,"categoryName":173,"taxonomyType":174,"taxonomyTypeDesc":175},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":177,"categoryName":178,"taxonomyType":174,"taxonomyTypeDesc":175},"01JBSEEDCAT000000000000033","数据分析师",[180,181,182,183,184,185,186,22,187,34,188,189,190,30,191,192,193,139,194,195],"dashboard","visual","visual dashboard","status","artifacts","http","plans","panel","start","release","opencode","browser","api","architecture","project status","http api"]