搜尋
搜尋結果
80 results for "superpowers"

diagnosing-superpowers
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.
obra
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
obra
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
obra
receiving-code-review
Use 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 implementation
obra
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
obra
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
obra
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
obra
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
obra
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
obra
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
obra
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
obra
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
obra
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
obra
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
obra
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
obra
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
sickn33
superpowers-lab
Lab environment for Claude superpowers
sickn33
mcp-builder
在构建 MCP 服务器或 MCP 工具时使用 —— 系统化的生产级 MCP 构建方法论,覆盖工具设计、错误处理、传输层选择与测试,让 AI 助手连接外部能力
jnmetacode
writing-skills
当创建新技能、编辑现有技能或在部署前验证技能是否有效时使用
jnmetacode
workflow-runner
在 Claude Code / OpenClaw / Cursor 中直接运行 agency-orchestrator YAML 工作流——无需 API key,使用当前会话的 LLM 作为执行引擎。当用户提供 .yaml 工作流文件或要求多角色协作完成任务时触发。
jnmetacode
dispatching-parallel-agents
当面对 2 个以上可以独立进行、无共享状态或顺序依赖的任务时使用
jnmetacode
finishing-a-development-branch
当实现完成、所有测试通过、需要决定如何集成这份工作时使用
jnmetacode
using-git-worktrees
当需要开始与当前工作区隔离的功能开发,或在执行实现计划之前使用——通过原生工具或 git worktree 回退机制确保隔离工作区存在
jnmetacode
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用,不要根据上下文自动触发。
jnmetacode