design-workflow

name	design-workflow
description	Use when drafting or revising technical design, API endpoint contracts, or advancing a service from evidence into design and implementation readiness (technical design, backend design, platform design, module boundary, API design, endpoint contract, validation, error code, service delivery, design closure, implementation readiness).
argument-hint	Target to design, e.g.: backend design update, api contract for Inventory get_stock_data, service delivery closure for Reporting, shared auth module design
user-invocable	true

Design Workflow

Covers technical design, API contract work, and service delivery closure — the full design phase after scope is clarified.

Module Routing

Identify the task, then load only the matching module via read_file before proceeding.

Task	Module
Platform, infrastructure, shared-runtime, or cross-service design needs to be drafted or revised	modules/technical-design.md
One API endpoint or service contract needs to be designed or made coding-ready	modules/api-contract.md
A service needs to be advanced from evidence into design closure and coding readiness	modules/service-delivery.md

Load exactly one module, then follow its Procedure section.

Typical Flow

service-delivery (orchestrates) → technical-design → api-contract → implementation readiness

For a single focused concern, load only the matching module directly.

When Not to Use This Skill

• Scope is still ambiguous → use discovery-workflow first
• An approved slice is ready for code execution → use execution-workflow
• Documents need to be moved, renamed, or archived → use document-lifecycle-workflow