grill-po

Grill PO

Interview the user relentlessly about every aspect of their plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask questions one at a time, waiting for feedback on each before continuing.

If a question can be answered by exploring the codebase, explore the codebase instead.

Domain Awareness

During codebase exploration, also look for existing documentation.

File Structure

Single-context repo:

/
├── bounded-context.md
├── docs/
│   └── features/
│       ├── place-order.feature
│       └── cancel-order.feature
└── src/

Multi-context mono-repo:

/
├── README.md                          ← contains "Bounded Contexts" section (context map)
├── AGENTS.md                          ← contains "Bounded Contexts" section (context map)
├── docs/
├── src/
│   ├── ordering/
│   │   ├── ordering-bounded-context.md
│   │   └── docs/features/             ← context-specific features
│   └── billing/
│       └── billing-bounded-context.md

Create files lazily — only when you have something to write.

Detecting the structure:

• If a bounded-context.md exists at root → single context
• If *-bounded-context.md files exist elsewhere → multi-context; read the "Bounded Contexts" section of README.md or AGENTS.md for the context map
• If neither exists → create bounded-context.md lazily when the first term is resolved

When multiple contexts exist, infer which one the current topic relates to. If unclear, ask.

During the Session

Challenge against the glossary

When the user uses a term that conflicts with the existing language in the bounded-context file, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"

Also scan existing .feature files for terminology drift: if a scenario uses a term differently from the bounded-context file, surface it. "Your feature file says 'purchase' but the glossary defines that concept as 'order' — which should it be?"