---
name: lightspeed-approval-gate-manager
description: manage approval checkpoints for lightspeed figma design system to wordpress block theme, block plugin, woocommerce, publishing, tourism and hybrid-theme projects. use when the user needs approval gates, sign-off checklists, decision logs, go/no-go criteria, stakeholder review packs, change-control notes, scope approval, prd approval, technical brief approval, github issue approval, implementation approval or launch approval before work moves to the next delivery stage.
---

# LightSpeed Approval Gate Manager

## Purpose

Create and manage approval gates between project planning, implementation, QA and launch for LightSpeed Figma-design-system-to-WordPress projects.

Use this skill when a project needs controlled sign-off before moving from one stage to the next.

## Core principle

Do not assume a project is approved because a document exists. Every major transition should have explicit approval status, owner, date, open decisions and known risks.

## Supported gates

- Intake approval
- Research approval
- PRD approval
- Figma-to-WordPress technical brief approval
- Task breakdown approval
- GitHub issue draft approval
- Estimate/proposal approval
- Implementation plan approval
- Figma parity approval
- Content/claims/policy approval
- QA readiness approval
- Launch go/no-go approval
- Post-launch review approval

## Inputs to accept

Accept any combination of:

- project brief
- research report
- PRD
- technical brief
- task breakdown
- GitHub issue drafts
- implementation plan
- launch QA plan
- claim register
- redirect map
- schema plan
- GA4 plan
- Figma parity report
- stakeholder feedback
- open questions
- decision log

## Workflow

1. Identify the project stage and requested approval gate.
2. Review source documents and classify evidence as approved, pending, missing or blocked.
3. Create an approval checklist for the current gate.
4. List open decisions, blockers, risks and assumptions.
5. Define what is approved, what is excluded and what requires follow-up.
6. Recommend one of:
   - Approved
   - Approved with conditions
   - Needs revision
   - Blocked
   - Not ready for review
7. Produce client-facing summary and internal LightSpeed notes.
8. Recommend the next workflow or specialist skill.

## Output requirements

Always include:

- Gate name
- Project stage
- Approval recommendation
- Approval checklist
- Required approvers
- Source documents reviewed
- Approved scope
- Exclusions and non-goals
- Open decisions
- Blockers
- Risks and assumptions
- Required changes
- Next workflow
- Client-facing summary
- Internal LightSpeed notes

## Reference loading

Use these references when relevant:

- `references/approval-gate-workflow.md` for the end-to-end gate process.
- `references/gate-types.md` to choose the correct gate.
- `references/status-model.md` for approval status language.
- `references/decision-log-rules.md` for decision and risk capture.
- `references/stakeholder-review-rules.md` for client/internal review packs.
- `references/wordpress-project-gates.md` for WordPress-specific gates.

## Quality standard

Be practical and direct. Separate client-safe wording from internal delivery notes. Never mark legal, privacy, accessibility, launch, claim or implementation work as approved when evidence is missing.

*Have questions? Ping us on GitHub! 🐙 Made with 💚 by LightSpeedWP*