close-management

anthropics/knowledge-work-plugins · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill close-management
0 commentsdiscussion
summary

Important: This skill assists with close management workflows but does not provide financial advice. All close activities should be reviewed by qualified financial professionals.

skill.md

Close Management

Important: This skill assists with close management workflows but does not provide financial advice. All close activities should be reviewed by qualified financial professionals.

Month-end close checklist, task sequencing and dependencies, status tracking, and common close activities organized by day.

Month-End Close Checklist

Pre-Close (Last 2-3 Business Days of the Month)

  • Send close calendar and deadline reminders to all contributors
  • Confirm cut-off procedures with AP, AR, payroll, and treasury
  • Verify all sub-systems are processing normally (ERP, payroll, banking)
  • Complete preliminary bank reconciliation (all but last-day activity)
  • Review open purchase orders for potential accrual needs
  • Confirm payroll processing schedule aligns with close timeline
  • Collect information for any known unusual transactions

Close Day 1 (T+1: First Business Day After Month-End)

  • Confirm all sub-ledger modules have completed period-end processing
  • Run AP accruals for goods/services received but not invoiced
  • Post payroll entries and payroll accrual (if pay period straddles month-end)
  • Record cash receipts and disbursements through month-end
  • Post intercompany transactions and confirm with counterparties
  • Complete bank reconciliation with final bank statement
  • Run fixed asset depreciation
  • Post prepaid expense amortization

Close Day 2 (T+2)

  • Complete revenue recognition entries and deferred revenue adjustments
  • Post all remaining accrual journal entries
  • Complete AR subledger reconciliation
  • Complete AP subledger reconciliation
  • Record inventory adjustments (if applicable)
  • Post FX revaluation entries for foreign currency balances
  • Begin balance sheet account reconciliations

Close Day 3 (T+3)

  • Complete all balance sheet reconciliations
  • Post any adjusting journal entries identified during reconciliation
  • Complete intercompany reconciliation and elimination entries
  • Run preliminary trial balance and income statement
  • Perform preliminary flux analysis on income statement
  • Investigate and resolve material variances

Close Day 4 (T+4)

  • Post tax provision entries (income tax, sales tax, property tax)
  • Complete equity roll-forward (stock compensation, treasury stock)
  • Finalize all journal entries — soft close
  • Generate draft financial statements (P&L, BS, CF)
  • Perform detailed flux analysis and prepare variance explanations
  • Management review of financial statements and key metrics

Close Day 5 (T+5)

  • Post any final adjustments from management review
  • Finalize financial statements — hard close
  • Lock the period in the ERP/GL system
  • Distribute financial reporting package to stakeholders
  • Update forecasts/projections based on actual results
  • Conduct close retrospective — identify process improvements

Task Sequencing and Dependencies

Dependency Map

Tasks are organized by what must complete before the next task can begin:

LEVEL 1 (No dependencies — can start immediately at T+1):
├── Cash receipts/disbursements recording
├── Bank statement retrieval
├── Payroll processing/accrual
├── Fixed asset depreciation run
├── Prepaid amortization
├── AP accrual preparation
└── Intercompany transaction posting

LEVEL 2 (Depends on Level 1 completion):
├── Bank reconciliation (needs: cash entries + bank statement)
├── Revenue recognition (needs: billing/delivery data finalized)
├── AR subledger reconciliation (needs: all revenue/cash entries)
├── AP subledger reconciliation (needs: all AP entries/accruals)
├── FX revaluation (needs: all foreign currency entries posted)
└── Remaining accrual JEs (needs: review of all source data)

LEVEL 3 (Depends on Level 2 completion):
├── All balance sheet reconciliations (needs: all JEs posted)
├── Intercompany reconciliation (needs: both sides posted)
├── Adjusting entries from reconciliations
└── Preliminary trial balance

LEVEL 4 (Depends on Level 3 completion):
├── Tax provision (needs: pre-tax income finalized)
├── Equity roll-forward
├── Consolidation and eliminations
├── Draft financial statements
└── Preliminary flux analysis

