design

Guide design sessions to elicit user intent and constraints before implementation.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/atmigtnca/sidep-ops --skill design-atmigtnca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/atmigtnca/sidep-ops/tree/main/skills/design
Command: npx skills add https://github.com/atmigtnca/sidep-ops --skill design-atmigtnca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design collaboration and upfront planning to clarify intent, requirements, and constraints before implementation.

Core Features & Use Cases

  • Socratic design dialogue to surface goals, constraints, and success criteria.
  • Ambiguity scoring and mode-based questioning (--quick, --standard, --deep).
  • Generate a formal design spec and get user approval before planning.

Quick Start

Describe an idea and start a guided design session by selecting a mode (--quick, --standard, or --deep).

Frequently Asked Questions about design

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

FAQPage Schema
How do I turn ideas into a solid design spec before coding?

Turn ideas into a solid design spec by using a Socratic design dialogue to surface goals, constraints, and success criteria, then generating formal design documentation for final approval. This structured exploration ensures requirements are fully clarified before implementation begins.

What is the best way to reduce ambiguity in feature design?

Reduce ambiguity in feature design by applying ambiguity scoring and mode-based questioning during early discovery or backlog refinement. Scoring ambiguity helps teams systematically identify unresolved constraints and elicit clear user intent before moving forward.

How do I elicit user intent and constraints for component architecture?

Elicit user intent and constraints for component architecture through guided Socratic design sessions. These sessions help teams define workflows, surface technical limitations, and document success criteria across early discovery and design reviews.

Can I run a quick design review for backlog refinement?

You can run a quick design review for backlog refinement by selecting the --quick mode. This mode initiates a fast-paced Socratic dialogue to score ambiguity and capture essential constraints without the depth required by --standard or --deep modes.

When should I not use upfront design exploration?

Upfront design exploration should be bypassed when implementation requirements are already fully defined and approved. If there is zero ambiguity in user intent, constraints, and success criteria, a formal Socratic dialogue and design spec generation are unnecessary.

Does the design process require formal approval before planning?

The design process requires a formal approval step before planning to ensure all elicited constraints and success criteria are validated. Generating a formal design spec secures team alignment and final approval before any implementation phase begins.