wa:design-feature

Plan and create design-only deliverables from feature descriptions via staged discovery and documentation.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-design-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wa:design-feature
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/design-feature
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-design-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a feature idea into a complete design package—requirements interview, research findings, and design documentation—without moving into implementation.

Core Features & Use Cases

  • Requirements & Discovery Interview: Collects feature requirements via the mandated discovery sub-skill so the design is grounded in user and project needs.
  • Design-Research Delegation: Runs dedicated research work to produce technical context for the design.
  • Design Documentation Suite: Generates documentation (scope changes by rigor level) and syncs it into the project context for later implementation.

Quick Start

Run the design-only workflow by calling /wa:design-feature with your feature description (optionally adding --rigor lite, standard, or strict).

Frequently Asked Questions about wa:design-feature

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

FAQPage Schema
How do I plan a feature end-to-end without writing implementation code?

Feature planning without implementation requires orchestrating requirements discovery, technical research, and design documentation stages to produce a complete design package. This workflow gathers project needs and generates design artifacts while stopping before any code is written.

What is the best way to document feature design requirements before development?

Feature design documentation is best produced through a structured discovery interview that collects requirements, followed by dedicated technical research to ground the design. The resulting documentation suite is then synced into the project context for downstream implementation use.

Can I adjust the scope of design documentation to match my project's planning needs?

Design documentation scope can be adjusted by setting a rigor level to lite, standard, or strict. This controls the depth of the generated design artifacts and requirements gathering during the planning workflow.

How does the feature design planning workflow handle technical research and architecture planning?

Technical research for architecture planning is handled by delegating dedicated research sub-skills during the workflow. This ensures the design documentation is grounded in accurate technical context before the final design artifacts are produced.

Do I need to start in plan mode to run the feature design workflow?

Plan mode is mandatory to run the feature design workflow. It uses a planning-session marker with stage gating to ensure requirements discovery and research are completed before design documentation is generated.

What is included in a design-only deliverable set for a new feature?

A design-only deliverable set includes requirements from a discovery interview, technical research findings, and generated design documentation. These artifacts are synced into context files to support later implementation without writing any code.