shaping

Coordinate collaborative problem-definition sessions and capture structured solution options.

157|12|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/dcosson/h2 --skill shaping-dcosson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shaping
Source: https://github.com/dcosson/h2/tree/main/internal/config/templates/styles/opinionated/skills/shaping
Command: npx skills add https://github.com/dcosson/h2 --skill shaping-dcosson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shaping techniques help teams collaboratively define problems, establish requirements, and explore solution options before committing to an approach.

Core Features & Use Cases

  • Iterative problem definition and option shaping between stakeholders.
  • Consistency guidance across R, shapes, and breadboard artifacts to prevent drift.
  • Structured progression from shaping to slicing with traceable documentation.
  • Facilitates collaborative decision-making and alignment in early-stage work.

Quick Start

Kick off a shaping session with the user to define requirements and explore initial shapes.

Frequently Asked Questions about shaping

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

FAQPage Schema
How do I facilitate collaborative problem definition and requirement gathering with stakeholders?

Collaborative problem definition is facilitated through structured shaping sessions that guide stakeholders in establishing requirements, exploring initial shapes, and capturing solution options before implementation.

What is the best way to maintain consistency between requirements, shapes, and breadboard artifacts?

Maintaining consistency between requirements, shapes, and breadboard artifacts requires enforcing cross-level synchronization during shaping sessions to prevent documentation drift across early-stage product and design work.

How do I transition from problem shaping to slicing with traceable documentation?

Transitioning from problem shaping to slicing involves guiding structured progression workflows that ensure traceable documentation is captured across every frame, shaping, and breadboard artifact.

Can I use shaping methodology for early-stage product and research work before committing to a specific approach?

Shaping methodology applies directly to early-stage product, design, and research work where stakeholders must collaboratively agree on requirements and explore potential solution shapes before committing to an implementation approach.

Do I need any specific tools or dependencies to run a problem shaping session?

Running a problem shaping session requires no specific external tools or dependencies, as the methodology coordinates iterative problem definition, option shaping, and synchronized documentation natively.

Why does documentation drift occur during collaborative design and research sessions?

Documentation drift occurs when cross-level consistency is not enforced between requirements, shapes, and breadboard artifacts, which structured progression and synchronized shaping workflows are designed to prevent.