cy-create-spec

Creates unified product and technical specifications with companion catalogs through staged research and grilling.

2.7k|171|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/compozy/compozy --skill cy-create-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cy-create-spec
Source: https://github.com/compozy/compozy/tree/main/.agents/skills/cy-create-spec
Command: npx skills add https://github.com/compozy/compozy --skill cy-create-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writing a feature spec that downstream LLM agents can actually implement requires gathering codebase context, market research, user decisions, and technical design in one coherent document — a process that usually produces vague specs, missed edge cases, and rework. This Skill structures that entire authoring process into a two-stage workflow with mandatory research and decision grilling before any file is written.

Core Features & Use Cases

  • Two-stage spec authoring: Produces one _spec.md with a Product part (WHAT, WHY, WHO) and a Technical part (HOW), separated by a user-confirmed checkpoint.
  • Companion catalogs: Generates _user_stories.md with acceptance criteria and edge cases, a _dx.md developer-experience contract, a _uiux.md UI change map for UI-bearing features, and a _tests.md test contract with stable IDs.
  • Frontier grill protocol: Runs parallel codebase and market research, then interviews the user in rounds until every design decision is resolved, recording significant trade-offs as ADRs.
  • Use Case: A developer wants to add webhook notifications to their product. The Skill researches the codebase and competing products, grills them on which events should notify users, freezes the CLI/API surface, then writes the full spec, story catalog, and test contract ready for task breakdown.

Quick Start

Ask the agent to create a spec for your new feature idea, providing the feature name and any existing notes you have.

Frequently Asked Questions about cy-create-spec

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

FAQPage Schema
How do I write a technical specification for a new feature?

Provide the feature name and optional idea notes, then answer the grill rounds. The Skill researches your codebase and market first, then writes a `_spec.md` with a Product part and Technical part plus companion catalogs for stories, DX, UI, and tests.

What files does a feature specification workflow produce?

It produces `_spec.md` as the core document, plus `_user_stories.md` with acceptance criteria and edge cases, `_dx.md` as the developer-experience contract, `_uiux.md` for UI-bearing features, `_tests.md` as the test contract, and ADRs under an `adrs/` directory.

When should I not use a spec creation workflow?

Do not use it for task breakdown, review remediation, or direct code implementation — those belong to downstream skills like task creation and execution. It is strictly for specifying requirements and technical design.

Can I update an existing spec instead of creating a new one?

Yes. If a `_spec.md` already exists at the feature slug, the Skill operates in update mode, preserving unchanged sections and mirroring every behavior or interface change into the affected companion files so the set stays in sync.

What happens if web research tools are unavailable during spec creation?

The Skill proceeds with codebase research only and explicitly notes the limitation. The market research track is skipped rather than blocking the workflow, and the grill continues with the available findings.