Growth Operations

Growth Operations & Infrastructure

Reuse Growth Context

At the start, read .agents/growth-context.md when it exists. Reuse only product, customer, market, outcome, constraint, evidence, and routing fields whose scope, definition, source, and date remain compatible; state what is reused and surface conflicts or staleness before asking for decision-changing gaps. The file grants no system access or execution authority, and this Skill must not silently rewrite the primary diagnosis.

Integrated Capabilities

This Skill consolidates adjacent workflows behind one trigger. Use the main workflow for core requests. When a request matches a module below, read that module before executing it:

• [Growth Capacity Planning](references/modules/growth-capacity-planning/SKILL.md)
• [Growth Investment Case](references/modules/growth-investment-case/SKILL.md)
• [Growth Budget Allocation](references/modules/growth-budget-allocation/SKILL.md)
• [Growth Initiative Planning](references/modules/growth-initiative-planning/SKILL.md)
• [Growth Operating Review](references/modules/growth-operating-review/SKILL.md)
• [Growth Decision Record](references/modules/growth-decision-record/SKILL.md)
• [Growth Risk Management](references/modules/growth-risk-management/SKILL.md)
• [Growth Learning System](references/modules/growth-learning-system/SKILL.md)
• [Growth Postmortem](references/modules/growth-postmortem/SKILL.md)
• [Growth Change Management](references/modules/growth-change-management/SKILL.md)
• [Growth Infrastructure Assessment](references/modules/growth-infrastructure-assessment/SKILL.md)
• [RevOps Audit](references/modules/revops-audit/SKILL.md)
• [Growth Organization Design](references/modules/growth-organization-design/SKILL.md)
• [Experiment Program Management](references/modules/experiment-program-management/SKILL.md)

Turn annual, quarterly, or rolling planning into an ordered decision system. Reconcile supplied specialist artifacts, compatible evidence, constrained resources, approval states, calendars, and review rules into one plan of record. A planning cycle coordinates decisions; it does not recreate every analysis, force ambition into a forecast, approve resources, or execute work.

Read [planning-cycle-contract.md](references/planning-cycle-contract.md) before accepting the cycle, cadence, horizon, owner, artifact, state, evidence cutoff, decision forum, or approval. Read [artifact-compatibility-and-reconciliation.md](references/artifact-compatibility-and-reconciliation.md) before combining metrics, baselines, targets, forecasts, opportunities, scenarios, portfolios, markets, currencies, or versions. Read [decisions-calendar-capacity-and-budget.md](references/decisions-calendar-capacity-and-budget.md) before ordering decisions, scheduling gates, reconciling initiatives, or allocating capacity and budget. Read [governance-refresh-and-market-transfer.md](references/governance-refresh-and-market-transfer.md) before approving, refreshing, transferring, operationalizing, or using personal data. Read [output-contract.md](references/output-contract.md) before delivery. Use [playbook-sources.md](references/playbook-sources.md) for the pinned Growth Playbook basis.

Select One Mode

| Mode | Use | | --- | --- | | build | Create one annual, quarterly, or rolling planning cycle from supplied versioned artifacts, evidence, decisions, and resource boundaries | | audit | Inspect an existing cycle for completeness, compatibility, feasibility, decision lineage, approval integrity, and governance | | refresh | Version a cycle after material evidence, strategy, metric, target, forecast, portfolio, capacity, budget, risk, or market change |

Name one cadence and primary mode. Use one cycle state: draft, reconciling, decision-ready, blocked, approved, active, superseded, cancelled, or expired. State is not evidence of approval, authorization, execution, completion, or business impact.

Route arena, value, mechanism, portfolio, and exclusion choices to growth-strategy; measurement, target, forecast, tracking, attribution, and experiment design to growth-measurement; opportunity ranges to growth-model-design; and planning, allocation, reviews, decisions, learning, infrastructure, organization, RevOps, and experiment-program work to the matching growth-operations module. This Skill owns orchestration and cross-artifact consistency, not those specialist outputs.

Freeze The Cycle Contract

Record cycle ID and version, mode and state, cadence, horizon and periods, accountable planning owner, artifact owners, decision owners, forums, required approvers, scope and exclusions, product and business model, customers and participant roles, markets and locales, strategy and metric versions, evidence cutoff, planning start, decision dates, effective period, review and refresh dates, expiry, superseded cycle, and external-action boundary.

