create-spec

Generate machine-readable implementation specifications from BDD-formatted PRDs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Hubble-inc/demo-nego --skill create-spec-hubble-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-spec
Source: https://github.com/Hubble-inc/demo-nego/tree/main/.cursor/skills/create-spec
Command: npx skills add https://github.com/Hubble-inc/demo-nego --skill create-spec-hubble-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill bridges the gap between high-level product requirements and detailed technical implementation by automatically generating machine-readable specifications (SPEC) from natural language Product Requirements Documents (PRDs).

Core Features & Use Cases

  • BDD to SPEC Conversion: Transforms Gherkin-formatted behavior specifications into structured API definitions, database schemas, and frontend component interfaces.
  • Contract Generation: Creates common.md, backend.md, and frontend.md files that serve as the single source of truth for implementation contracts.
  • Use Case: A Product Manager provides a tech-prd/user-authentication.md file. This Skill processes it to generate OpenAPI specs for the backend API, Prisma schema for the database, and React component interfaces for the frontend, ensuring all parts of the system adhere to the defined behavior.

Quick Start

Use the create-spec skill to generate implementation contracts from the file docs/tech-prd/user-profile.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 API specifications from a PRD?

To generate API specifications from a PRD, you use a tool that transforms BDD-formatted behavior specifications into machine-readable contracts. This process automatically extracts structured API definitions and database schemas from your natural language product requirements.

How do I convert BDD Gherkin scenarios into frontend and backend contracts?

Converting BDD Gherkin scenarios into frontend and backend contracts involves parsing behavior specifications to generate separate interface files. This creates structured OpenAPI specs for backend APIs and React component interfaces for frontend components from the defined behavior.

What is a single source of truth for software development contracts?

A single source of truth for software development contracts is a set of generated specification files ensuring traceability. It typically includes common definitions, backend APIs, and frontend component interfaces all derived directly from the product requirements document.

Can I generate separate contract files for frontend and backend from a PRD?

Yes, you can generate separate contract files for frontend and backend from a PRD. The conversion process creates distinct common.md, backend.md, and frontend.md files, ensuring all system parts adhere to the defined behavior and maintain clear traceability.

How to create OpenAPI and Prisma schemas from product requirements?

Creating OpenAPI and Prisma schemas from product requirements requires processing BDD-formatted documents through a specification generator. This automatically produces structured API definitions and database schemas that serve as the implementation source of truth.

Does create-spec work with React component interfaces and OpenAPI definitions?

Yes, create-spec works with React component interfaces and OpenAPI definitions by generating them from BDD specifications. It processes your PRD to output structured formats for frontend components and backend APIs, ensuring implementation aligns with product behavior.