shaping

Structure problem framing and option shaping for collaborative solution discovery.

10|Updated Dec 13, 2016
One-click install
npx skills add https://github.com/vitallium/dotfiles --skill shaping-vitallium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shaping
Source: https://github.com/vitallium/dotfiles/tree/main/dot_agents/skills/shaping
Command: npx skills add https://github.com/vitallium/dotfiles --skill shaping-vitallium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shaping provides a structured, collaborative approach to define problems and explore solution options, ensuring team alignment from requirements to final shapes.

Core Features & Use Cases

  • Multi-level consistency across Big Picture, Shaping doc, Slices, and Slice Plans to keep truth aligned as work progresses.
  • Start a session by capturing Requirements (R) or Shapes (S) entry points and iterating between them.
  • Fit Check, Breadboard, Spikes, and Slicing to guide decision-making and implementation planning.
  • Centralized documentation workflow that facilitates traceability, versioning, and collaboration.

Quick Start

Describe your problem and select an initial shape to begin a shaping session.

Frequently Asked Questions about shaping

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

FAQPage Schema
What is shaping in product management and how does it help with collaborative problem framing?▼

Shaping methodology streamlines collaborative solution discovery by structuring problem framing and option shaping for product teams. It enforces multi-level consistency across big picture, shaping docs, and slice plans to keep team truth aligned during development.

How do I structure product requirements and solution shapes during a design session?▼

Start a session by capturing Requirements (R) or Shapes (S) entry points and iterating between them. This formalizes the R and S levels, allowing teams to compare shapes, run fit checks, create breadboards, and execute spikes before finalizing an implementation plan.

When should I use breadboarding and spikes in product development?▼

Use breadboarding and spikes during the decision-making phase to guide implementation planning after selecting a shape. These techniques run fit checks to validate viability and de-risk solution shapes before committing to a final build plan and slicing.

Can I use this shaping methodology for iterative requirements definition in software development?▼

Yes, this shaping methodology applies directly to product design and development projects where teams iteratively define requirements. It enforces multi-level consistency across shaping docs and slice plans to maintain truth alignment as software work progresses.

Does this product management shaping workflow support traceability and versioning for documentation?▼

Yes, this shaping workflow provides centralized documentation that facilitates traceability, versioning, and collaboration. It maintains multi-level consistency across the big picture, shaping doc, slices, and slice plans to keep truth aligned as project work progresses.