Results for “requirements”

Takes a high-level feature from an Epic and generates a detailed Product Requirements Document (PRD) in Markdown, covering goals, user stories, requirements, and acceptance criteria.

Analyzes requirements and produces four artifact files: requirements.md, user-stories.md, acceptance-criteria.md, and business-rules.md, with optional loading from SRS workflow artifacts.

Guides collaborative dialogue to turn ideas into designs and specs, exploring intent and requirements before any implementation.

This skill should be used when the user asks to "create PRD", "write product requirements document", or mentions "PRD", "product requirements document".

Guides collaborative dialogue to turn ideas into fully formed designs and specs, exploring intent, requirements, and design before implementation.

Generates an IEEE 830 software requirements specification from raw client input through structured clarification rounds and a review gate.

Generates an IEEE 830 Software Requirements Specification from raw client input through structured brainstorming, gap analysis, and clarification rounds.

Creates structured specifications before writing code to clarify requirements, surface assumptions, and define success criteria, reducing rework and miscommunication.

Clarifies ambiguous or conflicting requests by researching first, then asking only judgment calls. Use when prompts say "grill me", ask hard questions, request relentless interrogation, pressure-test assumptions, clarify scope/requirements, define success criteria, or request system-design/optimization decisions.

Creates and manages Product Requirements Documents (PRDs) with structured user stories, acceptance criteria, and progress tracking for feature planning.

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

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

Guides a structured software requirements specification workflow from topic intake through brainstorming, spec writing, planning, review, SRS generation, validation, and improvement reporting.

Generates an IEEE 830 software requirements specification from raw client input, guiding users through structured clarification rounds and producing a compliant document.

Enter explore mode to think through ideas, investigate problems, and clarify requirements before implementation, with optional OpenSpec artifact creation.

Defines when to create Epic, Feature, UserStory, or Task tickets and adds concise guidance to SKILL.md.

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

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.

Structures product requirements into a single-page spec with problem, success metrics, scope, user stories, design notes, and rollout plan.

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

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.

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

Guides setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.

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

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

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.

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.

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