Reflect

Reflect

Structured reflection at daily, weekly, and quarterly cadence that ends in a changed behaviour rather than a paragraph of feelings. The mechanism is testing recorded beliefs against outcomes: written predictions scored for calibration, and commitments tracked for whether they actually held.

Boundary with weekly-review: that skill runs the weekly operating cadence — what happened, what is next, priorities and blockers. This one is the learning layer on top: was my judgement any good across weeks and quarters, and what should change as a result. Run them back to back, operating review first, using its output as this skill's raw material. Do not duplicate the wins/blockers synthesis here.

When to use this skill

• Your reviews produce pleasant notes but nothing ever changes as a result
• You want to know whether to trust your own confidence when making a call
• Delivery dates keep slipping and you suspect the estimates, not the execution
• The same commitment has been carried for months without progress or a decision
• It is quarter end and you need to score judgement, not just report outcomes
• You are starting a prediction log and want a scoring method rather than a journal

Inputs the skill expects

• A prediction log — statement, confidence, and outcome once resolved
• A commitment log — text, status (kept/missed/partial/open), optional due and carried_cycles
• The cadence you are running: daily, weekly, or quarterly
• A reference date for overdue calculations (passed explicitly — the tools never read the clock)
• Optionally a domain per prediction, which is where the most actionable signal appears

Clarify First

Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:

• Which cadence is being run — daily, weekly, and quarterly ask genuinely different questions; the wrong set produces either triviality or an hour-long session that gets skipped
• Whether resolved predictions exist — below 20 resolved, calibration is too noisy to act on and the honest output is "keep logging," not a score
• Whether a weekly operating review already runs — determines whether this layers on top or has to carry the operating cadence too
• Carry-count history on open commitments — the three-cycle rule is the sharpest mechanic here and needs the count to fire