Use when the user wants a product one-pager, brief, or short feature spec — drafting one from raw material (idea notes, a feature request, meeting/Slack notes, research snippets), or reviewing and strengthening an existing one (Markdown file or pasted text). Not for long-form PRDs, technical specs (architecture/API/RFC), or non-product docs.
Use when the operator wants to confirm a backend change is adequately tested before it ships — triggers include "QA this branch", "QA this PR", "is this tested enough", "do we have enough tests", "verify test coverage", "confirm the tests pass", "/backend-qa", or any request to audit/gate the unit + integration coverage of a backend change. Verifies an existing test suite; to author missing tests, use [backend-testing](../backend-testing/SKILL.md).
Use when writing, reviewing, or improving tests in a backend / API / service project — triggers include "write tests", "add tests", "test this endpoint", "test this service", "improve test coverage", "/backend-testing", or any request to create or fix backend tests. Also triggered when TDD is active in a backend codebase to provide the testing context and patterns. Covers HTTP APIs, services, workers, and data layers across languages (Python, Node, JVM, Go, Ruby).
This skill should be used when the user says "create a PR", "open a pull request", "make a PR", "push and create PR", "open PR for this", "submit a PR", "PR this branch", "let's get this reviewed", or wants to update an existing PR's description or reviewers. Handles the full PR lifecycle: pre-checks, branch pushing, structured descriptions, reviewer assignment, and task linking. Works standalone or as a step in the ship-it orchestrator.
Creates a Product Requirements Document from one or more content sources. Sources can be passed as arguments — task URL, Jira URL, Notion URL, Google Drive URL, Figma URL, Loom URL, any web URL, a local file or folder path, free-text problem statement, or left empty to read the current folder. Use this skill whenever the user wants to draft, write, or generate a PRD — "/create-prd", "write a PRD", "draft a PRD for X", "create a product requirements doc", "spec this out", "turn this one-pager into a PRD", or pastes a source URL (task manager / Notion / Figma / Drive / Loom / any web link) and asks for a PRD. Also triggers when the user describes a feature in free text and asks for a structured spec.
Use when the operator wants a design or mockup challenged against requirements — triggers include "challenge this design", "review these designs", "do the designs cover all the use cases / states", "verify the mockups match the spec", "audit the screens", "/design-review". Inputs are tool-agnostic: requirements can be PRDs, specs, tickets, Notion/Confluence pages, or pasted text; designs can be in Figma, an HTML page, exported images, or Photoshop. Produces a state-coverage gap report.
Handles bug-fix investigation and testing when start-task routes a Bug category task. Orchestrates root cause investigation (DIAGNOSE_AND_FIX_BUG capability) and a TDD hard gate to prevent recurrence (APPLY_TDD capability), resolved via the runtime-bindings table. Returns to start-task for QA verification and shipping. Always called from start-task; never invoked directly.
Use when writing, reviewing, or improving tests in a frontend project — triggers include "write tests", "add tests", "test this component", "improve test coverage", "/frontend-testing", or any request to create or fix frontend tests. Also triggered when TDD is active in a frontend codebase to provide the testing context and patterns.