design

Translate requirements into a structured design plan with templates.

52|3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill design-zte-aicloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/ZTE-AICloud/Co-OmniSpec/tree/main/skills/design
Command: npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill design-zte-aicloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and documenting executable design before coding is often overlooked, leading to misaligned implementations and repeated rework. This skill provides a structured design workflow that translates specifications into actionable design artifacts using templates, establishing a solid technical decision framework prior to implementation.

Core Features & Use Cases

  • Generates an executable design document from a plan template.
  • Establishes architecture decisions, data models, and contracts before code.
  • Improves traceability from spec to design to implementation, enabling safer handoffs to engineering teams.

Quick Start

Invoke the /design command with your project goals to trigger the design workflow and generate the initial design artifacts.

Frequently Asked Questions about design

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

FAQPage Schema
What is an executable design document in software architecture?

An executable design document translates project specifications into actionable architecture decisions, data models, and contracts before coding. It establishes a structured technical framework to guide implementation and ensure traceability from spec to code.

How do I generate design artifacts before coding from a project plan?

You generate design artifacts by invoking the /design command with your project goals. This triggers a workflow that translates requirements into structured design documents, data models, and execution plans using predefined templates.

When do I need to create architecture decisions and data models upfront?

You need upfront architecture decisions and data models when your software project requires upfront planning to influence implementation. This prevents misaligned implementations and repeated rework by establishing clear contracts before coding begins.

Can I use a template to establish technical contracts for feature planning?

Yes, you can use predefined plan templates to establish technical contracts for feature planning. The workflow automates translating your specifications into structured design artifacts, ensuring safer handoffs to engineering teams.

What's the best way to improve traceability from specifications to implementation?

The best way to improve traceability is to generate structured design documents and contracts before coding. This establishes a solid technical decision framework that directly maps specifications to implementation, enabling safer engineering handoffs.