design

To translate fuzzy product intents into a design-ready feature directory, this Skill uses interactive Socratic questioning to capture requirements and generate structured artifacts like component-specs.md and design-tokens.json.

A Socratic design workflow uses interactive, question-driven capture to convert vague requirements into concrete design artifacts. You need it when translating fuzzy product intents into a structured, design-ready feature directory.

You generate design-tokens.json and component-specs.md by capturing PRODUCT.md and DESIGN.md at the repo root, then applying post-processing to orchestrate these outputs into etc-native artifacts.

The design workflow requires no external dependencies but ensures alignment with /spec prerequisites. You invoke it with your project intent to capture markdown files and prepare design metadata for downstream phases.

To document gray areas during product design, the workflow post-processes captured markdown inputs to generate gray-areas-design.md, ensuring edge cases and ambiguities are recorded as etc-native artifacts for downstream phases.

Yes, you can update state.yaml.design_phase automatically by applying post-processing to the captured PRODUCT.md and DESIGN.md files, recording feature metadata for downstream phases.