Solution Shaping & Strategy FAQs

Question 1

How does the document hierarchy work?

Accepted Answer

It maintains consistency across three levels: the high-level Shaping doc (ground truth), the Slices doc (breadboards), and individual Slice Plans (implementation details), ensuring changes ripple through all levels.

Question 2

What is a 'Fit Check'?

Accepted Answer

A Fit Check is a decision matrix that compares different solution options (Shapes) against specific Requirements (R) to see which approach best satisfies the project goals through a binary pass/fail system.

Question 3

When should I use a 'Spike'?

Accepted Answer

Use a Spike when there is technical uncertainty about a specific component. It is a dedicated investigation task to learn how existing systems work and identify the concrete steps needed for implementation.

Question 4

What is 'breadboarding' in this skill?

Accepted Answer

Breadboarding is a technique to map out the affordances (what the user can do) and the wiring (how data flows) of a solution without committing to a full UI design or finalized code.

Question 5

What is 'shaping' in the context of this Claude Code skill?

Accepted Answer

Shaping is a pre-development phase where you define the boundaries of a project, identify requirements, and sketch out solution 'shapes' to ensure feasibility and fit before committing to full implementation.

Solution Shaping & Strategy

Key Features

Use Cases

Solution Shaping & Strategy

Key Features

Use Cases