skills.rest
daudaudinang
daudaudinangCOMMUNITY
Explore all skills by this author →
GitHub

lp-spec

Clarify business requirements and UX flows into a canonical spec.md artifact.

Updated Apr 14, 2026
Search Tags:#workflow#planning#specification#requirements#review#ux#acceptance-criteria
One-click install
npx skills add https://github.com/daudaudinang/vibecode --skill lp-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lp-spec
Source: https://github.com/daudaudinang/vibecode/tree/main/.agents/skills/lp-spec
Command: npx skills add https://github.com/daudaudinang/vibecode --skill lp-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonically defines and records business requirements, UX flows, and edge cases to remove ambiguity before planning.

Core Features & Use Cases

  • Provides a single source of truth for requirements and user flows.
  • Supports edge cases and acceptance criteria.
  • Produces spec artifacts and facilitates a review gate before planning.

Quick Start

Describe your product goal, user flow, and acceptance criteria to generate the canonical spec.

Frequently Asked Questions about lp-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify business requirements before starting project planning?▼

To clarify business requirements before project planning, you generate a canonical specification that defines user flows and edge cases. This removes ambiguity by establishing a single source of truth for review gates.

What is the best way to document edge cases and acceptance criteria for UX workflows?▼

Documenting edge cases and acceptance criteria for UX workflows is best handled by producing a formal spec artifact. This ensures all user flows and boundary conditions are reviewed before development begins.

How do I create a canonical specification for a product goal?▼

You create a canonical specification by providing your product goal, user flow, and acceptance criteria. This guides teams through formal spec generation, capturing happy paths and edge cases into a spec.md artifact.

Does this specification workflow enforce a review gate before development?▼

Yes, this specification workflow enforces a review gate before planning. It ensures teams validate the canonical spec, integration points, and acceptance criteria before transitioning into the development phase.

Why should I use a formal specification to remove ambiguity in requirements?▼

Using a formal specification removes ambiguity in requirements by canonically defining business needs and UX flows. It provides a single source of truth, ensuring edge cases and integration points are documented before planning.

Related Skills

Explore More Product & Management Skills→
viethahongviethahong

prd-writing

Generate PRDs with goals, user flows, requirements, acceptance criteria, and edge cases.

Community
Advanced
hachejhachej
45

plan

Route tracked TODOs through reviewed plans and dependency-aware graphs.

Community
Advanced
sidjamylsidjamyl

product-designer

Guide UI/UX design, design systems, prototyping, and usability testing.

Community
Advanced
ianphilianphil

quick-plan

Generate concise backlog planning documents from user input.

Community
Basic