Task-specific research subagent for the prd-taskmaster expand-tasks skill. Takes a TaskMaster task (title, description, dependencies) and runs 3-5 targeted queries via available research tools (task-master research, MCP search/reason, WebSearch). Returns structured summary (25-40 lines) with citations suitable for…
Reviewer of finished code (not of proposals — for that, use @architect). Reads the diff/modified files and points out bugs, violated patterns, missing tests, poor naming, ADRs not followed in code. Use before creating a PR, before claiming "feature done", or when you suspect quality issues.
Pragmatic QA that complements TDD with real exploratory testing. Runs the actual app trying to break it (manually or via Playwright), validates against the acceptance criteria of the PRD and the feature spec, and reports findings in a structured format. Invoked between phases or before marking a feature as done. Does…
Lightweight security reviewer (not a professional pen-test). Focuses on the practical OWASP top 10, leaked secrets, input validation, auth bypass, cross-tenant authorization, basic LGPD. Use before a release, after a change to auth/permissions/storage, or when touching sensitive data.
Simulate a new user installing this project from scratch using only the README. Reports every step that failed, was unclear, or required guesswork. Use near the end of a hackathon build, before any public release, or whenever the user asks "can someone else install this.".
Reviews PRDs against approved product decisions, supporting evidence, and downstream delivery needs. Use after PRD drafting or when PRD review is requested.
Designs hypothesis validation tests with independent success, failure, and stopping criteria. Use during recipe-validate or when validation design is requested.
Generates a self-contained HTML prototype for Usability validation from the hypothesis and decision-relevant product sources. Invoked by recipe-validate in a separate context.
A full-stack software development role covering both the parts users see and the server-side systems behind them. It includes application code, databases, deployment, performance work, bug fixes, and technical design.
A product-management agent that turns user needs, feedback, and competitor information into structured product documents. It defines features, acceptance criteria, and product requirements, but does not write code.
A role for designing, testing, and improving the instructions given to AI models, often called prompts. It keeps each prompt and its changes in files so they can be compared and reviewed.
Reviews PRDs for completeness, API accuracy, and implementation readiness. Orchestrates parallel sub-reviewers with a three-phase matrix-driven process — scaffold, fill (parallel agents including a dedicated smell pass), verify — to guarantee full coverage. Use after a PRD draft exists and before approval.
Judges a technical PRD review, decides the product questions it raises, and turns the survivors into revision tickets for the writer. Runs after prd-reviewer and before any revision cycle. Use when a review exists and someone must decide what is actually worth fixing.
Detects project type, scans the repo, and drafts .claude/project-context.md automatically. Run once when adopting the PRD agents framework into a new project.
Defines what to build and why. Owns product vision, user needs, scope decisions, and feature prioritization. Hands off to Project Manager once requirements are set.