OpenParable
Skip to content
← Back to skills

Close Status

Productivity
close-status

Close Status is an Agent Skill for productivity published in the davekilleen/Dex repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Month-end close checklist and blockers

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/davekilleen/Dex/blob/HEAD/.claude/skills/_available/finance/close-status/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/close-status, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Purpose

Track month-end close progress, identify blockers, and ensure timely completion.

Usage

  • /close-status - Current period close status
  • /close-status [month] - Specific month (e.g., "January")

Steps

  1. Read close checklist (from finance files or standard close process)
  2. Check status of each item:
    • Complete
    • In progress
    • Blocked
    • Not started
  3. Search recent meetings for close-related discussions and blockers
  4. Identify dependencies on other teams
  5. Calculate days remaining until close deadline
  6. Generate status dashboard with:
    • Checklist completion %
    • Blockers with owners
    • Timeline to completion
    • Critical path items

Output Format

# 📊 Close Status: [Month Year]

**Close deadline:** [Date]
**Days remaining:** [X]
**Completion:** [X]%

## Checklist Status
- [x] [Item 1] - Complete
- [ ] [Item 2] - In progress (Owner: [Name])
- [ ] [Item 3] - **BLOCKED** - [Reason]

## Blockers
1. [Blocker] - Owner: [Name] - Action: [What's needed]

## Dependencies
- Waiting on [Team/Person] for [Item]

## Critical Path
Items that must complete before others can start:
1. [Item] - [Status]