pm

Document a bug fix with root cause analysis, fix plan, and test plan in a single tech-spec.

Handle mid-sprint requirement changes with a structured Sprint Change Proposal.

Define architecture, data model, UX, and API specification in sequential and parallel stages.

Conduct product discovery on top of a prior ideation package to produce project context, baseline, and vision.

Run a focused interrogation on existing documentation to find ambiguities, contradictions, missing boundaries, and hidden assumptions.

Document a new feature within an existing product with 3-5 focused artifacts.

Run the ETUS ideation and elicitation layer before Discovery, Feature, Bug, or Spike documentation.

Create implementation documentation and release readiness artifacts.

Run the complete ETUS workflow with ideation layer and 4 product phases.

Split planning into opportunity focus and delivery requirements with solution discovery in between.

Capture what the developer had to figure out on their own during implementation, classify gaps by phase, and feed learnings back into the framework.

Run explicit solution discovery after opportunity selection and before delivery requirements.

Document a research investigation, feasibility study, or brainstorm in a single spike document.

Initialize a new product documentation project and begin the orchestrator.

Run quality checks on documentation including gate validation, SST, and traceability.

Generates backend API specification: endpoints, schemas, authentication, error handling. Use when the user wants to define APIs, integration contracts, or endpoints.

Defines technical architecture, NFRs and design decisions (ADRs). Use when the user wants to define architecture, choose technologies, or non-functional requirements.

Generates 6 data design documents: data-requirements, ERD, database-spec, data-dictionary, data-flow-diagram, data-catalog. Use when the user wants to model data, define entities, or create database schemas.

Conducts discovery interview using story-based probes (5W2H dimensions) and brainstorming techniques (BMAD CIS) to generate project-context.md and product-vision.md. Use when the user mentions a new product, idea, or wants to start documentation from scratch. Reference: .claude/skills/discovery/knowledge/story-probes.md

Generates implementation documentation and release-readiness artifacts. Use when design is complete and the user wants to plan implementation.

Searches docs/ets/projects/{project-slug}/learnings/ for past retrospectives and lessons learned. Matches findings by tags, patterns, and domain relevance. Returns relevant learnings to the calling agent (typically discovery-agent or planning-agent).

Generates opportunity focus, solution discovery, PRD, User Stories and Feature Specs via interactive interview using HMW, prioritization, and risk reduction. Use when the user wants to define opportunities, solutions, requirements, features, or user stories.

Independent reviewer dispatched as a subagent after any generator skill saves an artifact. Reviews the saved document with fresh eyes — no access to the conversation that created it. Checks completeness, consistency, clarity, traceability, SST compliance, scope, and YAGNI. Only flags issues that would cause real problems for the next skill in the pipeline. Approves unless there are serious gaps.

Generates 4 UX design documents: user-journey, ux-sitemap, wireframes, style-guide. Use when the user wants to define flows, navigation, layouts or design tokens.

Use when defining API endpoints, documenting the API contract, or specifying request/response schemas. Also triggers on 'API spec', 'endpoint definitions', 'what is the API contract', 'REST API', 'GraphQL schema', or 'integration specifications'.

Use when documenting architecture changes for a specific feature, assessing impact, or identifying what needs to be modified. Also triggers on 'design delta', 'what changes', 'architecture changes for feature', 'what do we need to modify', or 'impact analysis'.

Use when defining system architecture, creating C4 diagrams, or deciding on technology choices. Also triggers on 'architecture diagram', 'how does the system fit together', 'infrastructure overview', 'system structure', or 'show me the containers and components'.

Use when defining technical specifications, non-functional requirements, or architecture decisions. Also triggers on 'tech spec', 'what are the NFRs', 'architecture decisions', 'performance requirements', 'scalability', 'security requirements', or 'ADR'.

Use when documenting a single feature without requiring the full product pipeline. Also triggers on 'feature brief', 'document feature', 'new feature', 'add feature', or when wanting to spec a standalone feature quickly.

Use when requirements change mid-sprint, scope needs adjusting, or a significant pivot is needed. Generates a Sprint Change Proposal that documents what changed, impact analysis, and updates all affected documents. Also triggers on 'change request', 'scope change', 'pivot', 'requirements changed', 'correct course', or 'mid-sprint change'.

Use when creating a data catalog, documenting data ownership, or tracking data lineage. Also triggers on 'data catalog', 'asset inventory', 'data governance', 'data lineage', 'retention policies', or 'who owns this data'.

