---
name: lightspeed-prd-generator
description: create product requirements documents for lightspeed figma design system to wordpress block theme, block plugin, woocommerce, publishing, tourism and hybrid-theme projects. use when the user needs a prd, product brief, goals, non-goals, personas, user stories, acceptance criteria, success metrics, risks, assumptions, open questions, client-facing summary or internal lightspeed implementation notes before technical planning, task breakdown or github issue drafting.
---

# LightSpeed PRD Generator

## Purpose

Create clear, delivery-ready PRDs for LightSpeed WordPress projects, especially projects where a Figma design system must become a WordPress block theme, block plugin, WooCommerce implementation, publishing platform, tourism site or hybrid-theme project.

Use this skill before technical brief creation, task breakdown, GitHub issue drafting, project memory creation or launch QA planning.

## Core principles

- Keep PRDs practical, implementation-aware and suitable for client review.
- Separate client-facing decisions from internal LightSpeed notes.
- Do not invent scope, claims, budgets, estimates, technical constraints or success metrics.
- Flag assumptions, risks and open questions clearly.
- Preserve human approval gates before implementation, issue creation or scope finalisation.
- Prefer WordPress-native, block-first, maintainable approaches.

## Inputs to accept

Accept any combination of:

- client brief
- discovery notes
- Figma design system URL
- Figma page/frame URL
- Figma variables export
- Figma Make prototype
- screenshots
- existing WordPress site URL
- staging/dev URL
- GitHub repo links
- GitHub issue notes
- content collection outputs
- AI readiness or governance outputs
- launch QA notes
- manual business context

If evidence is missing, create a draft PRD with an assumptions and open-questions section rather than pretending the details are confirmed.

## Supported project types

Support:

- WordPress block theme builds
- block theme plus custom block plugin builds
- classic or hybrid theme conversions
- WooCommerce block theme projects
- publishing and editorial platforms
- tourism and tour-operator projects
- AI-readiness and governance website projects
- design-system-to-WordPress implementations

## Workflow

1. Identify the requested PRD scope:
   - PRD only
   - PRD plus discovery summary
   - PRD plus acceptance criteria
   - PRD seed for technical brief and task planning
   - full project pack seed
2. Confirm or infer the project type.
3. Capture available evidence and missing evidence.
4. Define goals, non-goals, users and business outcomes.
5. Define functional and non-functional requirements.
6. Include WordPress, Figma, accessibility, performance and governance considerations.
7. Write user stories and acceptance criteria.
8. Add risks, assumptions, dependencies and open questions.
9. Add success metrics and launch/readiness gates.
10. Output Markdown suitable for Google Docs, GitHub or a project pack.

## Required output sections

Every PRD should include:

- Value, risk and next step
- Executive summary
- Project context
- Goals
- Non-goals
- Target users and personas
- User journeys
- Functional requirements
- Non-functional requirements
- WordPress and technical considerations
- Figma/design-system considerations
- Content and governance considerations
- Accessibility, performance and SEO considerations
- User stories
- Acceptance criteria
- Success metrics
- Dependencies
- Risks and assumptions
- Open questions
- Approval gates
- Client-facing summary
- Internal LightSpeed notes

For smaller requests, use the same structure but keep sections concise.

## Reference loading

Use these references as needed:

- `references/prd-workflow.md` for the PRD creation sequence.
- `references/project-types.md` for WordPress project variants.
- `references/wordpress-prd-rules.md` for LightSpeed WordPress defaults.
- `references/figma-design-system-rules.md` for Figma-to-WordPress PRD coverage.
- `references/acceptance-criteria-rules.md` for acceptance criteria formats.
- `references/success-metrics.md` for measurable outcome options.
- `references/approval-gates.md` for human review checkpoints.

## Quality bar

A good PRD should be specific enough that another skill can create a technical brief and task breakdown from it without re-discovering the whole project.

---

*Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit!*