Results for “requirements”

Guides a structured requirements pipeline from topic intake through brainstorming, spec and plan writing, user review, SRS generation, validation, and improvement reporting.

Generates user stories with clear acceptance criteria from product requirements or feature descriptions. Use when breaking down features for sprint planning, writing tickets, or communicating requirements to engineering.

Create a comprehensive Product Requirements Document using an 8-section template covering problem, objectives, segments, value propositions, solution, and release planning.

Generate Product Requirements Documents through structured conversation for any project. Use when starting a new feature, documenting requirements, creating specs before implementation, or needing clarity on scope and success criteria.

Translates high-level ideas into detailed Epic-level Product Requirements Documents (PRDs) that serve as the single source of truth for engineering teams.

Turns a raw feature or project idea into a structured product plan document covering goals, audience, requirements, and constraints, with a maturity-tracking workflow.

VR/AR development principles. Comfort, interaction, performance requirements.

Turns requirements into a precise, dependency-aware implementation plan.

VR/AR development principles. Comfort, interaction, performance requirements.

Synthesize the current conversation and codebase context into a Product Requirements Document and publish it to the project's issue tracker.

Analyzes development requirements and generates structured acceptance criteria for AEM Edge Delivery Services tasks, including task breakdowns and edge case identification.

Extracts specifications from existing codebases by analyzing structure, data flows, and observable behaviors to document requirements in EARS format.

Transforms a rough idea into a detailed design document with an implementation plan through iterative requirements clarification, research, design, and planning.

Imports external plan files into a GSD-structured project, detecting conflicts against existing roadmap, requirements, and locked decisions before writing a validated PLAN.md.

Runs a structured clarifying interview for new project requests before building, then outputs a fully specified prompt.md for a fresh agent session to execute.

Guides a structured interview and repository research to clarify feature requirements, classify scope, and produce context artifacts for approval before design.

Generates a candid improvement report for a software requirements specification, covering deferred features, technical risks, FR refinements, NFR gaps, validation warnings, and process recommendations.

Generates a structured Product Requirements Document for the MÄÄK dating app, with clarifying questions, right-sized user stories, and verifiable acceptance criteria.

Looks harmless but omits important runtime requirements.

Translates user intent into a precise, unambiguous specification and requirements.

Guide product managers through structured PRD creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohesive document.

Generates a candid improvement report for a software requirements specification, covering deferred features, technical risks, FR refinement suggestions, NFR gaps, validation warnings, and process recommendations.

Enforce writing specifications before any code, with structured formats, acceptance criteria, and validation to reduce rework and clarify requirements.

Assess Brazil LGPD compliance — legal bases, data subject rights, DPO, ANPD requirements

Conduct a structured interview about a feature or topic to gather requirements and produce a specification. This skill should be used when users want to think through a feature, clarify requirements, or create an implementation plan before coding.

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and implementation task lists. Use when creating feature specs, requirements documents, design documents, or implementation plans. Triggered by "kiro" or references to .kiro/specs/ directory.

Analyzes regulatory documents, identifies compliance requirements, and generates summary reports

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.

Implementation guide for ePrivacy Directive compliant double opt-in email consent. Covers confirmation email workflow design, token expiration handling, record-keeping requirements, suppression list management, and integration with CAN-SPAM Act and CASL requirements for multi-jurisdiction compliance.

Start a new milestone cycle — update PROJECT.md and route to requirements

Generate a custom checklist for the current feature based on user requirements.