@obra

getting-started-with-skills documents mandatory workflows for skill discovery and usage within the implexa environment, emphasizing read-before-use discipline, todowrite integration for checklists, and explicit announcement patterns to maintain process transparency.

subagent-driven-development provides a pattern for executing multi-task implementation plans by spawning isolated agents per task with two-stage (spec then code quality) review gates, avoiding context bleed and maintaining coordinator focus.

You MUST invoke this skill before saying "I don't know," guessing, or treating any topic as new, no matter how trivial the question seems. It supplements other…

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via…

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…

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

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output…

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when implementing any feature or bugfix, before writing implementation code

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when you have a spec or requirements for a multi-step task, before touching code

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…

Use when executing implementation plans with independent tasks in the current session

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

Use when you have a spec or requirements for a multi-step task, before touching code

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 starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Use when you need direct browser control - teaches Chrome DevTools Protocol for controlling existing browser sessions, multi-tab management, form automation,…

using-tmux-for-interactive-commands — an installable skill for AI agents, published by obra/superpowers-lab.

Use when auditing a codebase for semantic duplication - functions that do the same thing but have different names or implementations. Especially useful for…

Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes…

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when creating new skills, editing existing skills, or verifying skills work before deployment