Use exactly verified, inferred, unavailable, or not applicable for evidence-bearing claims. Keep actual, baseline, benchmark, reported signal, estimate, target, opportunity, forecast, scenario, plan, budget, recommendation, decision, approval, authorization, action, completion, verification, causal estimate, and business result separate. Preserve source, owner, date, version, entity, definition, segment, market, period, cohort, maturity, currency, accounting basis, limitations, contradictions, revisions, and lineage.

Do not invent strategy, customers, baselines, targets, forecasts, opportunities, effects, portfolio choices, capacity, budgets, dates, probabilities, confidence, approvals, implementation, or results. Missing material inputs create named prerequisite decisions and handoffs; they do not become planning assumptions.

Build The Artifact Manifest

Inventory the current and prior strategy, metric system, baselines and actuals, targets, forecasts, opportunities, investment cases, organization and decision rights, initiative portfolio, initiative plans, operating obligations, risks, prior reviews, and external commitments as applicable. For each record ID, version, owner, state, source, as-of and cutoff, effective period, scope, dependencies, approval state, superseded version, and decision served.

Distinguish required, conditional, optional, unavailable, superseded, and not-applicable inputs. Do not choose the most favorable value across versions or call a presentation current merely because it is recent. Identify which downstream decisions are invalid, blocked, or must be refreshed when lineage conflicts.

Reconcile Compatibility Before Aggregation

Confirm entity, eligibility, identity, customer and participant role, product, market, segment, motion, channel, metric definition, numerator, denominator, window, cohort, maturity, period, calendar, currency, conversion date, accounting basis, source, cutoff, and version before combining values.

Use separate views when units or decisions differ. Reconcile parent and child outcomes only with mutually exclusive, collectively exhaustive partitions or explicit overlap and residual. Keep attributed, causal, forecast, scenario, opportunity, planned, approved, and realized value separate. Do not add the same customer, revenue, contribution, or effect across lifecycle stages, functions, channels, experiments, or initiatives.

Construct The Decision Architecture

For each planning decision record the question, alternatives, source artifacts, evidence and contradiction, owner, contributors, required approver, prerequisites, downstream artifacts, reversibility, risk, earliest valid date, latest useful date, expiry, escalation, and possible select, preserve, revise, defer, reject, stop, or route outcome.

Build the dependency graph before the calendar. Put strategy and compatible definitions before targets and portfolio commitments; evidence and opportunity before material investment; resource and approval decisions before initiative readiness; and maturity before outcome review. A ceremony date cannot make a decision valid. If lead time or maturity is unavailable, return a provisional order and evidence request rather than a fictional date.

Reconcile Portfolio, Capacity, And Budget

Use the selected strategy and supplied portfolio decision. Do not make every initiative top priority or fund all work equally. For every commitment preserve outcome, class, evidence, owner, dependencies, capacity, budget boundary, customer protections, opportunity cost, maturity, approval state, initiative plan, graduation, cap, stop, fallback, expiry, and review.

Deduplicate shared outcomes and expose cannibalization, interaction, concentration, shared dependencies, and work displaced. Do not add opportunity ranges, forecast upside, attributed value, experiment estimates, and initiative claims into one impact total.

Define compatible capacity units, skills, owners, periods, calendars, allocation, contention, operating reserve, and evidence state. Define budget owner, currency, accounting basis, cash timing, fixed and variable boundaries, requested, approved and contingent amounts, shared costs, and uncertainty. Requested headcount or spend is not available capacity. Do not double-book people, systems, vendors, money, inventory, or leadership attention.

Reserve explicit capacity and budget for existing-customer value, support, reliability, accessibility, privacy, security, fraud, compliance, data quality, localization, incidents, maintenance, migrations, communication, decommissioning, and residual obligations where applicable. Growth upside cannot buy off noncompensable harm.

Build A Decision Calendar, Not A Ceremony Calendar

Schedule evidence availability, maturity, decisions, approvals, initiative readiness, operating reviews, and refresh triggers. For each gate record owner, prerequisites, eligible scope, artifact or operating state, metric contract, evidence rule, guardrails, earliest valid date, latest useful date, decision, expiry, and escalation.

Match cadence to evidence. Weekly forums can handle fresh operating signals and blockers; monthly forums can reconcile mature lifecycle, economic, experiment, forecast, and initiative evidence; quarterly or annual forums can revisit strategy, portfolio, capacity, and structural assumptions. Immature or unobserved evidence is unavailable, not zero.

Use coherent conditional scenarios only when uncertainty changes a decision. Preserve assumptions, evidence, contradictions, sensitivities, triggers, robust commitments, contingencies, reversible options, irreversible commitments, responses, owners, and review dates. Do not invent probabilities, average incompatible scenarios, or call an upside scenario the plan or forecast.

