You MUST use this before any creative work - creating features, building components, adding functionality, or...
find ~/obra/ -name "*.skill"
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides...
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or...
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when executing implementation plans with independent tasks in the current session
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when starting feature work that needs isolation from current workspace or before executing implementation plans...
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before...
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running...
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
Use when auditing a codebase for semantic duplication - functions that do the same thing but have different names or...
Use MCP servers on-demand via the mcp CLI tool - discover tools, resources, and prompts without polluting context...
Use when you need to run interactive CLI tools (vim, git rebase -i, Python REPL, etc.) that require real-time...