close-management-typical-5-day-close-calendar
Sub-skill of close-management: Typical 5-Day Close Calendar (+1).
Best use case
close-management-typical-5-day-close-calendar is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of close-management: Typical 5-Day Close Calendar (+1).
Teams using close-management-typical-5-day-close-calendar should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/typical-5-day-close-calendar/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How close-management-typical-5-day-close-calendar Compares
| Feature / Agent | close-management-typical-5-day-close-calendar | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of close-management: Typical 5-Day Close Calendar (+1).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Typical 5-Day Close Calendar (+1) ## Typical 5-Day Close Calendar | Day | Key Activities | Responsible | |-----|---------------|-------------| | **T+1** | Cash entries, payroll, AP accruals, depreciation, prepaid amortization, intercompany posting | Staff accountants, payroll | | **T+2** | Revenue recognition, remaining accruals, subledger reconciliations (AR, AP, FA), FX revaluation | Revenue accountant, AP/AR, treasury | | **T+3** | Balance sheet reconciliations, intercompany reconciliation, eliminations, preliminary trial balance, preliminary flux | Accounting team, consolidation | | **T+4** | Tax provision, equity roll-forward, draft financial statements, detailed flux analysis, management review | Tax, controller, FP&A | | **T+5** | Final adjustments, hard close, period lock, reporting package distribution, forecast update, retrospective | Controller, FP&A, finance leadership | ## Accelerated Close (3-Day Target) For organizations targeting a faster close: | Day | Key Activities | |-----|---------------| | **T+1** | All JEs posted (automated + manual), all subledger reconciliations, bank reconciliation, intercompany reconciliation, preliminary trial balance | | **T+2** | All balance sheet reconciliations, tax provision, consolidation, draft financial statements, flux analysis, management review | | **T+3** | Final adjustments, hard close, reporting package, forecast update | **Prerequisites for a 3-day close:** - Automated recurring journal entries (depreciation, amortization, standard accruals) - Continuous reconciliation during the month (not all at month-end) - Automated intercompany elimination - Pre-close activities completed before month-end (cut-off, accrual estimates) - Empowered team with clear ownership and minimal handoffs - Real-time or near-real-time sub-system integration
Related Skills
flywheel-closeout
Use this at the end of substantial repo or agent waves to convert evidence-backed lessons into proposed durable assets: skills, scripts, rules/checks, prompt templates, docs, or issues. Always use it when the user mentions flywheel, wave closeout, repo ecosystem learning, durable asset promotion, or learning-to-tools.
overnight-verify-close-and-blocker-conversion
Use overnight Codex lanes to clear stale-open GitHub issues by verification-first closure, and convert blocked PR-repair attempts into dedicated blocker issues instead of speculative edits.
orcawave-orcaflex-semantic-proof-wave-closeout
Close out an OrcaWave/OrcaFlex semantic-proof wave after a PR merges, split unrelated CI blockers, and seed the next semantic-proof issue wave without duplicating existing issues.
overnight-verify-close-batch
Build overnight parallel batches that close stale-open GitHub issues by proving landed work already satisfies the issue, instead of wasting implementation lanes on redoing completed work.
cron-job-management
Patterns for creating, testing, debugging, and maintaining cron-driven automation in workspace-hub, including log strategy, failure analysis, and safe git-aware job design.
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
github-issue-closeout-race-safe
Close GitHub issues without losing the evidence comment when multiple agents or races may close the issue concurrently.
doc-audit-and-close-workflow
A repeatable workflow for executing a batch of documentation, audit, or planning tasks. For each task, it audits the current state, creates a plan/report, commits the result, and closes the corresponding GitHub issue. The process is designed to be idempotent.
data-management
Comprehensive DataFrame loading, filtering, transformation, and data pipeline management from Excel, CSV, and multiple sources with YAML-driven configuration.
closed-issue-plan-refile-loop
Reopen and re-drive a previously closed GitHub plan issue after review/governance blockers are fixed, without prematurely restoring approval state.
task-management
Simple task management using a shared TASKS.md file for tracking commitments and action items.
memory-management
Two-tier memory system for decoding workplace shorthand, acronyms, nicknames, and internal language.