claude-skills

Produces a Product Requirements Document for a feature by conducting a user interview (or using a completed grill-me session) and writing a structured PRD. Triggers on "create a PRD", "write a PRD", "document this feature", or when formalizing a feature before implementation.

Creates a pull request from a feature branch into main after verifying all quality gates — closed issues, PRD acceptance criteria, test coverage, and code quality. Triggers on "create the feature PR", "open a PR for the feature", "ship this feature", or any request to finalize a feature.

Conducts a structured interview to surface unstated requirements and design decisions before implementation. Uses iterative AskUserQuestion calls to identify gaps, edge cases, and constraints that would cause rework if missed. Triggers on "grill me", "let's think this through", "clarify requirements", or proactively when a task involves design decisions that would be expensive to reverse. Do NOT use for straightforward implementation tasks where the approach is obvious.

Conducts a structured interview grounded in the project's domain language (CONTEXT.md) and codebase. Like /grill-me, but it loads existing shared terminology before asking, refines it against the code as decisions surface, persists the refined glossary back to CONTEXT.md, and writes ADRs for non-obvious or hard-to-reverse decisions. Triggers on "grill with docs", "grill me with context", "let's think this through with the docs", or proactively when a task touches an existing codebase with domain modeling implications. Prefer this over /grill-me when a codebase exists.

Use this skill when the user asks to "review a PR", "review this pull request", "check the PR", "evaluate the PR", or wants to review and potentially merge an open pull request. Also use when the user wants to verify a PR meets all requirements before merging. Can be invoked with a PR number (e.g. `/pr-review 42`) or without to review the most recent open PR on the current branch.