iwe-rules-review

Perform a weekly operating rules review by analyzing commits, DayPlans, and Quick Close reports to identify violations and deadweight rules. This process detects cultural drift by evaluating whether existing rules hinder work or are routinely bypassed, producing a structured markdown report.

Identify deadweight rules and formalization candidates by applying a four-question analysis to weekly work artifacts. This process improvement technique synthesizes fleeting notes and reports to determine which rules are missing, ignored, or obstructing work, yielding concrete change proposals.

Yes, you can evaluate cultural health during Week Close by synthesizing Quick Close reports and DayPlans. This workflow inspects operating rule violations and gaps, generating health metrics and a proposed update to the rules registry for approval.

Generate registry change proposals by loading the rules registry, applying a four-question analysis to weekly work data, and identifying missing or bypassed rules. This produces a structured markdown report guiding updates and formalizing new rules.

You need a formal operating rules review during Week Close workflows, after a sprint, or following an organizational change. This process improvement step prevents outdated rules by evaluating cultural health and proposing necessary registry updates.

The weekly rules review requires Quick Close reports, DayPlans, commits, and fleeting notes as input data formats. It loads the operating rules registry and culture elements to establish the source of truth for detecting violations and producing change proposals.