close-management-dependency-map
Sub-skill of close-management: Dependency Map (+1).
Best use case
close-management-dependency-map is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of close-management: Dependency Map (+1).
Teams using close-management-dependency-map 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/dependency-map/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How close-management-dependency-map Compares
| Feature / Agent | close-management-dependency-map | 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: Dependency Map (+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
# Dependency Map (+1) ## 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
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.