shaping

Guide teams in defining problems and exploring solution shapes collaboratively.

11|1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/SZoloth/skill-pack --skill shaping-szoloth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shaping
Source: https://github.com/SZoloth/skill-pack/tree/main/skills/shaping
Command: npx skills add https://github.com/SZoloth/skill-pack --skill shaping-szoloth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collaborative shaping provides a structured, multi-level framework to define problems and explore solution options, ensuring alignment between requirements, shapes, and implementations.

Core Features & Use Cases

  • Enables starting from either requirements or shapes and iterating to converge on a plan.
  • Maintains multi-level consistency across shaping, slicing, and breadboarding to prevent drift.
  • Provides frontmatter-driven governance for tooling, traceability, and collaboration.

Quick Start

Create a Frame with source material, distill the problem and outcome, then develop a Shaping doc with R and S sections before moving to Slices.

Frequently Asked Questions about shaping

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

FAQPage Schema
What is collaborative problem framing and shaping in product development?

Shaping and breadboarding prevent implementation drift by maintaining multi-level consistency and traceability across requirements, solution shapes, and development slices. This structured documenting practice ensures alignment between product, design, and engineering teams throughout the process.

How do I start shaping a product requirement from scratch?

Start shaping a product requirement by creating a Frame with source material to distill the problem and outcome. Then, develop a Shaping document with Requirements and Shapes sections before moving to Slices and breadboarding for implementation.

Can I begin the shaping process from existing solution shapes instead of requirements?

Yes, you can begin the shaping process from either requirements or existing solution shapes. The framework supports iterating from either starting point to converge on a unified plan, ensuring cross-level consistency and traceability throughout the documentation.

What is the best way to maintain consistency across requirements, slices, and breadboarding?

The best way to maintain consistency across requirements, slices, and breadboarding is using frontmatter-driven governance for tooling and traceability. This structured documenting practice enforces multi-level consistency and prevents drift across shaping, slicing, and implementation phases.

Does this collaborative shaping framework work for large-scale product and engineering teams?

Yes, this framework supports collaborative problem framing and shaping at scale across product, design, and engineering sessions. It enforces structured documenting practices and frontmatter-driven governance to maintain alignment and traceability for multiple teams.