Establish The Plan Of Record

Record selected, preserved, deferred, rejected, stopped, routed, and unresolved decisions; accepted commitments; excluded work; capacity and budget boundaries; approval states; downstream initiative versions; review cadence; refresh rules; and residual obligations in one versioned record.

Mark decision-ready only when material artifacts are compatible, decisions and alternatives are explicit, required capacity and budget are reconciled, dependencies and maturity fit the calendar, owners and approvers are named, and unresolved items cannot invalidate the proposed plan. Mark approved or active only from attributable supplied evidence. A deck, comment, owner name, budget proposal, meeting, traffic-light status, or percent complete is insufficient.

Audit Or Refresh Without Rewriting History

In audit, inspect artifact lineage, compatibility, decision sequence, target and forecast independence, outcome reconciliation, portfolio choices, capacity and budget feasibility, operating obligations, evidence maturity, approval states, version history, and external-action controls. Surface stale, contradictory, ownerless, blocked, superseded, unapproved, and expired items by the decision affected.

In refresh, preserve the previous cycle, actuals, forecasts, targets, assumptions, decisions, commitments, misses, and evidence available at the time. Record the trigger and new cutoff, refresh only affected specialist artifacts, rebuild compatibility and downstream effects, and choose what to preserve, revise, defer, stop, cancel, supersede, or escalate. Do not backdate assumptions, erase misses, relabel failure, or make the new plan appear inevitable.

Handle Markets, People, And Actions

Treat every market as a new evidence and operating boundary. Revalidate customer value, product, channels, platforms, metrics, baselines, targets, forecasts, opportunities, prices, costs, capacity, budget, dependencies, calendars, support, risks, owners, approvals, and rollback. Translation and currency conversion do not validate transfer.

For China, distinguish market, legal entity, language, locale, product, platform, app distribution, identity, payment, invoice, data, consent, content, advertising, holidays, support, staffing, lead times, and locally accountable review. Use current direct sources and local expertise. Do not make legal, tax, regulatory, provider-availability, accounting, approval, or performance conclusions.

Use aggregate, redacted, pseudonymous, minimum-necessary evidence. Do not expose credentials, private messages, payment details, health or financial data, protected traits, precise locations, raw identities, employee reviews, compensation, ratings, or full histories when bounded evidence suffices. Do not rank individuals for consequential pricing, service, employment, credit, insurance, health, housing, or similar decisions.

Deliver In Order

Follow [output-contract.md](references/output-contract.md). Deliver the cycle contract; artifact and evidence manifest; compatibility and reconciliation; decision architecture; portfolio, capacity, budget, maintenance, and scenarios; decision calendar; plan of record and version history; risks, refresh, markets, privacy, handoffs, pinned sources, external actions, and completion record.

External-Action Boundary

Create and read local artifacts only. Do not access authenticated planning, finance, HR, analytics, data, CRM, billing, advertising, experiment, product, cloud, support, procurement, project, or communication systems; export or join personal data; approve targets, budgets, staffing, organization, prices, products, permissions, contracts, or records; assign work; launch initiatives; contact people; publish; send; spend; procure; deploy; or claim adoption, implementation, completion, or business results without separate task-level authorization and controls.

Keep One Output Language

Use the requested output language consistently across headings, prose, tables, labels, and actions. When no language is explicit, match the user's dominant language; market, locale, platform, and source language do not override it.

For Simplified Chinese, write natural Simplified Chinese and translate ordinary business or analytical jargon instead of embedding English words such as owner, brief, listing, cohort, baseline, benchmark, guardrail, gate, finding, roadmap, workflow, and handoff. Keep only proper names, standard acronyms after a Chinese first-use definition, machine tokens or IDs, code, formulas, filenames, URLs, and exact quotations where necessary.

For English, use idiomatic English and do not add Chinese glosses except for proper nouns or quoted source text. Use multiple languages only when explicitly requested, and keep each version in a separate labeled section rather than mixing languages within sentences or tables. Do not alternate languages for emphasis or perceived expertise.

Completion Gate

Confirm the output passes [output-contract.md](references/output-contract.md); artifacts and versions are explicit and compatible; targets remain distinct from forecasts and evidence; outcomes and res

…

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: krillinai
• Source: krillinai/growth-skills
• License: MIT
• Homepage: www.clawee.ai/

Install and usage instructions live in the source repository linked above.