sketching-design

Map a story-level behavioral spec to an implementation starting point.

2|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/chriswch/praxis --skill sketching-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sketching-design
Source: https://github.com/chriswch/praxis/tree/main/skills/sketching-design
Command: npx skills add https://github.com/chriswch/praxis --skill sketching-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about sketching-design

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

FAQPage Schema
How do I map a behavioral spec to an implementation starting point when the code path is non-obvious?

Mapping a behavioral spec to an implementation starting point requires locating affected files, matching existing code patterns, and proposing one implementation direction to produce a lightweight design sketch. This identifies the blast radius and names the first failing test.

When should I create a design sketch before starting test-driven development?

You should create a design sketch before test-driven development when the implementation path is non-obvious or requires mapping spec to code. If the change is obvious, a triage step determines that sketching is unnecessary and can be skipped.

How do I find existing code patterns to match a new story-level spec?

Finding existing code patterns to match a new story-level spec involves exploring the codebase for analogs and conventions. This pattern matching prevents inventing new structures and helps pinpoint the files, modules, and entry points the story touches.

What is the best way to decide the first failing test for TDD from a behavioral specification?

Deciding the first failing test for TDD from a behavioral specification involves committing to one implementation approach and specifying the core data-structure implication. The design sketch process names this first failing test to drive development.

Does sketching-design require any external dependencies to map a spec to code?

Sketching-design requires no external dependencies to map a spec to code. It operates by analyzing a single-story behavioral specification to produce a concise sketch.md and a structured results JSON file into the artifact directory.

What files does the design sketch process output into the artifact directory?

The design sketch process outputs a concise sketch.md and a structured results/sketching-design.json into the artifact directory. These files provide the implementation direction and structured data for orchestrator routing.