LEVEL 5 (Depends on Level 4 completion):
├── Management review
├── Final adjustments
├── Hard close / period lock
├── Financial reporting package
└── Forecast updates

Critical Path

The critical path determines the minimum close duration. Typical critical path:

Cash/AP/AR entries → Subledger reconciliations → Balance sheet recs →
  Tax provision → Draft financials → Management review → Hard close

To shorten the close:

  • Automate Level 1 entries (depreciation, prepaid amortization, standard accruals)
  • Pre-reconcile accounts during the month (continuous reconciliation)
  • Parallel-process independent reconciliations
  • Set clear deadlines with consequences for late submissions
  • Use standardized templates to reduce reconciliation prep time

Status Tracking and Reporting

Close Status Dashboard

Track each close task with the following attributes:

Task Owner Deadline Status Blocker Notes
[Task name] [Person/role] [Day T+N] Not Started / In Progress / Complete / Blocked [If blocked, what's blocking] [Any notes]

Status Definitions

  • Not Started: Task has not yet begun (may be waiting on dependencies)
  • In Progress: Task is actively being worked on
  • Complete: Task is finished and has been reviewed/approved
  • Blocked: Task cannot proceed due to a dependency, missing data, or issue
  • At Risk: Task is in progress but may not meet its deadline

Daily Close Status Meeting (Recommended)

During the close period, hold a brief (15-minute) daily standup:

  1. Review status board: Walk through open tasks, flag any that are behind
  2. Identify blockers: Surface any issues preventing task completion
  3. Reassign or escalate: Adjust ownership or escalate blockers to resolve quickly
  4. Update timeline: If any tasks are at risk, assess impact on overall close timeline

Close Metrics to Track Over Time

Metric Definition Target
Close duration Business days from period end to hard close Reduce over time
# of adjusting entries after soft close Entries posted during management review Minimize
# of late tasks Tasks completed after their deadline Zero
# of reconciliation exceptions Reconciling items requiring investigation Reduce over time
# of restatements / corrections Errors found after close Zero

Common Close Activities by Day

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

Close Process Improvement

Common Bottlenecks and Solutions

Bottleneck Root Cause Solution
Late AP accruals Waiting for department spend confirmation Implement continuous accrual estimation; set cut-off deadlines
Manual journal entries Recurring entries prepared manually each month Automate standard recurring entries in the ERP
Slow reconciliations Starting from scratch each month Implement continuous/rolling reconciliation
Intercompany delays Waiting for counterparty confirmation Automate intercompany matching; set stricter deadlines
Management review changes Large adjustments found during review Improve preliminary review process; empower team to catch issues earlier
Missing supporting documents Scrambling for documentation at close Maintain documentation throughout the month

Close Retrospective Questions

After each close, ask:

  1. What went well this close that we should continue?
  2. What took longer than expected and why?
  3. What blockers did we encounter and how can we prevent them?
  4. Were there any surprises in the financial results we should have caught earlier?
  5. What can we automate or streamline for next month?
how to use close-management

How to use close-management on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add close-management
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill close-management

The skills CLI fetches close-management from GitHub repository anthropics/knowledge-work-plugins and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/close-management

Reload or restart Cursor to activate close-management. Access the skill through slash commands (e.g., /close-management) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.530 reviews
  • Sofia Jackson· Dec 28, 2024

    Useful defaults in close-management — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Liam Kim· Dec 20, 2024

    We added close-management from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Rahul Santra· Nov 27, 2024

    Useful defaults in close-management — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Liam Rao· Nov 11, 2024

    close-management fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Pratham Ware· Oct 18, 2024

    Registry listing for close-management matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Isabella Martin· Oct 2, 2024

    close-management has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Yash Thakker· Sep 21, 2024

    Keeps context tight: close-management is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Sofia Sanchez· Sep 17, 2024

    close-management is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Dhruvi Jain· Aug 12, 2024

    I recommend close-management for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Kabir Shah· Aug 8, 2024

    Solid pick for teams standardizing on skills: close-management is focused, and the summary matches what you get after install.

showing 1-10 of 30

1 / 3