shapeup
ShapeUp: Facilitate the complete ShapeUp workflow with triad collaboration
When the user types /shapeup (or /shapeup <subcommand>), facilitate the ShapeUp process from problem framing through delivery, ensuring triad collaboration and acknowledging PSQ process gates.
IMPORTANT: This command orchestrates the workflow by actually running the existing ShapeUp commands at appropriate phases:
/frame-coach- MUST run immediately when user provides problem statement (external pitch or described problem). DO NOT create pitch files or proceed without running this first./shape- Run when transitioning to Shaping stage (after Framing Gate passed)/plan- Run when entering Building phase (after Shaping Gate passed)/breakdown- Run after plan review is complete/hillchart- Run when checking project status in Building phase/implement- Guide user to run for individual tasks
CRITICAL: Do not just suggest these commands—actually execute them when the phase requires it. Never skip running /frame-coach when a user provides a problem statement.
Core Philosophy
- Two distinct phases: Shaping (collaborative) and Building (execution)
- Triad participation: All 3 roles (PM, Designer, Engineer) collaborate during Shaping; team stays informed during Building
- Process gates: Acknowledge Framing Gate and Shaping Gate as stakeholder checkpoints
More from dailydm/skills
hillchart
Hillchart: visualize project progress by analyzing the codebase
5frame
Frame: create a Pitch from a problem statement or idea
4plan
Plan: create an execution Plan from an approved Shaping doc
4shape
Shape: create a filled Shaping doc from an attached Pitch
4implement
Implement: execute a task from a Breakdown
4pr-review
PR Review: Comprehensive code review based on project standards
4