Cursor plan-chat vocabulary

The collision

Plans omit acceptance loops, mis-size L work as XS, or conflate DoR with DoD — expensive agent runs without checkpoints.

How to choose

1) Emit triage line first (XS–XL) sizing underlying work not just "write a plan" utterance. 2) L/XL? → forge-planning-standards: phases, tests, PDCA per phase, drift gate, model tiers. 3) Roadmap not ready? → cite DoR before WBS; suggest Product Management Versona session. 4) Discipline challenge needed? → named Versona (BA, ARCH, UX, …) — §5 output optional. 5) Mechanical breadth? → subagent (explore/shell) on cheaper tier; parent keeps integration.

Using several at once

PDCA + DoD define done per phase; DoR defines ready to start; Versona sessions live in forge-logs/ not calendar meetings. Estimation Versona owns method; triage sizes gate orchestration cost separate from story points.

Terms covered

• PDCA
• DoR
• DoD
• Versona
• subagent
• XS
• S
• M
• L
• XL
• WBS

Examples from chat / plan.md

User: "Plan LCDL break-in for mail ingest" → Triage: L · cross-repo → phases with lcdl tasks first, cockpit bridge second, PDCA harness per phase, ARCH Versona suggested for attach-owner invariant.

User: "fix typo in README" → Triage: XS · single file → no subagents, no PDCA table.

Bridge page plan-chat-vocabulary — read when multiple abbreviations appear in one sentence.