diagnosing-superpowers · Claude / Claude Code · OpenAI · Codex · Gemini CLI · Grok Build
작업 기록에서 계획 누락, 반복 작업과 스킬 사용 문제를 점검합니다.
AI가 같은 일을 반복하거나 계획 없이 수정해 작업량이 늘어났을 때 사용하는 진단 스킬입니다. 세션 기록을 읽고 어디에서 흐름이 꼬였는지 살펴봅니다.
불편했던 지점과 작업 기록을 준비해보세요. 계획 누락과 불필요한 반복, 스킬 선택의 문제를 구분한 뒤 다음 작업에서 바꿀 방법을 정리할 수 있습니다.
“이 작업 기록에서 같은 파일을 반복해서 수정한 이유를 찾아줘. 필요한 확인과 불필요한 반복을 나누고 진행 방법을 개선해줘.”
받을 수 있는 결과반복·비용 증가 원인과 개선안
사용 중인 코딩 에이전트에 Superpowers를 설치해야 합니다. 에이전트별 제공 도구는 다를 수 있습니다.
사용하는 환경에 맞는 방법 하나를 선택하세요. Superpowers 전체 패키지를 설치하고 새 세션에서 작업을 요청하면 관련 스킬이 호출됩니다.
Claude Code: /plugin install superpowers@claude-plugins-official Codex 앱: Plugins → Coding → Superpowers 설치 Codex CLI: /plugins → Superpowers → Install Plugin Gemini CLI 터미널: gemini extensions install https://github.com/obra/superpowers
“diagnosing-superpowers 스킬을 사용해줘. 입력 자료: 세션 기록과 불편했던 지점”처럼 요청하세요. 위의 예시를 내 자료에 맞게 바꿔도 좋아요.
예상 결과는 ‘반복·비용 증가 원인과 개선안’입니다. 필요한 내용이 포함됐는지 확인하세요. 입력 자료의 사실·숫자와 결과를 대조하고, 부족한 부분을 이어서 요청하세요.
제작자 원본 2026-10-04 확인 · 설치 안내 2026-10-04 확인 · 실제 설치·실행 미검증
모델 사용 요금과 연결 앱 요금은 이용 중인 서비스의 정책을 따릅니다.
설치 안내 출처--- name: diagnosing-superpowers description: 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. --- # Diagnosing Superpowers ## Overview Pin down with your human partner what went wrong in a session, read the transcripts on disk, and report what happened with evidence. You report; you do not diagnose superpowers. Whoever triages the bundle or the issue decides whether superpowers changes. **Core principle:** Every finding cites `path:line`. No citation, no finding. Every number comes from the transcript or from a command you ran, never from memory. ## Workflow Create a todo per step. Steps 5–7 run only on their stated condition. 1. **Problem intake.** Ask one question at a time until you can write a statement naming the session(s), the turn range if known, what your partner expected, what happened, and the observable they care about--- name: diagnosing-superpowers description: 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. --- # Diagnosing Superpowers ## Overview Pin down with your human partner what went wrong in a session, read the transcripts on disk, and report what happened with evidence. You report; you do not diagnose superpowers. Whoever triages the bundle or the issue decides whether superpowers changes. **Core principle:** Every finding cites `path:line`. No citation, no finding. Every number comes from the transcript or from a command you ran, never from memory. ## Workflow Create a todo per step. Steps 5–7 run only on their stated condition. 1. **Problem intake.** Ask one question at a time until you can write a statement naming the session(s), the turn range if known, what your partner expected, what happened, and the observable they care about (wall-clock, tokens, repeated actions, one specific action). "It took too long" is a complaint, not a problem statement. Note whether the goal is a superpowers bug report. 2. **Locate.** Resolve each session to verified absolute filesystem paths using `references/session-discovery.md`. Confirm a past session by quoting its first prompt and timestamp, and list every candidate you rejected with the reason, or "none". Enumerate subagent transcripts. Create `~/.superpowers/diagnosing-superpowers/<session-id>/`, tell your partner the path, and fill `templates/case.md` there, following its provenance rules for environment and skill observations. 3. **Triage.** Read the region around the reported problem yourself. Then dispatch one analyst subagent per dimension in parallel, each given the case file path, `prompts/analyst-common.md`, and one dimension file from `prompts/`: `skill-timeline.md`, `plan-adherence.md`, `repeated-work.md`, `stumbles.md`, `quality-evidence.md`, `request-conflicts.md`, `cost-and-time.md`. Split a dimension by turn range when the transcript is long. Discard any returned finding without `path:line`. 4. **Report.** Fill every section of `templates/report.md` in order, write it to the workspace, show it, and give the path. Check what cited content actually proves and preserve the supporting case; a symlink alias is not a redundant copy. 5. **GitHub issues** — when report §7 says possible or likely, or your partner asks. Search open and closed issues for the symptoms per `references/github-issues.md`. Show matches and suggest adding the report to the closest. If none match, fill `templates/issue.md`, write it to the workspace, show the exact text, and create the issue only after approval. `gh` cannot attach files; if a bundle exists, give your partner its path to attach in the browser. 6. **Export** — only when your partner asks for a bundle; never build one unprompted. If the intake goal was a bug report, say once that a scrubbed bundle is available on request, then wait. Ask the redaction level, stating what each includes: skeleton (no tool-result bodies), evidence (bodies only for cited events), full. Build the bundle per `templates/bundle-README.md`, dispatch `prompts/scrub.md`, then `prompts/scrub-audit.md`, repeating both until the audit returns CLEAN. Complete the bundle template's evidence check and reconciliation before showing the final scrub log, file list, and privacy and evidence outcomes. Archive (`zip -r` or `tar -czf`) only after approval. With the archive path, state what it contains, point at the scrub log for replacements, and say scrubbing can miss things: they must review every file before sharing. 7. **Similar sessions** — when asked. Turn confirmed findings into a signature, list candidates by mtime and size, find marker line numbers, dispatch `prompts/similar-session.md` per candidate in parallel, and append report §9. ## Quick reference All seven analysts always run. This table says which region to read yourself in step 3 and which findings to lead with in the verdict. | Complaint | Read first, lead with | |---|---| | "It took too long" | cost-and-time, stumbles | | "Why did it do this extra work?" | repeated-work, plan-adherence | | "Why is it so expensive?" | cost-and-time | | "What the hell is it doing?" (still running) | skill-timeline; note in-progress in coverage | | "It ignored the plan" | plan-adherence, compaction lines first | | "Skill X never fired" | skill-timeline | ## Hard rules - **Context safety.** One transcript line can be a megabyte. Follow `references/context-safety.md` on every session file, every time. - **Read-only.** Never modify, move, or delete a session file. - **Exact paths to subagents.** A subagent's "current session" is its own. Pass absolute paths and ids. - **Human prompts only.** Hook output, system reminders, and tool results are not your partner's words. In a subagent transcript, "user" is the parent agent. - **No superpowers diagnosis.** Report §7 states involvement and stops. Never name a defect in a skill or propose a change. Your partner pressing for a fix does not waive this; point at the issue step and mention that a bundle is available on request. No advice to your partner either. - **Approval gates.** No archive before your partner has seen the scrub log and file list. No issue or comment before they approve the exact text. - **Intake before analysis.** Nothing in steps 2–7 starts until your partner has answered. If they are away, write the questions and stop. A statement you reconstructed for them is not an answer. An already-scoped request — one specific event, what is running now, or the analysis to run — is itself the statement: answer it, then ask. A whole-session "why" is a complaint. ## Red Flags | Thought | Reality | |---------|---------| | "The problem is obvious, skip intake" | The problem statement scopes everything. Ask. | | "They're away, so I'll reconstruct the statement" | You cannot reconstruct what they wanted. Write the questions and stop. | | "I'll sweep everything now and ask at the end" | An unscoped sweep spends their budget on the wrong question. Ask first. | | "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. | | "Small, targeted edit, no restructuring needed" | Not your call, however small. Report the evidence; the triager decides. | | "The price per token is well known" | Numbers you did not compute from the transcript are invented. Cite or drop. |
Original skill: obra/superpowers/skills/diagnosing-superpowers/SKILL.md Source: https://github.com/obra/superpowers/blob/8ca22dba9a94f28898bbce59f2537ff4d87c747d/skills/diagnosing-superpowers/SKILL.md License: MIT MIT License Copyright (c) 2025 Jesse Vincent Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SKILL.md 본문입니다. 원문에서 참조하는 스크립트·보조 파일은 원본 패키지에 포함되어 있습니다.