obra
Imported from public sources. Its owner can claim it by signing in.
15 items
- obra 297kusing-superpowersUse when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questionsSkillNo code
- obra 297kDiagnosing 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.SkillNo code
- obra 297kVerification 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 alwaysSkillNo code
- obra 297kWriting PlansUse when you have a spec or requirements for a multi-step task, before touching codeSkillNo codeWriting
- obra 297kBrainstorming Ideas Into DesignsYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.SkillNode.js
- obra 297kUsing 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 fallbackSkillNo codeGit and GitHub
- obra 297kWriting SkillsUse when creating new skills, editing existing skills, or verifying skills work before deploymentSkillNode.jsDevOpsWriting
- obra 297kFinishing a Development BranchUse when implementation is complete, all tests pass, and you need to decide how to integrate the workSkillNo code
- obra 297kSystematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesSkillNode.jsCoding
- obra 297kTest-Driven Development (TDD)Use when implementing any feature or bugfix, before writing implementation codeSkillNo codeWriting
- obra 297kExecuting 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 availableSkillNo codeAgents
- obra 297kDispatching Parallel AgentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillNo code
- obra 297kRequesting Code ReviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsSkillNo codeCoding
- obra 297kCode Review ReceptionUse 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 implementationSkillNo codeCoding
- obra 297kSubagent-Driven DevelopmentUse when executing implementation plans with independent tasks in the current sessionSkillNo codeAgents