lane-prompt-builder

What problem does it solve?

It prevents build-lane prompt failures by generating fully self-contained prompts that force a spawned Sonnet/Opus/Codex thread to follow TBM’s canon-doc boot sequence and the four-step close protocol, reducing stale/local-only handoffs and missing PR/comment outcomes.

Core Features & Use Cases

• Build-lane prompt construction with guardrails: Produces prompts that include SPAWN INVARIANT and a non-negotiable BOOT sequence so the spawned thread can’t drift from the repository’s current canon.
• Mandatory evidence-before-claim behavior: Enforces “verify-before-assert” and a deliverable shipment check against gitea/main before the thread writes anything.
• Deterministic close protocol: Requires writing a thread handoff file, committing it, pushing/opening a PR, and commenting the canonical <!-- handoff --> marker with the PR number to guarantee LT can pick up reliably.
• Concurrency and hot-file lock reminders: Embeds lane identity, active work avoidance, and hot-file constraints so multiple lanes don’t collide on canonical docs or workflow infrastructure.

Quick Start

Ask your AI to “use lane-prompt-builder to generate the Sonnet prompt for the rescue queue (#441/#442) with a queue ordered by Issues/PRs, explicit carve-outs, and the predecessor handoff path.”