Specs & PRDs

Turn the current conversation into a spec and publish it to your issue tracker

Turn vague product or engineering changes into scoped, testable acceptance criteria

Turn a PRD or roadmap ask into a plan with constraints, interfaces and open decisions

Interview the user one question at a time to uncover what they actually want

Write a spec with objectives, scope and requirements before any code is written

Ask a structured set of questions to clear up unresolved requirements

Draft a one-page product requirements doc with success metrics, scope and rollout

Gather requirements, define acceptance criteria and store the spec in memory

Chat with a product manager persona for PRDs and requirements discovery

Create, update or validate a product requirements document (PRD)

Test a product idea with a Working Backwards press release and tough FAQs

Create, update or validate a product brief for a product or feature

Write an epic product requirements document to feed architecture planning

Write a feature product requirements document under an existing epic

Find missing features, rank them and write implementation-ready specifications

Write product requirements documents with user stories, specs and risk analysis

Turn a pasted chat log or problem report into a structured intent document

Turn a feature idea or problem statement into a structured PRD

Write INVEST user stories and plan sprints with backlog and velocity tracking

Pressure-test a PRD or spec for silent gaps, edge cases and missing states

Extract feature lists and task checklists from product screenshots for PRDs

Reconstruct a product requirements doc from the routes and screens of any codebase

Write a lean, decision-ready product requirements document from a short template

Write job stories with motivations, outcomes and acceptance criteria

Write user stories with acceptance criteria that follow INVEST and the 3 Cs

Write product backlog items in Why-What-Acceptance format that stay testable

Turn vague or ambitious ideas into a right-sized requirements plan before building

Review requirements, plans and specs through role-specific reviewer lenses

Write a product requirements document for a new feature before coding starts

Turn feature ideas into specs, user stories, EARS requirements and acceptance criteria

Turn a feature idea into a PRD with problem, users, requirements and success metrics

Turn a ticket into requirements and journeys, and propose a split if it is too big

Turn a vague wish into a clear, checkable delivery goal with success criteria

Plan a phase as a vertical MVP slice built from user stories and SPIDR splits

Clarify what a phase delivers with ambiguity scoring and write a SPEC.md

Write product specs covering goals, scope, user stories, rollout and open questions

Draft a business requirements document from a product idea or customer problem

Write a market requirements document that sizes demand and rival products

Write a practical product requirements document from an idea or customer request

Turn raw requirements into structured specs through guided Socratic questioning

Run quality gates and interactive reviews on PRDs, specs and design docs before handover

Review a feature plan from strategy, design and engineering angles before building

Turn product intake into a spec with clear acceptance outcomes and explicit scope

Write a domain spec for a dashboard project with panels, data sources and interfaces

Define a personal daily monitoring dashboard with its panels, data sources and priorities

Turn a conversation into a milestone brief or PRD saved as a context file

Break epics into user stories with split patterns so each piece can be delivered

Frame an epic as a testable hypothesis with target user, outcome and validation method

Build an engineering-ready PRD that connects problem, users, solution and success criteria