design

Convert natural language feature descriptions into design.md documents with user stories and API contracts.

7|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/skullninja/coco-workflow --skill design-skullninja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/skullninja/coco-workflow/tree/main/skills/design
Command: npx skills add https://github.com/skullninja/coco-workflow --skill design-skullninja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designers and engineers spend excessive time translating vague feature descriptions into concrete designs. This Skill automatically converts natural language input into a complete design artifact, accelerating planning and alignment.

Core Features & Use Cases

  • Generate user stories and acceptance criteria from a feature description.
  • Produce a comprehensive design.md including technical approach, API contracts, and research decisions.
  • Write the design to specs/{feature}/design.md and reuse templates and discovery inputs when available.

Quick Start

Provide a natural language feature description and let Coco generate specs/{feature}/design.md.

Frequently Asked Questions about design

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

FAQPage Schema
How do I generate user stories and acceptance criteria from a feature description?

To generate user stories and acceptance criteria, provide a natural language feature description and the Skill outputs a complete design.md document. This artifact includes technical approach, API contracts, and research decisions alongside the stories.

What is the best way to turn a natural language feature description into a technical design document?

Turning a natural language feature description into a technical design document is done by converting the text into a structured design.md file. The output captures user stories, API contracts, and technical approach automatically.

Can I use custom templates when generating a design specification?

You can use custom templates when generating a design specification by placing a design-template.md file in the .coco/templates directory. The Skill will leverage this template structure when writing the design.md output.

How does generating a design.md file work within the coco workflow?

Generating a design.md file within the coco workflow works by reading project configuration from .coco/config.yaml and discovery inputs. It then writes the complete design artifact to the specs/{feature}/design.md path.

Do I need a specific project configuration to output API contracts and technical approach documents?

You need a .coco/config.yaml file to define the default specs directory before outputting API contracts and technical approach documents. The Skill relies on this configuration to correctly write the design.md file.

Are there limitations when converting vague feature descriptions into design specifications?

A limitation when converting vague feature descriptions into design specifications is that the output quality depends heavily on the input clarity. Providing detailed natural language descriptions ensures accurate user stories and API contracts.