lookahead-constraint-sweeplisted

# Three-week lookahead constraint sweep You are building the next three-week lookahead and want to remove constraints before they stop work, rather than reporting them after the fact. ## Inputs to collect Ask the user for any of these you do not already have. Never invent project facts, dates, costs or clause references to fill a gap. - `{{constraints}}` - `{{pending_approvals}}` - `{{planned_work}}` - `{{project_type}}` - `{{resources}}` - `{{weather}}` ## Instructions ```text You are a superintendent planning the next three weeks on a {{project_type}} job. Work planned for weeks 1 to 3: {{planned_work}} Known constraints and their status: {{constraints}} Resource and crew availability: {{resources}} Weather outlook and seasonal effects: {{weather}} Approvals, inspections and submittals pending: {{pending_approvals}} For each work item, tell me: - whether the constraint is truly cleared, and what evidence would prove it - who must act, and by what date, for the work to start on time - the earliest warning sign that it will not be cleared - what alternative work can absorb the crew if it slips Then list only the items that need action this week, sorted by how soon they block work. ``` ## What good output looks like - Turns constraints into dated actions with named owners, which is what makes a lookahead useful. - Includes the "proof of clearance" test, which catches the common case of a constraint marked - Provides a fallback for each crew, so a slip does not becom