[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HAZN6BQVQJ4HVZ8FD8B99":3,"skill-same:01M71HAZN6BQVQJ4HVZ8FD8B99":66},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M71HAZN6BQVQJ4HVZ8FD8B99","diagnose-stall",null,"Diagnose why agent orchestration stopped producing progress — silent stalls in \u002Floop, dispatch-agents, or execute-plan. Use when work appears hung, no output for several minutes, or a subagent never returned.","danielvm-git\u002Fbigpowers","danielvm-git","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1020864?v=4","01M71H1N1CTQ529S0KN7KETVG6","Daniel V M","01M71H1N218Y3S8WHCJ58NPRSW",292,"MIT","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.codebuddy\u002Fskills\u002Fdiagnose-stall\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"diagnose","diagnose stall","execute","minutes","dispatch","output","use","for","why","progress","haiku","plan","work","subagent","when","orchestration","loop","agent orchestration","never","2026-11-10 10:12:30",false,"---\nname: diagnose-stall\nmodel: haiku\ndescription: \"Diagnose why agent orchestration stopped producing progress — silent stalls in \u002Floop, dispatch-agents, or execute-plan. Use when work appears hung, no output for several minutes, or a subagent never returned.\"\n---\n\n# Diagnose Stall\n\n> **HARD GATE** — Do NOT restart work blindly. Run this diagnostic first when orchestration goes quiet without an explicit terminal state.\n\nExplicit handler for silent stalls in long-running agent workflows (`\u002Floop`, `dispatch-agents`, `execute-plan`, `build-epic` resume mode).\n\n## Stall signals\n\n| Signal | Likely cause |\n|--------|----------------|\n| No stdout for >5 min on a monitored loop tick | Sleep\u002Fwatcher misconfigured or prompt never re-armed |\n| Subagent dispatched but no completion message | Agent hung, blocked on approval, or scope too large |\n| `dispatch-agents` cycle 3 reached with gaps | Circuit exhausted — needs human escalation |\n| Verify command running >15 min | Missing timeout or waiting on external service |\n| `handoff.next_skill` unchanged across turns | Prior skill never wrote handoff |\n\n## Process\n\n1. **Read state** — `specs\u002Fstate.yaml`: `handoff.next_skill`, `active_flow`, `metrics.story_start`, open decisions.\n2. **Check locks** — `bash scripts\u002Fcheck-stale-locks.sh` if present; read `specs\u002Fagent-locks.yaml`.\n3. **Inspect terminals** — list background shells; note PIDs, last output timestamp, exit codes.\n4. **Classify stall type:**\n   - **waiting_approval** — tool blocked on user consent\n   - **blocked_dependency** — prior task incomplete or red gate\n   - **agent_exhausted** — max iterations\u002Fcycles reached\n   - **misconfigured_loop** — duplicate sentinel, wrong regex, or sleeper not re-armed\n   - **external_io** — network, CI, or deploy wait without timeout\n   - **unknown** — escalate with evidence bundle\n5. **Recommend recovery** — one action only (resume, kill PID, re-dispatch with smaller brief, escalate to user).\n6. **Write report** — `specs\u002Fverifications\u002FSTALL-\u003Ctimestamp>.md` with classification, evidence, and recommended next skill.\n\n## Integration\n\n| Caller | When to invoke |\n|--------|----------------|\n| `\u002Floop` (Cursor) | After two consecutive ticks with no observable progress |\n| `dispatch-agents` | When a wave exceeds expected duration with zero returns |\n| `execute-plan` | When a step checkpoint is overdue |\n| User | \"Why did this stop?\" \u002F \"Nothing is happening\" |\n\n## Verify\n\n→ verify: `test -f specs\u002Fstate.yaml`\n\n## Handoff\n\nGate: READY → next: survey-context (if state unclear) or resume prior skill from `state.yaml`\nWrites: `specs\u002Fverifications\u002FSTALL-*.md`\n","# Diagnose Stall\n\n> **HARD GATE** — Do NOT restart work blindly. Run this diagnostic first when orchestration goes quiet without an explicit terminal state.\n\nExplicit handler for silent stalls in long-running agent workflows (`\u002Floop`, `dispatch-agents`, `execute-plan`, `build-epic` resume mode).\n\n## Stall signals\n\n| Signal | Likely cause |\n|--------|----------------|\n| No stdout for >5 min on a monitored loop tick | Sleep\u002Fwatcher misconfigured or prompt never re-armed |\n| Subagent dispatched but no completion message | Agent hung, blocked on approval, or scope too large |\n| `dispatch-agents` cycle 3 reached with gaps | Circuit exhausted — needs human escalation |\n| Verify command running >15 min | Missing timeout or waiting on external service |\n| `handoff.next_skill` unchanged across turns | Prior skill never wrote handoff |\n\n## Process\n\n1. **Read state** — `specs\u002Fstate.yaml`: `handoff.next_skill`, `active_flow`, `metrics.story_start`, open decisions.\n2. **Check locks** — `bash scripts\u002Fcheck-stale-locks.sh` if present; read `specs\u002Fagent-locks.yaml`.\n3. **Inspect terminals** — list background shells; note PIDs, last output timestamp, exit codes.\n4. **Classify stall type:**\n   - **waiting_approval** — tool blocked on user consent\n   - **blocked_dependency** — prior task incomplete or red gate\n   - **agent_exhausted** — max iterations\u002Fcycles reached\n   - **misconfigured_loop** — duplicate sentinel, wrong regex, or sleeper not re-armed\n   - **external_io** — network, CI, or deploy wait without timeout\n   - **unknown** — escalate with evidence bundle\n5. **Recommend recovery** — one action only (resume, kill PID, re-dispatch with smaller brief, escalate to user).\n6. **Write report** — `specs\u002Fverifications\u002FSTALL-\u003Ctimestamp>.md` with classification, evidence, and recommended next skill.\n\n## Integration\n\n| Caller | When to invoke |\n|--------|----------------|\n| `\u002Floop` (Cursor) | After two consecutive ticks with no observable progress |\n| `dispatch-agents` | When a wave exceeds expected duration with zero returns |\n| `execute-plan` | When a step checkpoint is overdue |\n| User | \"Why did this stop?\" \u002F \"Nothing is happening\" |\n\n## Verify\n\n→ verify: `test -f specs\u002Fstate.yaml`\n\n## Handoff\n\nGate: READY → next: survey-context (if state unclear) or resume prior skill from `state.yaml`\nWrites: `specs\u002Fverifications\u002FSTALL-*.md`\n",{"name":5,"model":29,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".codebuddy\u002Fskills\u002Fdiagnose-stall",23,"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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add danielvm-git\u002Fbigpowers --skill diagnose-stall",{"tool":58,"command":59},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill diagnose-stall",{"tool":61,"command":62},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill diagnose-stall","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.codebuddy\u002Fskills\u002Fdiagnose-stall\u002FSKILL.md",true,[],[67,86,93,121,144,165],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":78,"publishedAt":38},"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",[73],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[79,80,81,82,83,84,85,26,37],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run",{"skillNo":87,"name":88,"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":89,"categories":90,"keywords":91,"publishedAt":38},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[92,84],"negative path",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":102,"publishedAt":38},"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",[99],{"categoryNo":100,"categoryName":101,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000002","文档处理",[103,104,105,106,107,108,109,110,111,112,25,33,113,114,115,116,117,118,119,120],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","minimal","bold","sonnet","integrity","organize","sync","directory","guides",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":38},"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",[],[128,129,130,112,131,25,132,133,134,135,115,136,137,138,139,140,141,33,142,143],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":38},"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",[],[151,152,153,154,155,156,157,158,159,160,161,112,162,26,128,115,163,164],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","with","ci pipeline setup","git","workflows",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":182,"publishedAt":38},"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",[171,174,179],{"categoryNo":172,"categoryName":173,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":175,"categoryName":176,"taxonomyType":177,"taxonomyTypeDesc":178},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":180,"categoryName":181,"taxonomyType":177,"taxonomyTypeDesc":178},"01JBSEEDCAT000000000000033","数据分析师",[183,184,185,186,187,188,189,190,191,115,192,193,194,30,195,196,197,142,198,199],"dashboard","visual","visual dashboard","status","artifacts","http","plans","planning","panel","start","release","opencode","browser","api","architecture","project status","http api"]