write-specs

Converts SDD proposals into domain-scoped delta specifications with Given/When/Then scenarios.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/lleontor705/cortex-ia --skill write-specs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-specs
Source: https://github.com/lleontor705/cortex-ia/tree/main/internal/assets/skills/write-specs
Command: npx skills add https://github.com/lleontor705/cortex-ia --skill write-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms SDD proposals into precise, domain-scoped delta specifications, enabling automated test stubs and traceability.

Core Features & Use Cases

  • Converts a proposal into a structured, domain-based spec set with clear, RFC 2119-compliant requirements.
  • Generates per-domain spec artifacts that seed the Architect and Test stages, with optional test stubs.
  • Integrates with the Spec-Driven Development pipeline to ensure proposals are verifiable and maintainable.

Quick Start

Run the write-specs skill after drafting an SDD proposal to produce per-domain delta specifications.

Frequently Asked Questions about write-specs

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

FAQPage Schema
How do I convert SDD proposals into executable domain specs?▼

To convert SDD proposals into executable domain specs, this tool reads Cortex-propagated proposals and produces per-domain delta specifications with Given/When/Then scenarios and optional test stubs.

What are delta specifications and when do I need them for Given/When/Then scenarios?▼

Delta specifications are domain-scoped requirement sets containing Given/When/Then scenarios. You need them when transforming proposals into verifiable artifacts within the Spec-Driven Development pipeline.

How do I generate test stubs from domain-scoped specifications?▼

Generating test stubs from domain-scoped specifications happens by translating SDD proposals into delta specs that include optional test stubs, seeding the downstream Test stage.

Does the Spec-Driven Development pipeline support RFC 2119 compliant requirements?▼

Yes, the Spec-Driven Development pipeline supports RFC 2119 compliant requirements by ensuring every generated domain spec includes uniquely identified, verifiable conditions.

How many scenarios does each requirement need for delta specs?▼

Each requirement in delta specs needs three Given/When/Then scenarios: a happy path, an edge case, and an error state, ensuring comprehensive coverage.

Do I need Cortex to write domain-scoped specifications?▼

Yes, you need Cortex to write these domain-scoped specifications, as the tool reads Cortex-propagated proposals and persists the concatenated spec artifacts back to Cortex.