Use when defining database schema, creating table definitions, or planning migrations. Also triggers on 'database spec', 'create the tables', 'DDL', 'migration strategy', 'index strategy', or 'database schema'.

Use when defining field semantics, event definitions, or domain terminology. Also triggers on 'data dictionary', 'what does this field mean', 'field definitions', 'event catalog', 'enumerated types', or 'domain glossary'.

Use when creating an ER diagram, mapping entity relationships, or visualizing the data model. Also triggers on 'ERD', 'entity relationship diagram', 'how do entities relate', 'cardinality mapping', or 'show the data model'.

Use when mapping data flows, understanding how data moves through the system, or documenting ETL processes. Also triggers on 'data flow diagram', 'how does data move', 'ETL flows', 'integration paths', or 'process-to-storage mapping'.

Use when starting data modeling, identifying entities, or defining what data the system needs. Also triggers on 'data requirements', 'what data do we need', 'data sources', 'entity inventory', or when the data-agent begins its workflow.

Use when surfacing assumptions, unknowns, and unanswered questions before planning or implementation. Also triggers on 'assumptions', 'unknowns', 'open questions', 'what are we assuming', or 'dependency interview'.

Use when establishing the current state of metrics, funnels, and data quality before a discovery or feature decision. Also triggers on 'baseline', 'current state', 'dados e contexto', 'funnel metrics', 'what are the numbers today', or 'AS-IS'.

Use when turning journeys and requests into explicit use cases. Also triggers on 'use case', 'use-case matrix', 'actor trigger action result', or 'main scenarios'.

Use when surfacing exceptions, abuse cases, and failure states before design or implementation. Also triggers on 'edge cases', 'failure cases', 'exceptions', 'abuse flow', 'what can go wrong', or 'pre-mortem'.

Use when extracting a raw idea into a coverage-driven discovery package before writing product docs. Also triggers on 'ideate', 'brainstorm a feature', 'explore the problem space', 'capture all use cases', 'JTBD', 'journeys', 'edge cases', or 'turn this idea into something implementation-ready'.

Use when mapping user journeys before requirements or solution design. Also triggers on 'journey', 'happy path', 'failure path', 'alternate flow', 'before during after', or 'anti-journey'.

Use when extracting Jobs To Be Done from interviews, ideas, notes, or product requests. Also triggers on 'JTBD', 'job to be done', 'switch interview', 'functional job', 'emotional job', or 'social job'.

Use when defining product vision, business objectives, target audience, or brainstorming product direction. Also triggers on 'what problem are we solving', 'who are our users', 'define the vision', 'product vision', 'business objectives', or 'value proposition'.

Use when starting a new project, gathering initial project context, or conducting a 5W2H interview. Also triggers on 'new project', 'project context', 'what are we building', 'tell me about the project', or when the discovery-agent begins its workflow. This is always the first document in any product documentation effort.

Use when consolidating discovery findings into an evidence-based report with methodology, key evidence, insights by theme, personas/JTBD, testable hypotheses, and remaining uncertainties. Also triggers on 'discovery report', 'research findings', 'what did we learn', 'evidence summary', 'discovery synthesis', or 'sumário de evidências'.

Use when conducting research, evaluating feasibility, or exploring options before committing to a direction. Also triggers on 'spike', 'research', 'investigate', 'feasibility', 'POC', 'proof of concept', 'brainstorm', 'explore options', or 'compare alternatives'.

Use when a feature has complex business logic, multiple state transitions, or intricate validation rules that need detailed specification. Also triggers on 'feature specification', 'this feature needs a detailed spec', 'complex feature', 'state machine', or 'business rules'.

Use when the user needs guidance, is unsure how to proceed, or wants to see project status. Also triggers on 'help', 'where am I', 'what is next', 'what can I do', 'show me the commands', or 'how does this work'.

Use when generating a consolidated developer handoff document. Triggers on 'handoff', 'dev packet', 'implementation packet', 'what does the dev need', 'developer handoff', 'consolidate for dev', or 'engineering brief'.

Use when creating an implementation plan, breaking down tasks, estimating effort, or planning sprints. Also triggers on 'how do we build this', 'task breakdown', 'development roadmap', 'sprint planning', or 'implementation plan'.

