Skip to content
cccskills
FreePublished on GitHub

codexkit-finance-close-coordinator

Organize month-end or quarter-end close blockers, reconciliations, owners, and evidence gaps into a routine control pack. Use when the work is finance close coordination and issue tracking. Do not use for accounting judgment, policy interpretation, or final technical accounting conclusions.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md2.8 KB
  • agents/openai.yaml179 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Finance Close Coordinator

Purpose

Keep close operations moving with a short, decision-ready issue view.

When to use

  • close has many open issues and no clean tracker
  • controllers or FP&A need one summary of blockers and owners
  • evidence or reconciliations are arriving in fragments

When not to use

  • the user needs accounting analysis under IFRS, GAAP, or tax rules
  • the task is a variance story, not close coordination

Inputs

  • close issue list or status notes
  • reconciliations, evidence status, or owner updates
  • period and escalation timing

Procedure

  1. Normalize each open issue into owner, status, risk, and due date.
  2. Separate evidence gaps from true close blockers.
  3. Flag items that could miss the period close.
  4. Group related issues under one line when possible.
  5. End with escalation items and next owner actions.

Output

  • close blocker summary
  • evidence and reconciliation gaps
  • owner action list
  • escalations for the period

Definition of done

  • open close issues are visible in one read
  • owners and deadlines are clear
  • routine reminders are separated from real escalation risk

Examples

  • "Summarize these close notes into blockers, gaps, and owners."
  • "Turn this close tracker into a morning control pack."

Quality Criteria

  • Steps are executable in sequence without external context
  • Decision points have clear if/then branching
  • Rollback or abort procedures are documented for risky steps
  • Expected duration or time-per-step is estimated

Verification (4C)

CheckQuestion
CorrectnessDo the steps execute correctly in the order specified?
CompletenessAre decision points, error handling, and escalation paths all documented?
Context-fitCould someone with the right access but no prior context complete this runbook?
ConsequenceIf Step N fails and the operator skips to Step N+1, what breaks?

Edge Cases

  • Steps require access the operator doesn't have — Document exact access requirements upfront. Include escalation contact for emergency access.
  • Environment differs from documented state — Add a pre-flight check as Step 0 to verify prerequisites before starting.
  • Runbook is triggered during off-hours — Document who to contact and which steps can be safely deferred to business hours.

Changelog

  • v1.0.0 — Initial release

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

See all skills by hoavdc

Report a problem with this skill