create-spec

Generate a testable LP spec package with business context and acceptance criteria.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/daudaudinang/vibecode --skill create-spec-daudaudinang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-spec
Source: https://github.com/daudaudinang/vibecode/tree/main/.agents/skills/create-spec
Command: npx skills add https://github.com/daudaudinang/vibecode --skill create-spec-daudaudinang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill generates a complete, testable LP spec package from a user requirement, providing a baseline for planning and validation.

Core Features & Use Cases

  • Canonical spec generation: produces business context, UX flows, rules, and acceptance criteria in a structured spec.
  • Artifact production: emits machine-readable outputs and human-readable documentation to guide orchestration.
  • Handoff-ready outputs: creates .codex/plans/PLAN_<NAME>/spec.md and related pipeline contracts to drive subsequent steps.

Quick Start

Provide the requirement and run the create-spec skill to generate the spec artifact at .codex/plans/PLAN_<NAME>/spec.md.

Frequently Asked Questions about create-spec

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

FAQPage Schema
How do I generate a testable LP spec package from a user requirement?

To generate a testable LP spec package, provide your user requirement to the skill. It outputs a canonical spec containing business context, UX flows, rules, and acceptance criteria to support planning and validation workflows.

What is a canonical LP specification and when do I need it?

A canonical LP specification is a structured document containing business context, UX flows, rules, and acceptance criteria. You need it when establishing a baseline for LP planning and validation workflows to ensure testability.

How do I create machine-readable artifacts for LP planning orchestration?

You create machine-readable artifacts for orchestration by running the skill with your requirement. It emits both human-readable documentation and pipeline contracts ready to drive subsequent planning steps.

Does the generated specification include acceptance criteria and UX flows?

Yes, the generated specification includes both acceptance criteria and UX flows. The canonical spec package contains business context, rules, and these testable components to validate your LP requirements.

What is the best way to structure spec artifacts for a planning pipeline?

The best way to structure spec artifacts for a planning pipeline is generating a handoff-ready package. The skill creates a spec.md file and related pipeline contracts within a dedicated plan directory to drive subsequent steps.

Can I use this specification generation approach without external dependencies?

Yes, you can use this specification generation approach without external dependencies. The skill operates independently to transform your user requirement into a complete, testable spec package and orchestration artifacts.