close-status

<!-- Generated from `.claude/skills/_available/finance/close-status/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. --> ## When to use Use when a finance or leadership user asks where a specified close period stands, what evidence supports completion, what is blocked, or which dependencies determine the sequence. Confirm the period, close deadline, and checklist scope before counting. Do not use this skill to post journal entries, change the close checklist, certify completion, assign owners, or approve an accounting treatment. Not for budget-versus-actual explanation, forecasting, or audit sign-off. ## Inputs and source discipline 1. Identify the period, fiscal calendar/timezone, checklist version, and deadline. Use the controller- or process-owner-approved **authoritative checklist** as the denominator source; record its source, source date, date checked, and `as-of` date. Never invent a deadline or silently substitute a remembered checklist. 2. For each checklist row, capture its stable label, required evidence, current evidence source, source date, date checked, named owner only if explicitly recorded, and confidence. Prefer system/close evidence and dated owner confirmation over meeting notes; use notes to locate evidence, not to override it. Preserve contradictory sources. 3. Keep the checklist's scope and exclusions explicit. If the authoritative checklist is missing, partial, or stale, report the denominator as unknown rather t...