shaping

Guide teams to define problems and explore solution options in shaping documents.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/ReadyStateChange/agents --skill shaping-readystatechange
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shaping
Source: https://github.com/ReadyStateChange/agents/tree/main/skills/shaping
Command: npx skills add https://github.com/ReadyStateChange/agents --skill shaping-readystatechange

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterative, collaborative problem framing and option shaping to align user needs with viable solution paths.

Core Features & Use Cases

  • Enables joint problem definition (R) and exploration of solution options (S) with traceable relationships.
  • Enforces multi-level consistency across shaping documents, slices, and breadboards for reliable governance.
  • Supports structured conversations that surface requirements, shapes, and implementation considerations early in the lifecycle to reduce drift.

Quick Start

Start a shaping session by outlining the problem and at least one shape, then generate a shaping document and a breadboard for execution.

Frequently Asked Questions about shaping

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

FAQPage Schema
What is collaborative problem shaping in product discovery?

Collaborative problem shaping is a structured method to define problems and explore solution options early in product design. It aligns stakeholders on requirements and potential shapes to reduce drift before execution begins.

How do I align stakeholders on requirements and design options?

To align stakeholders on requirements and design options, run a structured shaping session that explores solution paths with traceable relationships. This ensures multi-level consistency across shaping documents and breadboards for reliable governance.

How do I start a shaping session for early product design?

Start a shaping session by outlining the problem and at least one shape. Then generate a shaping document and a breadboard to establish traceability and prepare for execution.

Can I enforce traceability across shaping, slices, and breadboards?

Yes, you can enforce traceability across shaping, slices, and breadboards. The process enforces multi-level consistency and required document structure to ensure reliable governance throughout the design lifecycle.

When should I use problem framing instead of direct implementation?

Use problem framing during early product discovery to surface requirements, shapes, and implementation considerations collaboratively. This reduces drift and aligns user needs with viable solution paths before committing to direct implementation.