Obra技能

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.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

当您有书面的实施计划需要在单独的会话中执行并包含审查检查点时使用

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

在接收代码审查反馈时使用，尤其是在实施建议之前，如果反馈看起来不清晰或技术上存疑——需要技术严谨性和验证，而非表面上的同意或盲目实施

在完成任务、实现主要功能或合并前使用，以验证工作是否符合要求

在当前会话中执行包含独立任务的实施计划时使用

在遇到任何错误、测试失败或意外行为时使用，在提出修复方案之前

在编写实现代码之前，用于实现任何功能或修复错误时使用

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

在任何对话开始时使用——建立如何查找和使用技能的方法，要求在做出任何回应（包括澄清性问题）之前必须先调用技能工具。

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

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