Results for “requirements”

Create, validate, or edit product requirements documents. Tri-modal. Phase 2 Planning

Creates an approval-gated product requirements document or decomposes an approved PRD into a traceable roadmap, covering product-level problems, new initiatives, multi-feature scope, PRDs, release outcomes, and roadmap planning.

Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

Comprehensive process for discovering and validating data model requirements before design

Guides the agent to act as a product manager, collecting context, proposing three requirement plans (bug fix, new feature, iteration), scoring them by ROI, and recommending one with an MVP slice and timeline.

Write a Product Requirements Document structured with problem statement, goals, user stories, scope, and success metrics.

Turn an approved PRD or implementation goal into SRS/FRS technical requirements (How), architecture, contracts, and verification decisions.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Esboça a abordagem técnica como delta sobre o legado, gerando roadmap, investigation, data-delta, onboarding e interfaces da feature ativa. Use quando o usuário digitar "/reversa-plan", "reversa-plan", "esboçar plano técnico" ou pedir para virar requirements em desenho de solução. Terceiro skill do ciclo forward, depois de `/reversa-requirements` e (opcionalmente) `/reversa-clarify`.

Run a structured discovery interview and produce a complete, developer-ready Product Requirements Document. Load when the user asks to write a PRD, create product requirements, document a feature, define user stories with acceptance criteria, or turn a rough idea into a formal product requirements document. Also triggers on "document this feature", "write requirements for", "create a one-pager", "turn this into a PRD", "I need a PRD for", or any request to produce a structured product document for stakeholder alignment or engineering handoff. Supports Full PRD, Lean PRD, and One-Pager formats. Note: for executable feature specifications (FRs, NFRs, ACs as Given/When/Then consumable by AI coding agents), route to `feature-spec` instead — PRDs frame the product, feature-specs encode the implementable contract.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Guides collaborative dialogue to turn ideas into fully formed designs and specs before any implementation begins.

Guides CAPA effectiveness assessment with verification methods, SMART criteria, and closure requirements.

Guides a structured brainstorming session that surfaces user ideas, narrows options, and produces a spec file for later planning.

Guides a structured brainstorm that surfaces user ideas, explores directions, and produces a spec and report for later planning.

Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.

Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.

Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.

Guides users through a structured interview to clarify their AI agent idea and produces an Agent Requirement Document (ARD).

Designs system architecture and translates requirements into actionable plans, creating PRDs and tasks via Task Copilot.

Reverse-engineer any codebase into a complete Product Requirements Document (PRD). Analyzes routes, components, state management, API integrations, and user interactions to produce business-readable documentation detailed enough for engineers or AI agents to fully reconstruct every page and endpoint. Works with frontend frameworks (React, Vue, Angular, Svelte, Next.js, Nuxt), backend frameworks (NestJS, Django, Express, FastAPI), and fullstack applications. Trigger when users mention: generate PRD, reverse-engineer requirements, code to documentation, extract product specs from code, document page logic, analyze page fields and interactions, create a functional inventory, write requirements from an existing codebase, document API endpoints, or analyze backend routes.

Roadmap parsing, analysis, and mutation operations for ROADMAP.md. Handles phase and milestone lifecycle including add, insert (decimal), remove, complete, and requirements coverage analysis.

Update an existing implementation plan file with new or updated requirements for features, refactoring, package upgrades, design, architecture, or infrastructure.

Interviews the user in depth about a plan, probing technical implementation, UI/UX, risks, tradeoffs, and missing decisions before writing or refining a spec.

Guides a structured interview and codebase exploration to produce a PRD, then submits it as a GitHub issue.

Choose the right Project + Product skill for a request and sequence multiple skills when the work spans discovery, requirements, delivery, launch, PRINCE2 governance, or team rituals.

Formaliza una idea como propuesta de cambio antes de invertir tiempo en especificaciones y diseño, alineando contexto, alternativas, impacto y criterios de éxito.

Designs an approval-gated feature specification from approved requirements, covering architecture decisions, component boundaries, quality constraints, and definition of done.

Breaks a product requirements document into independently-grabbable GitHub issues using vertical slices, with user approval before creation.

Turns product ideas into structured specs for AI tools or stakeholder review, with quick feature specs and full project scopes.

Trigger: PM, product tasks, project planning, backlog priority, user stories, ticket scoping. Scope: Product management, task priorities, requirements scoping. Boundary: Excludes writing raw code or designing page layouts.

Synthesizes the current conversation and codebase context into a structured PRD and publishes it to the project issue tracker with a triage label.

Turns the current conversation context and codebase understanding into a PRD and publishes it to the project issue tracker with a triage label.