Verified:GitHub

wa:design-specs

Generate design specification artifacts from feature descriptions.

Updated Mar 26, 2026

Search Tags:#api-contracts #database-schema #sequence-diagrams #design-specs #non-functional-requirements #confluence-publish

Ready to run

npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-design-specs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wa:design-specs
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/design-specs
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-design-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a feature or epic description into implementable, structured specification artifacts so teams can align on API contracts, database schemas, and non-functional requirements before coding.

Core Features & Use Cases

Stage-based spec generation: Runs a multi-phase workflow (pre-flight, complexity assessment, API, schema, NFRs) guided by a mode/rigor tier.
API contract outputs: Produces endpoint-level method/path definitions with request/response schemas, error codes, authentication, and rate limits.
Database schema outputs: Generates table/collection design, relationships, indexes, and migration plans, and adds sequence diagrams for complex cases.
Non-functional requirements: Captures quantified performance, scalability, security, reliability, and observability targets for complex tiers.

Quick Start

Run /design-specs user notification preferences API to generate the planning artifacts for the specified feature.

Frequently Asked Questions about wa:design-specs

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

FAQPage Schema

How do I generate API contracts and database schemas from a feature description?▼

You can generate API contracts and database schemas by providing a feature or epic description to a design specification generator. This tool runs a multi-phase workflow to produce endpoint definitions, request/response schemas, table designs, and migration plans.

What is the best way to document non-functional requirements for a complex API?▼

Documenting non-functional requirements for a complex API is best handled by a complexity-tiered design spec generator. It captures quantified performance, scalability, security, reliability, and observability targets based on the feature's assessed complexity.

How do I create sequence diagrams for database schema migrations?▼

To create sequence diagrams for database schema migrations, use a design specification tool that adds them automatically for complex cases. It generates table designs, relationships, indexes, and sequence diagrams alongside the migration plans.

Can I publish design specifications to Confluence directly from the generation tool?▼

Yes, you can publish design specifications to Confluence directly. The tool writes versioned draft specs to local docs and optionally attempts a Confluence publish without blocking the workflow if the publish operation fails.

Does the design spec generation workflow require plan mode?▼

Yes, the design specification workflow requires plan mode to function. It uses plan mode to resolve development rigor and guide the multi-phase complexity assessment before generating the structured specification artifacts.