sketching-design

What problem does it solve?

Many story-level behavioral specs leave developers unsure where to begin coding; this Skill turns a spec into a concise, actionable starting point by locating the affected files, matching existing patterns, and proposing the single first implementation direction needed to write the first failing test.

Core Features & Use Cases

• Triage: Decide whether a sketch is necessary or if the change is obvious and should be skipped.
• Change map: Identify the files, modules, and entry points that the story touches and describe the blast radius.
• Pattern matching: Find existing analogs and conventions in the codebase to avoid inventing new structures.
• Direction & test: Commit to one implementation approach, specify the core data-structure implication if any, and name the first failing test to drive TDD.
• Outputs: Write a concise sketch.md and a structured results/sketching-design.json into the artifact directory for orchestrator routing.

Quick Start

Run sketching-design on the story artifact directory to produce a short sketch.md and a results/sketching-design.json in the artifact directory.