self-improving-business

Log business administration issues and policy gaps to .learnings with ownership.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/jose-compu/self-improving-skills --skill self-improving-business
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-improving-business
Source: https://github.com/jose-compu/self-improving-skills/tree/main/self-improving-business
Command: npx skills add https://github.com/jose-compu/self-improving-skills --skill self-improving-business

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Captures business administration issues, policy gaps, KPI misalignment, decision delays, handoff failures, and stakeholder misalignment to improve operational decision quality. Use when: (1) approval or execution bottlenecks appear, (2) KPI definitions conflict across teams, (3) process governance is inconsistent, (4) SLA commitments are missed or trending late, (5) budget variance requires triage, (6) vendor or cross-team handoff breaks, (7) policy documentation drifts from actual practice.

Core Features & Use Cases

  • Structured logging of operational issues, governance gaps, and KPI risks to persistent artifacts.
  • Guidance for triage, escalation, and promotion to playbooks, KPI registries, and RACI matrices.
  • Use Case: When a recurring approval bottleneck emerges, log the pattern and extract a reusable governance pattern.

Quick Start

Create and log your first entry in the .learnings directory to capture an ongoing governance issue.

Frequently Asked Questions about self-improving-business

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log governance gaps and policy drift in cross-functional workflows?

To log governance gaps and policy drift, you record operational issues in a persistent `.learnings` artifact with clear ownership. This structured logging captures approval bottlenecks and policy deviations to improve operational decision quality across cross-functional workflows.

What is the best way to resolve KPI misalignment and disputes across teams?

Resolving KPI misalignment involves capturing conflicting metric definitions and execution issues into structured logs. You can then extract these captured findings into a centralized KPI registry to standardize definitions and align stakeholders across teams.

How do I triage SLA misses and budget variance when approval bottlenecks occur?

Triage SLA misses and budget variance by logging the approval bottlenecks with clear ownership and requiring human approval for high-impact decisions. This safety-first approach escalates critical governance issues and tracks resolution accountability.

Can I use this approach for vendor handoff failures and RACI matrix extraction?

Yes, you can log vendor handoff failures and stakeholder misalignment to map accountability gaps. These structured logs can be directly extracted into RACI matrices and operational playbooks to prevent future cross-team execution breakdowns.

When do I need structured logging for business administration issues?

You need structured logging for business administration issues when approval bottlenecks emerge, process governance is inconsistent, or policy documentation drifts from actual practice. It enforces safety by requiring human approval for high-impact operational decisions.

Does this workflow require dependencies to capture decision delays and handoff failures?

No dependencies are required to capture decision delays and handoff failures. You can start immediately by creating and logging your first entry in the `.learnings` directory to document ongoing governance issues and stakeholder misalignment.