Business Capabilities

---
name: business-capabilities
description: Structure cross-functional business decisions and briefs with one primary business lens and at most one supporting lens across strategy, finance, people, operations, revenue/customer experience, and marketing/content. Not for SOP/runbook/RACI authoring, reusable marketing context, channel execution, media generation, regulated advice, or external actions.
---

# Business Capabilities

Use this skill to add a focused business perspective to work that is not mainly
software delivery. It is a decision and briefing aid, not a simulated department
or a source of authority.

## Route the request

1. Read [references/capability-map.md](references/capability-map.md).
2. Select exactly one primary lens. Add one supporting lens only when it answers
   a materially different part of the request.
3. Read only the reference files named for those selected lenses. Do not load the
   whole pack and do not present a parade of fictional roles.
4. Name the selected lens or lenses in one short line, then do the work.

For cross-functional Personal Brand, Marketing & Sales department workflows, route to
[references/dzial-marka-marketing-sprzedaz.md](references/dzial-marka-marketing-sprzedaz.md)
for the end-to-end playbook, specialist skill connections, T2 consent gates, and pilot templates.

## Decision contract

For either an analysis or a deliverable, make these elements explicit:

- the decision, outcome, audience, time horizon, and constraints;
- verified evidence, assumptions, unknowns, and facts that need current sources;
- options and trade-offs, including what would make the recommendation wrong;
- the recommended action or requested artifact;
- owner, next evidence, approvals, and specialist or execution handoffs.

Scale the structure to the request. A small pricing question may need a few
lines; a portfolio decision may need a decision memo. Do not manufacture a long
report merely to satisfy the contract.

## Authority boundaries

- Agent Fleet still selects models and balances quota. Agent Graph still owns
  dependencies and work decomposition. Agent Loop still owns bounded repair
  cycles. This skill supplies a business lens to their tasks; it does not replace
  them.
- Existing specialist skills remain authoritative. Route legal, tax, accounting,
  employment-law, privacy, security, regulated, or jurisdiction-specific claims
  to the relevant specialist and current primary sources.
- Route operational SOPs to `operations-playbook`, marketing foundations to
  `marketing-context`, channel execution to the relevant ads/growth/search skill,
  data changes to `data-governance`, and software delivery to the existing
  engineering stack.
- For image, video, voice, music, or multimedia work, produce a business-ready
  brief and hand production to `video-gen`, `avatar-gen`, `voice-gen`,
  `audio-bed-gen`, the available image capability, or the MiniMax route when
  Agent Fleet selects it. This skill does not generate media.
- Never invent company facts, access, approvals, metrics, legal conclusions, or
  system state. Separate evidence from assumptions and recommendations.
- Drafts do not authorize publication, outreach, hiring, termination, spending,
  contracting, provider changes, production actions, or other external effects.
- Personal Brand, Marketing & Sales department execution strictly enforces the
  T2 consent gates in
  [references/dzial-marka-marketing-sprzedaz.md](references/dzial-marka-marketing-sprzedaz.md):
  research, drafts, and media briefs are autonomous in DEV/TEST, whereas live
  publication, ad spend, live email sends, and pricing commitments require
  mandatory Mateusz consent.

Source adaptation and audit notes are in
[references/provenance.md](references/provenance.md).