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…
Drafts CHANGELOG entries from git log applying pm-skills CHANGELOG hygiene rules from CLAUDE.md: describe what changed (not where), public paths only, never reference gitignored NOTES/ or agent-context/SESSION-LOG/ or docs/internal/efforts/. Distinguishes user-facing from internal-only commits. Returns a draft for…
Runs an ordered sequence of pm-skills from a prioritized-action-plan or a user-named chain, pausing for go/no-go and stopping on a failed or empty step. Explicit invocation only; never fires proactively.
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker (beads — see issue-tracker.md).
Designs and executes efficient cross-project and long-term memory so agents build apps better. Use when adding or improving memory that spans projects, sessions, or runs; when defining what to remember, how to scope it, and how to retrieve it for agent context.
Evaluates app fidelity and completion against docs/SYSTEMARCHITECTURE.md and domain references. Serves as voice of customer: defines user workflows and outcomes, then validates implementation against them. Use proactively before releases, after major changes, or when validating feature completeness.
PROACTIVELY use this subagent whenever product planning calls for a dedicated pre-mortem deep run, typically after MVP scoping or solution prioritization and before committing to a plan, or when architecture context is available for risk-grounding. Also use whenever the user says "what could go wrong", "pre-mortem…
PROACTIVELY use this subagent immediately after the user writes or revises any strategy artifact: Strategy Blocks (mission/vision/strategy hierarchy), Rumelt's Good Strategy Kernel (diagnosis / guiding policy / coherent action), DHM Model (Delight/Hard-to-copy/Margin-enhancing), or Empowered Teams charter (Marty…
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.