據 AlphaMoat 統計,截至 2026-10,Superpowers 累計下載 52,527 次、獲 75 個星標,按累計下載量在本次參與排名的 10,914 個 AI 技能中排名第 472 位,在「開發程式設計」分類(1,069 個)中排名第 28 位。
列表預設按累計下載量排序,也可按星標排序;詳情頁排名按累計下載量計算。
| 平台 | 累計下載 | 星標 | 評論 |
|---|---|---|---|
| SkillHub ↗ | 5.3萬 | 75 | — |
各平台的計數口徑不同,統計時間不一致。
A complete software development methodology and skill composition system, ported from obra/superpowers. Provides structured, repeatable workflow: brainstorming, design, planning, TDD, subagent-driven dev, code review, finishing branch. Use for coding, building projects, refactoring, bug fixing, or any programming tasks.
| 月份 | 累計下載 | 環比 | 星標 |
|---|---|---|---|
| 2026-10 | 5.3萬 | — | 75 |
| 2026-09 | 2.2萬 | — | 74 |
以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 2026-11-20。
--- name: superpowers description: "A complete software development methodology and skill composition system, ported from obra/superpowers. Provides structured, repeatable workflow: brainstorming, design, planning, TDD, subagent-driven dev, code review, finishing branch. Use for coding, building projects, refactoring, bug fixing, or any programming tasks." --- # Superpowers ## Overview Superpowers is a complete software development methodology that provides AI agents with a structured, repeatable workflow. Ported from the obra/superpowers project, it breaks down the software development process into 7 core phases, each with dedicated skills and checkpoints to ensure high-quality, maintainable code output.
## Core Workflow Superpowers follows a strict 7-phase workflow. Each phase is mandatory and cannot be skipped: ### 1. Brainstorming **Trigger**: Automatically activates at the start of any development task. **Goal**: Clarify the user's real needs through questioning, explore alternatives, and produce a verifiable design document. **Key Actions**: - Ask what the user really wants to achieve (not just surface requirements) - Explore multiple design approaches and trade-offs - Break design into readable chunks (max 200 words each) - Generate design document and save to `design.md` - Get user sign-off on the design ### 2. Design Validation **Trigger**: After Brainstorming completes. **Goal**: Ensure the design is complete, feasible, and meets user expectations. **Key Actions**: - Present design chunks for user review - Ask "Is this section clear?" - Confirm technical feasibility and constraints - Record feedback and update design ### 3. Implementation Planning **Trigger**: After design validation passes. **Goal**: Decompose the design into executable, fine-grained development tasks. **Key Actions**: - Create detailed task list, each task taking 2-5 minutes - Each task includes: exact file paths, complete code, verification steps - Follow YAGNI (You Aren't Gonna Need It) and DRY (Don't Repeat Yourself) - Generate plan document and save to `plan.md` ### 4. Test-Driven Development (TDD) **Trigger**: Automatically activates during implementation. **Goal**: Enforce the Red-Green-Refactor cycle. **Key Actions**: - Write a failing test first (Red) - Write minimal code to pass the test (Green) - Refactor to keep code clean - Delete any code written before tests - Follow this cycle for every feature ### 5. Subagent-Driven Development **Trigger**: After plan approval. **Goal**: Use subagents to execute tasks in parallel or sequentially. **Key Actions**: - Create fresh subagent per task - Two-stage review: spec compliance, then code quality - Set human checkpoints during batch execution - Stop and report immediately if subagent deviates from plan ### 6. Code Review **Trigger**: Between tasks or upon completion. **Goal**: Ensure code meets plan and quality standards. **Key Actions**: - Review code against the plan - Report issues by severity: Critical (blocking), Major, Minor - Critical issues must be fixed before proceeding - Generate review report and save to `review.md` ### 7. Finishing Development Branch **Trigger**: After all tasks complete. **Goal**: Cleanly finish the development cycle. **Key Actions**: - Verify all tests pass - Present options: merge, create PR, keep branch, discard - Clean up workspace - Generate final report ## Core Principles ### 1. Test-Driven Development - Always write tests first - Red-Green-Refactor cycle - Tests serve as documentation and design tools ### 2. Systematic over Ad-Hoc - Follow process rather than guessing - Every decision has a rationale - Document all assumptions and decisions ### 3. Complexity Reduction - Simplicity is the primary goal - Remove unnecessary code - Prefer the simplest viable solution ### 4. Evidence over Claims - Verify rather than declare success - Use tests to prove functionality - Use data to support decisions ## Skill Trigger Mechanism Superpowers is a mandatory workflow, not an optional suggestion. When any of the following is detected, the corresponding skill must activate: 1. **User mentions development/programming** -> Start Brainstorming 2. **Design complete** -> Start Implementation Planning 3. **Starting to write code** -> Start TDD 4. **Tasks need parallelism** -> Start Subagent-Driven Development 5. **Code complete** -> Start Code Review 6. **Project complete** -> Start Finishing ## Deliverables Each phase produces documentation to ensure traceability: | Phase | Output File | Purpose | |-------|------------|---------| | Brainstorming | `design.md` | Complete design document | | Planning | `plan.md` | Detailed implementation plan | | Development | `code/` | Source code | | Review | `review.md` | Code review report | | Finish | `final_report.md` | Project summary | ## Example Workflow **User Request**: "Build me a todo app" 1. **Brainstorming**: Ask about requirements (Web/Mobile? Auth needed? Data storage?) 2. **Design**: Generate UI design, architecture diagram, API design 3. **Planning**: Break down into: create project structure, implement auth, build CRUD, add frontend 4. **TDD**: Write tests for each feature first 5. **Subagent**: Dispatch subagents to develop different modules in parallel 6. **Review**: Review code quality of each module 7. **Finish**: Merge code, generate deployment docs ## Troubleshooting **Issue**: Subagent deviates from plan **Solution**: Stop immediately, analyze the deviation, adjust plan or re-dispatch **Issue**: Tests failing **Solution**: Return to Red phase, analyze failure cause, fix tests or code **Issue**: Requirements change **Solution**: Return to Brainstorming phase, re-evaluate design ## Reference Resources For detailed workflow guides and best practices, see `references/workflow.md` and `references/best_practices.md`. ## Resources This skill includes bundled resource directories for organizing different types of content: ### scripts/ Executable code (Python/Bash/etc.) that can be run directly to perform specific operations. **Examples from other skills:** - PDF skill: `fill_fillable_fields.py`, `extract_form_field_info.py` - utilities for PDF manipulation - DOCX skill: `document.py`, `utilities.py` - Python modules for document processing **Appropriate for:** Python scripts, shell scripts, or any executable code that performs automation, data processing, or specific operations. ### references/ Documentation and reference material intended to be loaded into context to inform the agent's process and thinking. **Examples from other skills:** - Product management: `communication.md`, `context_building.md` - detailed workflow guides - BigQuery: API reference documentation and query examples - Finance: Schema documentation, company policies **Appropriate for:** In-depth documentation, API references, database schemas, comprehensive guides, or any detailed information to reference while working. ### assets/ Files not intended to be loaded into context, but rather used within the output produced. **Examples from other skills:** - Brand styling: PowerPoint template files (.pptx), logo files - Frontend builder: HTML/React boilerplate project directories - Typography: Font files (.ttf, .woff2) **Appropriate for:** Templates, boilerplate code, document templates, images, icons, fonts, or any files meant to be copied or used in the final output. --- Any unneeded directories can be deleted. Not every skill requires all three types of resources.
【全棧能力】程式設計大神.Skill:面向複雜真實專案的高階全棧程式設計助手。不止生成程式碼,而是從一句目標接手陌生程式碼庫,拆解需求、補齊實現、追到根因、完成重構、聯調前後端,並把結果推進到能執行、能驗證、能交付。覆蓋 Web、後端、指令碼、iOS、安卓、鴻蒙 ArkUI、微信小程式及其他技術棧,支援中英文工程、疑難 Bug、跨模組任務和長任務續做;用構建、日誌、真實入口、裝置或介面證據說明結果。僅問概念時直接回答,要求落地時持續推進到驗收或明確阻塞。
程式設計專家 Pro:融合程式設計專家 2.0.3 工程專題與程式設計大神的鴻蒙 ArkTS/ArkUI、微信小程式和小遊戲開發資料。用於專案實現、根因除錯、審查、重構、測試、架構效能分析及多端開發驗證。支援自然語言和 @專題標識,按任務讀取包內知識;只問概念時直接回答。
程式設計專家.Skill P8級程式設計助手,25年實戰經驗技能Skill,全棧:Java/Php網站/軟體專案、API設計、Bug診斷、程式碼生成、程式碼審查、重構、測試用例、效能基準、技術選型、文件生成、任務拆解、Spec驅動、Karpathy規範、CMS二次開發、前端設計、MySQL/Mariadb、專案知識圖譜,以及工程紀律層(根因除錯硬閉環、階段導航、事故復盤/SLO、威脅建模/供應鏈安全、生產就緒/漸進式釋出、AI編碼治理、面向Agent程式碼可讀性、LLM應用安全)。支援 @標識 顯式呼叫跳過路由。
程式設計專家.Skill P8級程式設計助手,25年實戰經驗技能Skill,全棧:Java/Php網站/軟體專案、API設計、Bug診斷、程式碼生成、程式碼審查、重構、測試用例、效能基準、技術選型、文件生成、任務拆解、Spec驅動、Karpathy規範、CMS二次開發、前端設計、MySQL/Mariadb、專案知識圖譜,以及工程紀律層(根因除錯硬閉環、階段導航、事故復盤/SLO、威脅建模/供應鏈安全、生產就緒/漸進式釋出、AI編碼治理、面向Agent程式碼可讀性、LLM應用安全)。支援 @標識 顯式呼叫跳過路由。
程式設計專家 Pro:融合程式設計專家 2.0.3 工程專題與程式設計大神的鴻蒙 ArkTS/ArkUI、微信小程式和小遊戲開發資料。用於專案實現、根因除錯、審查、重構、測試、架構效能分析及多端開發驗證。支援自然語言和 @專題標識,按任務讀取包內知識;只問概念時直接回答。
程式設計專家 Pro:融合程式設計專家 2.0.3 工程專題與程式設計大神的鴻蒙 ArkTS/ArkUI、微信小程式和小遊戲開發資料。用於專案實現、根因除錯、審查、重構、測試、架構效能分析及多端開發驗證。支援自然語言和 @專題標識,按任務讀取包內知識;只問概念時直接回答。
程式設計專家.Skill P8級程式設計助手,25年實戰經驗技能Skill,全棧:Java/Php網站/軟體專案、API設計、Bug診斷、程式碼生成、程式碼審查、重構、測試用例、效能基準、技術選型、文件生成、任務拆解、Spec驅動、Karpathy規範、CMS二次開發、前端設計、MySQL/Mariadb、專案知識圖譜,以及工程紀律層(根因除錯硬閉環、階段導航、事故復盤/SLO、威脅建模/供應鏈安全、生產就緒/漸進式釋出、AI編碼治理、面向Agent程式碼可讀性、LLM應用安全)。支援 @標識 顯式呼叫跳過路由。
用 gh 命令列工具檢視 GitHub 上的 PR 檢查、工作流執行與 API 查詢的技能。
資料月份:2026-10 · 下載/星標數聚合自公開技能註冊庫(ClawHub、SkillHub),按月更新。口徑說明見資料方法。