shaping

Facilitate collaborative problem definition and solution shaping through structured methodologies.

1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/iancleary/dotfiles --skill shaping-iancleary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shaping
Source: https://github.com/iancleary/dotfiles/tree/main/.claude/skills/shaping
Command: npx skills add https://github.com/iancleary/dotfiles --skill shaping-iancleary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured methodology for collaboratively defining problems (requirements) and exploring potential solutions (shapes), ensuring clarity and alignment before implementation.

Core Features & Use Cases

  • Iterative Requirement Gathering: Systematically capture and refine user needs.
  • Solution Exploration: Compare multiple design approaches (shapes) against requirements.
  • Fit Check Analysis: Use decision matrices to objectively evaluate solution viability.
  • Use Case: When developing a new feature, use this Skill to work with stakeholders to clearly define what the feature must do (requirements) and then explore different ways to build it (shapes), selecting the best fit before coding begins.

Quick Start

Use the shaping skill to start a new shaping session by offering the user entry points to begin from requirements or shapes.

Frequently Asked Questions about shaping

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

FAQPage Schema
How do I collaboratively define problems and solutions before product development?

Collaborative problem and solution definition uses structured methodologies to iteratively gather requirements and compare multiple design approaches, ensuring alignment before implementation begins.

What is the best way to compare different solution options against product requirements?

Comparing solution options against requirements uses a fit check analysis with decision matrices to objectively evaluate the viability of different design shapes before coding begins.

How do I structure iterative requirement gathering with stakeholders for a new feature?

Iterative requirement gathering systematically captures and refines user needs through multi-level document consistency, allowing stakeholders to clearly define what a feature must do.

Can I start a shaping session from either requirements or shapes?

Yes, you can start a shaping session from either entry point, offering the flexibility to begin by defining requirements first or by exploring potential solution shapes directly.

When should I use a structured methodology for solution design?

Use a structured methodology for solution design when developing a new feature that requires stakeholders to clearly define requirements and explore different ways to build it beforehand.

Does the shaping methodology support multi-level document consistency?

Yes, the shaping methodology supports multi-level document consistency across defined phases for shaping and slicing, ensuring structured alignment throughout the requirement and solution exploration process.