obra/superpowers
An agentic skills framework & software development methodology that works.
https://skillcdn.ai/gh/obra/superpowers내 AI에 이 주소를 연결하면 이 스킬들을 쓸 수 있어요. 연결 방법 보기
- 기본 브랜치
main - 커밋
22f0b46 - 라이선스
MIT - 검색단어와 의미
저장소 둘러보기
스킬과 문서의 원문에서 단어와 의미로 찾습니다. 화면용 번역은 검색되지 않아요.
스킬
- brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).MIT
- diagnosing-superpowersUse 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.MIT
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesMIT
- executing-plansUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableMIT
- finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the workMIT
- receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationMIT
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsMIT
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionMIT
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesMIT
- test-driven-developmentUse when implementing any feature or bugfix, before writing implementation codeMIT
- using-git-worktreesUse 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 fallbackMIT
- using-superpowersUse when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questionsMIT
- verification-before-completionUse 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 alwaysMIT
- writing-plansUse when you have a spec or requirements for a multi-step task, before touching codeMIT
- writing-skillsUse when creating new skills, editing existing skills, or verifying skills work before deploymentMIT