Pipeline Crm M0 2 Stage Gate Jumps

loom-builderpromptmarkdown
Path: loom-builder/prompts/pipeline-crm-m0-2-stage-gate-jumps.mdRelative: prompts/pipeline-crm-m0-2-stage-gate-jumps.mdSubproject: loom-builderCategory: dispatch-prompts
Lines: 21Bytes: 2,632Imports: 0Exports: 0
loom-builderpromptmarkdownprompts

Content Preview

  1. # pipeline-crm M0.2 — Stage-Gate Hole: non-adjacent jumps bypass criteria
  3. ## INTENT
  4. Live smoke on `/home/mikes/base44CRM/pipeline-crm` proved a methodology-enforcement hole: a fresh lead (stage New, zero activities, painPoint/authority/timelineDays empty) was moved to Qualified via `POST /api/leads/:id/stage {"stage":"Qualified"}` and got **200** — should be 422. Existing gate logic validates only specific adjacent from→to pairs; skipping stages bypasses ALL criteria. SUCCESS METRIC: stage vali