skills.rest
LuizEduPP
LuizEduPPCOMMUNITY
Explore all skills by this author →
GitHub

design-create

Produce structured design documents covering requirements, architecture, risks, and APIs.

Updated Apr 10, 2026
Search Tags:#planning#architecture#documentation#review#api-design#design-docs#technical-decision
One-click install
npx skills add https://github.com/LuizEduPP/skills --skill design-create
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-create
Source: https://github.com/LuizEduPP/skills/tree/main/design-create
Command: npx skills add https://github.com/LuizEduPP/skills --skill design-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating thorough design documents can stall without a steady process, leaving teams unclear on architecture, APIs, risks, or review checkpoints before building.

Core Features & Use Cases

  • Structured Workflow: Follows Analyze, Research, Design, Document, and Review steps to keep every decision justified.
  • Template-driven Documentation: Supplies an outline covering overview, goals, non-goals, architecture components, API sketches, alternatives, and risks.
  • Use Case: Before launching a new feature, capture the system context, component responsibilities, proposed API contracts, and mitigation plans so implementation teams stay aligned.

Quick Start

Ask the assistant to draft a design document outlining requirement analysis, architecture, API details, alternatives, and risks for your upcoming feature.

Frequently Asked Questions about design-create

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

FAQPage Schema
How do I create a structured design document for a new feature?▼

To create a structured design document, follow a stepwise workflow covering analysis, research, architecture, documentation, and review. This process captures requirements, architecture components, API sketches, alternatives, and risks to justify technical decisions before implementation.

What should be included in an architecture design document for technical decisions?▼

An architecture design document should include an overview, goals, non-goals, component responsibilities, proposed API contracts, alternatives considered, and risk mitigation plans. This template-driven approach ensures implementation teams stay aligned on system context.

When do I need to draft a design doc for API planning?▼

You need to draft a design doc for API planning when you require documented guidance and review checkpoints before building new systems or features. It captures proposed API contracts and technical decisions to satisfy design validation and approval needs.

What is the best way to document technical decisions and system risks?▼

The best way to document technical decisions and system risks is by applying a structured workflow that evaluates alternatives and outlines mitigation plans. This ensures every architectural choice is justified and validated through a formal review process.

Can I use a template-driven workflow to align teams before system implementation?▼

Yes, you can use a template-driven workflow to align teams before implementation by capturing system context, component responsibilities, and proposed API contracts. This structured documentation process keeps teams informed and validates design decisions prior to building.

Related Skills

Explore More Software Engineering Skills→
bfree-trainerbfree-trainer
60

teach-impeccable

Capture project design context and persist it to AI configuration.

Official
Intermediate
shakhovskiya-createshakhovskiya-create

architecture

Generate C4 architecture designs and ADRs from an approved PRD.

Community
Advanced
ianclearyiancleary
1

planning

Generate detailed implementation plans with file paths and verification steps.

Community
Intermediate
AmidVoshakulAmidVoshakul

architecture-decision-records

Standardize creation and maintenance of Architecture Decision Records with templates.

Community
Intermediate