"Welcome to ShapeUp! Let's start a new project.

First, I need to know the project details:
- Domain name (e.g., 'payments', 'family-messaging', 'attendance-plus')
- Project name (e.g., 'bank-deposit-reconciliation', 'attendance-notifications')

This will create the project structure at:
projects/<domain>/<project>/

What domain and project name should we use?"

"Great! Now let's start with your Problem.

📄 Do you have an external pitch (from Google Doc)?

If yes: Paste the key points (Problem, Who's affected)
        Note: Appetite will be set by leadership after reviewing
        the problem and first instinct solutions.
        I'll run /frame-coach to evaluate and refine the problem.

If no:  Describe the problem you're trying to solve
        and I'll help you frame it.

Remember: All triad members should be present for Framing."

"Your framing has been evaluated. Let's align the triad on the problem:

Discussion prompts (discuss together as a team):
[Select 2 most relevant prompts from "Problem Alignment Prompts" library]

Once aligned, let's capture first instinct solutions.
(Note: Appetite will be set by leadership after reviewing problem + solutions)"

"Let's capture first instinct solutions from each perspective.
No wrong answers — we're exploring the solution space.

Discussion prompts:
[Select 2 most relevant prompts from "First Instinct Solutions Prompts" library]

These instincts will inform our shaping. Often the best solutions
combine insights from all three perspectives.

Capture and document these first instinct solutions together."

"Now that we have:
✅ Problem definition (refined via /frame-coach)
✅ Triad alignment on the problem
✅ First instinct solutions captured

⛳ FRAMING GATE CHECK
   Leadership reviews the problem and first instinct solutions, then:
   1. Sets the Appetite (time/effort allocation)
   2. Approves both the problem and first instinct solutions
   
   [ ] Yes, appetite set and both approved — proceed to Shaping
   [ ] Not yet — pause here, get leadership review and approval first

The appetite is determined by leadership based on:
- The problem's importance and priority
- The complexity implied by the first instinct solutions
- Available resources and business context

Once appetite is set and approved, we'll proceed to formal shaping."

"Now let's shape the solution. I'll create a shaping doc and we'll
refine it together.

Running /shape with your pitch...

"📐 BREADBOARD (Places, Affordances, Connections)

Discussion prompts:
[Select 2 most relevant prompts from "Breadboard Review Prompts" library]

Discuss together, then confirm when ready."

"🎨 FOR THE DESIGNER: Fat Marker Sketches/Prototypes

Now that the breadboard is complete, create fat marker sketches or 
prototypes to visualize the solution at the right level of detail.

Feel free to copy this prompt template to start in Figma:

---
Make prototype: Replicate the attached page applying a hand-drawn fat 
marker aesthetic: FIRST, ask the user which sections should remain 
visually high-level/non-functional. For these sections, use skeleton-style 
placeholders: light grey box characters (████████) with text-gray-400 and 
.sketch-border (not thick) with grey borders instead of black. Create an 
SVG filter in the root component (<svg width="0" height="0" 
style={{ position: 'absolute' }}>) with feTurbulence 
(type="fractalNoise", baseFrequency="0.05", numOctaves="3") and 
feDisplacementMap (scale="3"). Define .sketch-border (2px black border, 
2px border-radius, -2px offset) and .sketch-border-thick (4px black 
border, 3px border-radius, -3px offset) in /styles/globals.css using 
::before pseudo-elements with absolute positioning, pointer-events: none, 
and filter: url(#sketch-filter). Apply these classes to all containers, 
cards, buttons, and navigation—never use standard Tailwind borders. Use 
monospace fonts (font-mono) throughout with this hierarchy: page titles 
(text-2xl font-bold), card/section labels (text-sm, often uppercase), 
large metrics (text-3xl font-bold), supporting details (text-sm 
text-gray-600), buttons (text-sm), module titles (font-bold), module 
descriptions (text-xs text-gray-400), nav section headers (text-xs 
font-bold). STRICT GREYSCALE ONLY: All colors must be white, gray-50, 
gray-100, gray-200, gray-300, gray-400, gray-600, or black—no blues, greens, 
reds, or any other colors. Sharp rectangular shapes (no rounded corners), 
low-fidelity hand-drawn aesthetic. Add inline styles where needed: 
style={{ borderBottom: '4px solid black' }}.
---

The fat marker sketches help the team visualize the solution without 
getting into pixel-perfect detail. They should match the breadboard's 
places, affordances, and connections.

While the designer works on sketches, the team can continue with rabbit 
holes and no-gos. Share sketches when ready for triad review."

"🐰 RABBIT HOLES (Risks)

Discussion prompts:
[Select 2 most relevant prompts from "Rabbit Holes (Risks) Prompts" library]

Discuss together, then confirm when ready."

"🚫 NO-GOS (Boundaries)

Discussion prompts:
[Select 2 most relevant prompts from "No-Gos (Boundaries) Prompts" library]

Discuss together, then confirm when ready."

"📝 Shaping Complete Checklist:

- [ ] Breadboard captures all key flows
- [ ] Fat marker sketches/prototypes created (recommended)
- [ ] Risks identified and classified
- [ ] No-gos protect the appetite
- [ ] All 3 roles have contributed and agree

🎨 FOR THE DESIGNER: Design Review with Paul

Before proceeding to the Shaping Gate, review the design artifacts 
(breadboard, fat marker sketches/prototypes) with @Paul Hershey for 
design QA and feedback.

This review should happen before the Shaping Gate to ensure design 
alignment before the Go/No-Go decision.

⛳ SHAPING GATE CHECK
   Has the Pitch been approved at the Shaping Gate (Go/No-Go)?
   
   [ ] Yes, Go decision — proceed to Building
   [ ] Not yet — pause here, schedule Shaping Gate review
   [ ] No-Go — archive this pitch, return to problem discovery

If approved, I'll transition to Building phase."

"To check status, I need to know which project you're working on.

Please specify:
- The project name/path (e.g., 'payments/bank-deposit-reconciliation')
- Or say 'list projects' to see available projects"

"Welcome to ShapeUp! To get started, I need to know which project you're working on.

📋 Which project would you like to work on?

Option 1: Existing project
- I'll scan the projects/ directory and list available projects
- You can select from the list or provide the project path

Option 2: Brand new project
- Confirm it's a new project
- I'll guide you through /shapeup start

Please specify:
- The project name/path (e.g., 'payments/bank-deposit-reconciliation')
- Or say 'new project' if this is brand new
- Or say 'list projects' to see available projects"

"I don't see a project at that path. Is this a brand new project?

[ ] Yes, new project — I'll guide you through /shapeup start
[ ] No, existing project — please check the path or provide the correct project location"