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