Use when preparing for release, checking quality readiness, or defining QA criteria. Also triggers on 'quality checklist', 'are we ready to ship', 'release criteria', 'QA requirements', or 'pre-launch validation'.

Use when planning a production release with rollout strategy, monitoring, rollback plan, and stakeholder communication. Also triggers on 'release plan', 'rollout plan', 'go-live', 'launch plan', 'how to deploy', 'rollback plan', or 'post-release monitoring'.

Legacy compatibility skill for projecting implementation work into an optional execution adapter state. Use only when an execution adapter is enabled and a local execution projection needs updating.

Use when documenting a bug fix, planning a hotfix, or performing root cause analysis before implementation. Also triggers on 'bug spec', 'fix plan', 'root cause analysis', 'hotfix spec', 'fix this bug', 'debug plan', or 'incident report'.

Use when running the full documentation pipeline, coordinating multiple phases, or managing the end-to-end workflow. Also triggers on 'orchestrate', 'full workflow', 'start documentation', 'run all phases', or 'coordinate the pipeline'.

Use when structuring discovery findings into an opportunity tree that connects outcomes to opportunities to candidate solutions. Also triggers on 'OST', 'opportunity solution tree', 'opportunity tree', 'where should we focus', 'which opportunities', or 'structure the discovery'.

Use when creating a PRD, defining features, prioritizing requirements, or scoping an MVP. Also triggers on 'product requirements', 'feature list', 'what should we build first', 'MoSCoW', 'prioritize features', or 'define the product scope'.

Use when prioritizing opportunities or features using ICE or RICE scoring with documented rationale and trade-offs. Also triggers on 'prioritize', 'ICE score', 'RICE score', 'what comes first', 'priorização', 'ranking', or 'P0/P1/P2'.

Use after implementation to capture what the developer had to figure out on their own. Triggers on 'retro', 'dev feedback', 'what did you have to guess', 'implementation gaps'.

Use when finishing a project, reflecting after a sprint, or capturing lessons learned. Also triggers on 'retro', 'retrospective', 'lessons learned', 'what did we learn', 'post-mortem', or 'what worked and what did not'.

Use when exploring candidate solutions after opportunities are selected and before writing delivery requirements. Also triggers on 'solution discovery', 'prototype', 'concept test', 'value risk', 'usability risk', 'viability risk', or 'feasibility risk'.

Use when writing user stories, defining acceptance criteria, or specifying user behaviors. Also triggers on 'user stories', 'as a user I want', 'acceptance criteria', 'Given/When/Then', 'BDD scenarios', or 'behavioral specifications'.

Use when mapping user journeys, analyzing touchpoints, or understanding the user experience end-to-end. Also triggers on 'user journey', 'journey map', 'user flows', 'what is the user experience', 'touchpoint analysis', or 'pain points'.

Use when creating a sitemap, defining navigation structure, or planning information architecture. Also triggers on 'sitemap', 'how are screens organized', 'page hierarchy', 'navigation map', or 'screen structure'.

Use when defining a style guide, design tokens, or visual design system. Also triggers on 'style guide', 'design tokens', 'what colors/fonts', 'brand guidelines', 'component library', 'typography', or 'color palette'.

Use when creating wireframes, planning screen layouts, or defining UI structure. Also triggers on 'wireframes', 'what does this page look like', 'screen layout', 'UI structure', 'component placement', or 'low-fidelity mockup'.

Use when stress-testing documentation for ambiguities, contradictions, and developer confusion. Triggers on 'elicit', 'stress-test', 'challenge the spec', 'find gaps', 'interrogate docs', 'what did we miss', or 'semantic review'.

Use when checking if a phase is ready to proceed, reviewing phase quality, or approving a gate. Also triggers on 'validate', 'are we ready', 'gate check', 'review phase', 'GO/NO-GO', or 'can we move to the next phase'.

Use for a 60-second quality check across all documents. Triggers on 'quick check', 'quality check', 'are the docs ready', 'sanity check', 'check rapido', 'check rápido', or 'are we ready'.

Use when checking document consistency, verifying SST compliance, or during gate validation. Also triggers when the orchestrator runs quality checks, or when asking 'are there duplicate definitions', 'check SST rules', or 'validate document ownership'.

Use when validating ID consistency, checking for orphan references, or during gate validation. Also triggers when asking 'are all IDs connected', 'check traceability', 'find broken links', or 'verify the requirements chain'.