[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DEGVCXYGTKQEXPJA99FANE":3,"skill-same:01M7DEGVCXYGTKQEXPJA99FANE":124},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7DEGVCXYGTKQEXPJA99FANE","diagnosing-superpowers",null,"Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, \"it took too long\", \"why is it so expensive\", \"what is it doing\" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.","MichaelKinsy\u002Fpigpen","MichaelKinsy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54590707?v=4","01M7CYQK2FGYV1482DN7VHACJ6","Michael Kinsy","01M7DEAGVENVX1P76H737CT5FX",18,"MIT","https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: diagnosing-superpowers\ndescription: Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, \"it took too long\", \"why is it so expensive\", \"what is it doing\" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.\n---\n\n# Diagnosing Superpowers\n\n## Overview\n\nPin down with your human partner what went wrong in a session, read the\ntranscripts on disk, and report what happened with evidence. You report;\nyou do not diagnose superpowers. Whoever triages the bundle or the issue\ndecides whether superpowers changes.\n\n**Core principle:** Every finding cites `path:line`. No citation, no\nfinding. Every number comes from the transcript or from a command you ran,\nnever from memory.\n\n## Workflow\n\nCreate a todo per step. Steps 5–7 run only on their stated condition.\n\n1. **Problem intake.** Ask one question at a time until you can write a\n   statement naming the session(s), the turn range if known, what your\n   partner expected, what happened, and the observable they care about\n   (wall-clock, tokens, repeated actions, one specific action). \"It took\n   too long\" is a complaint, not a problem statement. Note whether the\n   goal is a superpowers bug report.\n2. **Locate.** Resolve each session to verified absolute filesystem paths using\n   `references\u002Fsession-discovery.md`. Confirm a past session by quoting its\n   first prompt and timestamp, and list every candidate you rejected with the\n   reason, or \"none\". Enumerate subagent transcripts. Create\n   `~\u002F.superpowers\u002Fdiagnosing-superpowers\u002F\u003Csession-id>\u002F`, tell your\n   partner the path, and fill `templates\u002Fcase.md` there, following its\n   provenance rules for environment and skill observations.\n3. **Triage.** Read the region around the reported problem yourself. Then\n   dispatch one analyst subagent per dimension in parallel, each given the\n   case file path, `prompts\u002Fanalyst-common.md`, and one dimension file from\n   `prompts\u002F`: `skill-timeline.md`,\n   `plan-adherence.md`, `repeated-work.md`, `stumbles.md`,\n   `quality-evidence.md`, `request-conflicts.md`, `cost-and-time.md`.\n   Split a dimension by turn range when the transcript is long. Discard\n   any returned finding without `path:line`.\n4. **Report.** Fill every section of `templates\u002Freport.md` in order, write\n   it to the workspace, show it, and give the path. Check what cited content\n   actually proves and preserve the supporting case; a symlink alias is not a\n   redundant copy.\n5. **GitHub issues** — when report §7 says possible or likely, or your\n   partner asks. Search open and closed issues for the symptoms per\n   `references\u002Fgithub-issues.md`. Show matches and suggest adding the\n   report to the closest. If none match, fill `templates\u002Fissue.md`, write\n   it to the workspace, show the exact text, and create the issue only\n   after approval. `gh` cannot attach files; if a bundle exists, give\n   your partner its path to attach in the browser.\n6. **Export** — only when your partner asks for a bundle; never build one\n   unprompted. If the intake goal was a bug report, say once that a\n   scrubbed bundle is available on request, then wait. Ask the redaction\n   level, stating what each includes: skeleton (no tool-result bodies),\n   evidence (bodies only for cited events), full. Build the bundle per\n   `templates\u002Fbundle-README.md`, dispatch `prompts\u002Fscrub.md`, then\n   `prompts\u002Fscrub-audit.md`, repeating both until the audit returns CLEAN.\n   Complete the bundle template's evidence check and reconciliation before\n   showing the final scrub log, file list, and privacy and evidence outcomes.\n   Archive (`zip -r` or `tar -czf`) only after approval. With the archive\n   path, state what it contains, point at the scrub log for replacements, and\n   say scrubbing can miss things: they must review every file before sharing.\n7. **Similar sessions** — when asked. Turn confirmed findings into a\n   signature, list candidates by mtime and size, find marker line numbers,\n   dispatch `prompts\u002Fsimilar-session.md` per candidate in parallel, and\n   append report §9.\n\n## Quick reference\n\nAll seven analysts always run. This table says which region to read\nyourself in step 3 and which findings to lead with in the verdict.\n\n| Complaint | Read first, lead with |\n|---|---|\n| \"It took too long\" | cost-and-time, stumbles |\n| \"Why did it do this extra work?\" | repeated-work, plan-adherence |\n| \"Why is it so expensive?\" | cost-and-time |\n| \"What the hell is it doing?\" (still running) | skill-timeline; note in-progress in coverage |\n| \"It ignored the plan\" | plan-adherence, compaction lines first |\n| \"Skill X never fired\" | skill-timeline |\n\n## Hard rules\n\n- **Context safety.** One transcript line can be a megabyte. Follow\n  `references\u002Fcontext-safety.md` on every session file, every time.\n- **Read-only.** Never modify, move, or delete a session file.\n- **Exact paths to subagents.** A subagent's \"current session\" is its\n  own. Pass absolute paths and ids.\n- **Human prompts only.** Hook output, system reminders, and tool results\n  are not your partner's words. In a subagent transcript, \"user\" is the\n  parent agent.\n- **No superpowers diagnosis.** Report §7 states involvement and stops.\n  Never name a defect in a skill or propose a change. Your partner\n  pressing for a fix does not waive this; point at the issue step and\n  mention that a bundle is available on request. No advice to your\n  partner either.\n- **Approval gates.** No archive before your partner has seen the scrub\n  log and file list. No issue or comment before they approve the exact\n  text.\n- **Intake before analysis.** Nothing in steps 2–7 starts until your\n  partner has answered. If they are away, write the questions and stop.\n  A statement you reconstructed for them is not an answer. An\n  already-scoped request — one specific event, what is running now, or\n  the analysis to run — is itself the statement: answer it, then ask.\n  A whole-session \"why\" is a complaint.\n\n## Red Flags\n\n| Thought | Reality |\n|---------|---------|\n| \"The problem is obvious, skip intake\" | The problem statement scopes everything. Ask. |\n| \"They're away, so I'll reconstruct the statement\" | You cannot reconstruct what they wanted. Write the questions and stop. |\n| \"I'll sweep everything now and ask at the end\" | An unscoped sweep spends their budget on the wrong question. Ask first. |\n| \"They want a bug report, so I'll build the bundle now\" | The bundle is their session data, packaged. Build it only when they ask for it. |\n| \"Small, targeted edit, no restructuring needed\" | Not your call, however small. Report the evidence; the triager decides. |\n| \"The price per token is well known\" | Numbers you did not compute from the transcript are invented. Cite or drop. |\n","# Diagnosing Superpowers\n\n## Overview\n\nPin down with your human partner what went wrong in a session, read the\ntranscripts on disk, and report what happened with evidence. You report;\nyou do not diagnose superpowers. Whoever triages the bundle or the issue\ndecides whether superpowers changes.\n\n**Core principle:** Every finding cites `path:line`. No citation, no\nfinding. Every number comes from the transcript or from a command you ran,\nnever from memory.\n\n## Workflow\n\nCreate a todo per step. Steps 5–7 run only on their stated condition.\n\n1. **Problem intake.** Ask one question at a time until you can write a\n   statement naming the session(s), the turn range if known, what your\n   partner expected, what happened, and the observable they care about\n   (wall-clock, tokens, repeated actions, one specific action). \"It took\n   too long\" is a complaint, not a problem statement. Note whether the\n   goal is a superpowers bug report.\n2. **Locate.** Resolve each session to verified absolute filesystem paths using\n   `references\u002Fsession-discovery.md`. Confirm a past session by quoting its\n   first prompt and timestamp, and list every candidate you rejected with the\n   reason, or \"none\". Enumerate subagent transcripts. Create\n   `~\u002F.superpowers\u002Fdiagnosing-superpowers\u002F\u003Csession-id>\u002F`, tell your\n   partner the path, and fill `templates\u002Fcase.md` there, following its\n   provenance rules for environment and skill observations.\n3. **Triage.** Read the region around the reported problem yourself. Then\n   dispatch one analyst subagent per dimension in parallel, each given the\n   case file path, `prompts\u002Fanalyst-common.md`, and one dimension file from\n   `prompts\u002F`: `skill-timeline.md`,\n   `plan-adherence.md`, `repeated-work.md`, `stumbles.md`,\n   `quality-evidence.md`, `request-conflicts.md`, `cost-and-time.md`.\n   Split a dimension by turn range when the transcript is long. Discard\n   any returned finding without `path:line`.\n4. **Report.** Fill every section of `templates\u002Freport.md` in order, write\n   it to the workspace, show it, and give the path. Check what cited content\n   actually proves and preserve the supporting case; a symlink alias is not a\n   redundant copy.\n5. **GitHub issues** — when report §7 says possible or likely, or your\n   partner asks. Search open and closed issues for the symptoms per\n   `references\u002Fgithub-issues.md`. Show matches and suggest adding the\n   report to the closest. If none match, fill `templates\u002Fissue.md`, write\n   it to the workspace, show the exact text, and create the issue only\n   after approval. `gh` cannot attach files; if a bundle exists, give\n   your partner its path to attach in the browser.\n6. **Export** — only when your partner asks for a bundle; never build one\n   unprompted. If the intake goal was a bug report, say once that a\n   scrubbed bundle is available on request, then wait. Ask the redaction\n   level, stating what each includes: skeleton (no tool-result bodies),\n   evidence (bodies only for cited events), full. Build the bundle per\n   `templates\u002Fbundle-README.md`, dispatch `prompts\u002Fscrub.md`, then\n   `prompts\u002Fscrub-audit.md`, repeating both until the audit returns CLEAN.\n   Complete the bundle template's evidence check and reconciliation before\n   showing the final scrub log, file list, and privacy and evidence outcomes.\n   Archive (`zip -r` or `tar -czf`) only after approval. With the archive\n   path, state what it contains, point at the scrub log for replacements, and\n   say scrubbing can miss things: they must review every file before sharing.\n7. **Similar sessions** — when asked. Turn confirmed findings into a\n   signature, list candidates by mtime and size, find marker line numbers,\n   dispatch `prompts\u002Fsimilar-session.md` per candidate in parallel, and\n   append report §9.\n\n## Quick reference\n\nAll seven analysts always run. This table says which region to read\nyourself in step 3 and which findings to lead with in the verdict.\n\n| Complaint | Read first, lead with |\n|---|---|\n| \"It took too long\" | cost-and-time, stumbles |\n| \"Why did it do this extra work?\" | repeated-work, plan-adherence |\n| \"Why is it so expensive?\" | cost-and-time |\n| \"What the hell is it doing?\" (still running) | skill-timeline; note in-progress in coverage |\n| \"It ignored the plan\" | plan-adherence, compaction lines first |\n| \"Skill X never fired\" | skill-timeline |\n\n## Hard rules\n\n- **Context safety.** One transcript line can be a megabyte. Follow\n  `references\u002Fcontext-safety.md` on every session file, every time.\n- **Read-only.** Never modify, move, or delete a session file.\n- **Exact paths to subagents.** A subagent's \"current session\" is its\n  own. Pass absolute paths and ids.\n- **Human prompts only.** Hook output, system reminders, and tool results\n  are not your partner's words. In a subagent transcript, \"user\" is the\n  parent agent.\n- **No superpowers diagnosis.** Report §7 states involvement and stops.\n  Never name a defect in a skill or propose a change. Your partner\n  pressing for a fix does not waive this; point at the issue step and\n  mention that a bundle is available on request. No advice to your\n  partner either.\n- **Approval gates.** No archive before your partner has seen the scrub\n  log and file list. No issue or comment before they approve the exact\n  text.\n- **Intake before analysis.** Nothing in steps 2–7 starts until your\n  partner has answered. If they are away, write the questions and stop.\n  A statement you reconstructed for them is not an answer. An\n  already-scoped request — one specific event, what is running now, or\n  the analysis to run — is itself the statement: answer it, then ask.\n  A whole-session \"why\" is a complaint.\n\n## Red Flags\n\n| Thought | Reality |\n|---------|---------|\n| \"The problem is obvious, skip intake\" | The problem statement scopes everything. Ask. |\n| \"They're away, so I'll reconstruct the statement\" | You cannot reconstruct what they wanted. Write the questions and stop. |\n| \"I'll sweep everything now and ask at the end\" | An unscoped sweep spends their budget on the wrong question. Ask first. |\n| \"They want a bug report, so I'll build the bundle now\" | The bundle is their session data, packaged. Build it only when they ask for it. |\n| \"Small, targeted edit, no restructuring needed\" | Not your call, however small. Report the evidence; the triager decides. |\n| \"The price per token is well known\" | Numbers you did not compute from the transcript are invented. Cite or drop. |\n",{"name":5,"description":7},"main","262f2fbc0c721ee470028905399e2cbe1d652847","components\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers",5,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen","https:\u002F\u002Fgithub.com\u002FMichaelKinsy","Systems & platform engineer @ HPE | \r\nBSU Alumni 21.              |\r\nBuilding AI\u002Fsoftware infrastructure, tools, and open-source software.","2026-11-15 06:15:23",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add MichaelKinsy\u002Fpigpen --skill diagnosing-superpowers",{"tool":38,"command":39},"bunx","bunx skills add MichaelKinsy\u002Fpigpen --skill diagnosing-superpowers",{"tool":41,"command":42},"pnpm","pnpm dlx skills add MichaelKinsy\u002Fpigpen --skill diagnosing-superpowers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"prompts\u002Fanalyst-common.md","REFERENCE","参考文档",1582,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fanalyst-common.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"prompts\u002Fcost-and-time.md",1640,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fcost-and-time.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"prompts\u002Fplan-adherence.md",1637,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fplan-adherence.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"prompts\u002Fquality-evidence.md",1476,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fquality-evidence.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"prompts\u002Frepeated-work.md",1469,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Frepeated-work.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"prompts\u002Frequest-conflicts.md",1011,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Frequest-conflicts.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"prompts\u002Fscrub-audit.md",1363,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fscrub-audit.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"prompts\u002Fscrub.md",1471,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fscrub.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"prompts\u002Fsimilar-session.md",1711,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fsimilar-session.md",{"path":85,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":86,"sourceHtmlUrl":87},"prompts\u002Fskill-timeline.md",1646,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fskill-timeline.md",{"path":89,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":90,"sourceHtmlUrl":91},"prompts\u002Fstumbles.md",1330,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Fprompts\u002Fstumbles.md",{"path":93,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fcontext-safety.md",990,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Freferences\u002Fcontext-safety.md",{"path":97,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fgithub-issues.md",1644,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Freferences\u002Fgithub-issues.md",{"path":101,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fredaction-policy.md",2243,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Freferences\u002Fredaction-policy.md",{"path":105,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fsession-discovery.md",1859,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Freferences\u002Fsession-discovery.md",{"path":109,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":110,"sourceHtmlUrl":111},"templates\u002Fbundle-README.md",3672,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Ftemplates\u002Fbundle-README.md",{"path":113,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":114,"sourceHtmlUrl":115},"templates\u002Fcase.md",2983,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Ftemplates\u002Fcase.md",{"path":117,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":118,"sourceHtmlUrl":119},"templates\u002Fissue.md",1851,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Ftemplates\u002Fissue.md",{"path":121,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":122,"sourceHtmlUrl":123},"templates\u002Freport.md",2359,"https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fport\u002Foracle\u002Fskills\u002Fdiagnosing-superpowers\u002Ftemplates\u002Freport.md",[125,132,139,146,153,160],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":19},"01M7DEP7TB04M3XJ8Z0NGKW97X","pigpen-superpowers-writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fskills\u002Fpigpen-superpowers-writing-skills\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":19},"01M7DEP3W24SKFVMRYWJQB1073","pigpen-superpowers-writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fskills\u002Fpigpen-superpowers-writing-plans\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":19},"01M7DENZ1ZPD21VGVXBQKE8Z4F","pigpen-superpowers-verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fskills\u002Fpigpen-superpowers-verification-before-completion\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":19},"01M7DENV9CTFN7KAGPA9BEMGQ1","pigpen-superpowers-using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fskills\u002Fpigpen-superpowers-using-superpowers\u002FSKILL.md",[],[],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":19},"01M7DENQR56MYZJAAWDEX1YEMZ","pigpen-superpowers-using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fskills\u002Fpigpen-superpowers-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":19},"01M7DENFGH1S9583WWJ4EY9RCN","pigpen-superpowers-test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FMichaelKinsy\u002Fpigpen\u002Fblob\u002Fmain\u002Fcomponents\u002Fsuperpowers\u002Fskills\u002Fpigpen-superpowers-test-driven-development\u002FSKILL.md",[],[]]