Write Product Spec / Acceptance Criteria
Independent PiSkill directory guide. The original skill remains hosted by Anthropic Knowledge Work Plugins.
What is Write Product Spec / Acceptance Criteria?
Turns a vague product idea into a structured PRD or feature specification with goals, non-goals, user stories, prioritized requirements, measurable success metrics, and testable acceptance criteria.
What does Write Product Spec / Acceptance Criteria do?
Write Product Spec / Acceptance Criteria is an Anthropic product-management skill for turning a feature idea, problem statement or user request into a structured feature specification or PRD. It is particularly useful when the initial request is too vague to hand directly to design or engineering.
Who is Write Product Spec / Acceptance Criteria best for?
- Product managers and founders
- Engineering leads clarifying requirements before implementation
- Teams translating customer requests into scoped work
- Projects that need explicit success metrics and acceptance criteria
Common use cases
- Turn a vague feature idea into a PRD
- Define goals, non-goals, constraints and target users
- Create measurable acceptance criteria
- Identify dependencies and prior related work before implementation
How does Write Product Spec / Acceptance Criteria work?
The skill first clarifies the user problem, target users, success measures, constraints and prior work. When connected tools are available it can pull related tickets, research and design context. It then structures the result into a feature specification with clear scope and testable criteria.
Key benefits
- Reduces ambiguity before engineering starts
- Connects requirements to measurable success
- Encourages explicit constraints and non-goals
- Creates a common artifact for product, design and engineering
Things to know
- A generated PRD still requires stakeholder agreement
- Acceptance criteria are only as good as the product decisions behind them
- Technical feasibility and estimates should be validated by the relevant engineering team
Compatible tools
Frequently asked questions
Can AI write acceptance criteria?
What information does the skill need?
Related skills
Product Roadmap Update
Creates or reprioritizes a product roadmap when initiatives, dependencies, timelines, or new information change, including Now/Next/Later planning and trade-off decisions.
Process Documentation / SOP Builder
Turns a messy business process into a structured SOP with purpose, scope, RACI ownership, process flow, detailed steps, exceptions, metrics, and related documentation.
Process Optimization
Analyzes an inefficient workflow, maps its current state, identifies waiting, rework, handoff and manual-work bottlenecks, then proposes a streamlined future-state process and implementation plan.
Brainstorming
Turns an initial product or feature idea into a clearer design by exploring intent, requirements, alternatives, constraints, and trade-offs before implementation begins.
Writing Implementation Plans
Turns an approved software design into an execution-ready implementation plan with small tasks, dependencies, test cycles, file-level changes, and verification steps.
AWS Billing and Cost Management
Analyzes AWS spending, identifies savings opportunities, manages budgets, evaluates commitment discounts, checks pricing, investigates anomalies, and supports cost-optimization workflows.