Implement a feature phase by phase following a PLAN.md, with human approval gates between phases. Handles the full cycle from branch creation through implementation, verification, and PR creation. Use this skill when the user wants to implement, build, or code a planned feature — including phrases like "implement this", "start coding", "build the feature", "execute the plan", "start phase 1", "continue implementation", "create the PR", or when the user has a PLAN.md and wants to begin or continue development. Also trigger when the user asks to resume implementation from a specific phase.
Run a comprehensive pre-PR quality gate before creating a pull request. Verifies build, tests, lint, PLAN.md coverage, and common mistakes — then reports go/no-go with specific issues to fix. Use this skill when the user is about to create a PR, has finished implementing a feature, wants to verify everything is ready before pushing, or mentions phrases like "pre-PR check", "ready to PR", "create PR", "push and create PR", "is this ready", "run checks", "quality gate", or "final check". Also trigger when the developer skill reaches the PR creation step.
Run a structured product owner / business analyst session for a new feature. Takes raw feature requirements, interviews the human to uncover gaps and edge cases, and produces a SPEC.md with user stories, acceptance criteria, and out-of-scope items. Use this skill whenever the user wants to define, scope, or spec out a new feature — including phrases like "new feature", "requirements", "write a spec", "BA session", "product owner", "user stories", "acceptance criteria", or "let's scope this out". Also trigger when the user pastes or references raw feature requirements and wants them refined into a structured specification.
Run a post-merge retrospective for a completed feature. Reads the PR review comments, analyzes what Claude got right and wrong during implementation, and produces a RETRO.md with lessons learned and actionable improvements for CLAUDE.md. Use this skill after merging a feature PR, or when the user mentions "retrospective", "retro", "lessons learned", "what went wrong", "post-mortem", "what should we improve", "update CLAUDE.md from review", or "what did the reviewer find". Also trigger when the user wants to analyze review findings across multiple features to spot patterns.
Create a detailed technical implementation plan (PLAN.md) for a feature that has a completed SPEC.md. Analyzes the existing codebase, proposes changes organized into self-contained buildable phases, and produces a plan that another developer or AI agent can execute without additional context. Use this skill when the user wants to plan, architect, or design the implementation of a feature — including phrases like "create a plan", "architecture", "technical design", "implementation plan", "how should we build this", "plan this feature", or when the user has a SPEC.md and wants to move to the implementation planning stage. Also trigger when the user asks to break a feature into phases or create a PLAN.md.