generator-proposal

To convert a backlog item into a sprint proposal, the generator identifies exactly one ready item and transforms it into a bounded sprint contract. It grounds the scope using repository inputs like AGENTS.md, tracked-work.json, current-focus.md, and roadmap.md, then writes the proposal to .harness/<workstream-id>/sprint_proposal.md.

A bounded sprint contract is a concrete proposal document drafted from a single backlog item. It defines clear objectives, scope, acceptance criteria, risks, and required inputs to reduce ambiguity and align work with the roadmap for adversarial review.

The sprint proposal process ensures synchronization by checking the selected backlog item against docs/live/tracked-work.json, docs/live/roadmap.md, and current focus. It guarantees the chosen feature remains the sole active proposal and no other runnable sprint exists.

Generating a sprint proposal requires repository files including AGENTS.md, docs/live/tracked-work.json, current-focus.md, roadmap.md, ideas.md, progress.md, memory.md, reference docs, and linked records for the selected feature.

No, you cannot draft proposals for multiple items simultaneously. The generator ensures exactly one backlog item is selected for proposal and verifies no other runnable sprint exists to maintain strict focus and alignment.

Creating a sprint proposal generates .harness/<workstream-id>/sprint_proposal.md and .harness/<workstream-id>/status.json. It also produces optional scoped docs/records or roadmap updates to reflect the new contract state.