design

Generate technical design specifications with interfaces, data flow, and acceptance criteria.

15|4|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/jmylchreest/aide --skill design-jmylchreest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/jmylchreest/aide/tree/main/skills/design
Command: npx skills add https://github.com/jmylchreest/aide --skill design-jmylchreest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design mode generates a technical design specification that downstream SDLC stages can consume, detailing interfaces, data flow, rationale, and acceptance criteria.

Core Features & Use Cases

  • Define public APIs and interfaces first, including types and contracts.
  • Document data flow and component interactions to guide implementation and testing.
  • Record key architectural decisions and acceptance criteria for the TEST stage.
  • Use cases include designing a new service, a module, or a feature with clear interfaces and verification steps.

Quick Start

Provide a design for a new feature by outlining the interfaces, data flow, and acceptance criteria.

Frequently Asked Questions about design

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

FAQPage Schema
How do I generate technical design specifications for downstream SDLC stages?

To generate technical design specifications, define public APIs, document data flow, and record architectural decisions to produce a comprehensive spec for implementation and testing.

What is the best way to define public APIs and data flow diagrams for a new module?

The best way to define public APIs and data flow diagrams is to outline interfaces, types, and contracts first, then document component interactions to guide implementation and testing.

How do I document architectural decisions and acceptance criteria for feature planning?

To document architectural decisions and acceptance criteria, record key design rationale and verification steps within a technical specification to ensure the TEST stage can validate implementation.

Can I use this approach to design a new service with clear interfaces and verification steps?

Yes, you can use this approach to design a new service by defining its public interfaces, outlining data flow, and establishing acceptance criteria for clear verification steps.

When do I need a formal technical design specification over basic feature documentation?

You need a formal technical design specification when planning tasks require capturing public API definitions, data-flow diagrams, decision logs, and acceptance criteria for downstream stages.