spec-design

Automate specification and design workflows from feature idea to final approval.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/moonseokchoi-kr/moon-harness --skill spec-design-moonseokchoi-kr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-design
Source: https://github.com/moonseokchoi-kr/moon-harness/tree/main/skills/spec-design
Command: npx skills add https://github.com/moonseokchoi-kr/moon-harness --skill spec-design-moonseokchoi-kr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-design provides a structured workflow that captures ideas as formal specs and design artifacts up to implementation readiness.

Core Features & Use Cases

  • Automated, staged pipeline from Phase 1 spec to Phase 2 design and API contracts, including blocker checks and user gates.
  • Worktree-isolated collaboration for parallel features and independent approvals.
  • Supports WITH_UI and WITHOUT_UI modes, enabling architecture-only or full UI/API design flows.

Quick Start

Run the spec-design pipeline once with /spec-design start <feature> <WITH_UI|WITHOUT_UI> to begin the automated workflow.

Frequently Asked Questions about spec-design

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

FAQPage Schema
How do I turn feature ideas into software specs and UI designs before coding?

To turn feature ideas into specs and UI designs before coding, use an automated pipeline that captures ideas as formal specs and design artifacts. This enforces a staged workflow from Phase 1 specification to Phase 2 architecture and API design with automated phase advancement.

What is the best way to manage architecture and API design workflows for parallel features?

Managing architecture and API design workflows for parallel features is best handled using worktree isolation. This enables independent approvals and isolated collaboration for multiple features progressing through the specification and design pipeline.

Can I automate phase progression and enforce hard gates in a specification pipeline?

Yes, you can automate phase progression in a specification pipeline by applying hard gates and blocker checks. The workflow automatically advances from feature spec to design readiness while enforcing mandatory user input gates before proceeding.

Does the spec and design workflow support architecture-only features without UI components?

Yes, the spec and design workflow supports architecture-only features without UI components using WITHOUT_UI mode. This enables architecture-only design flows, while WITH_UI mode handles full UI and API design contracts.

When do I need blocker checks and user gates during software architecture design?

Blocker checks and user gates are needed during software architecture design when progressing through staged pipelines. They enforce hard gates between specification and design phases, ensuring user input is captured before API contracts and UI designs are finalized.