close-management-close-status-dashboard
Sub-skill of close-management: Close Status Dashboard (+3).
Best use case
close-management-close-status-dashboard is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of close-management: Close Status Dashboard (+3).
Teams using close-management-close-status-dashboard 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/close-status-dashboard/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How close-management-close-status-dashboard Compares
| Feature / Agent | close-management-close-status-dashboard | 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: Close Status Dashboard (+3).
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
# Close Status Dashboard (+3) ## 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 |
Related Skills
well-production-dashboard
Create interactive well production dashboards with real-time monitoring, verification integration, economic metrics, and multi-format exports. Use for well performance analysis, field aggregation, production forecasting, and API-driven dashboards.
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.
interactive-dashboard-builder
Create self-contained HTML/JavaScript dashboards with Chart.js, filters, and professional styling
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.