shaping

Iterate on requirements and shapes with R/S notation and Big Picture alignment.

1.4k|90|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/rjs/shaping-skills --skill shaping-rjs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shaping
Source: https://github.com/rjs/shaping-skills/tree/main/shaping
Command: npx skills add https://github.com/rjs/shaping-skills --skill shaping-rjs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shaping provides a structured methodology for collaborative problem framing and solution exploration. It helps teams iteratively define requirements and evaluate shapes before committing to implementation.

Core Features & Use Cases

  • R/S driven: fosters iterative development by maintaining a live relationship between requirements (R) and shapes (S).
  • Breadboarding & Big Picture: guides teams from shaping through slicing with a visible Big Picture summary.
  • Multi-level consistency: ensures truth stays aligned across Big Picture, Frame, Shaping, and Slices.

Quick Start

Start a shaping session by outlining the problem (R) and sketching a shape (S); then breadboard to map affordances and create a Big Picture summary.

Frequently Asked Questions about shaping

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

FAQPage Schema
What is collaborative shaping in product management?

Breadboarding maps solution affordances during product shaping to create a visible Big Picture summary. It guides teams from initial framing through slicing, ensuring truth stays aligned across all documentation levels.

How do I maintain consistency between requirements and solution shapes?

You can use this shaping methodology for teams and projects that require multi-level consistency. It enforces explicit R/S notation and full fit checks, making it suitable for collaborative environments needing structured framing and breadboarding.

What is breadboarding in the context of product shaping?

Breadboarding maps solution affordances during product shaping to create a visible Big Picture summary. It guides teams from initial framing through slicing, ensuring truth stays aligned across all documentation levels.

How do we start a collaborative shaping session for a new feature?

You maintain consistency by enforcing explicit R/S notation and full fit checks during collaborative shaping. This ensures the living Big Picture stays perfectly aligned with ground truth documents across Frame, Shaping, and Slices.

Can I use this shaping methodology for small team projects?

Start a shaping session by outlining the problem as a requirement and sketching a solution shape. Then, use breadboarding to map affordances and generate a Big Picture summary for team alignment.