Run a cross-Kit product launch

Coordinate Marketing discovery and launch work with Engineer implementation through explicit artifacts, owners, and approval gates.

Use this workflow when a product or feature launch needs both a tested product change and coordinated marketing execution. The Marketing Kit owns market evidence, positioning, campaign assets, and measurement. The Engineer Kit owns technical scope, implementation, verification, and release readiness.

Define the shared contract

Before invoking a Skill, agree on:

Field	Required decision
Outcome	Product behavior and market result expected
Audience	Segment, user need, and exclusions
Scope	Product change, launch assets, channels, and non-goals
Timing	Target window, dependencies, and readiness deadline
Evidence	Product, customer, market, and technical sources
Measurement	Product and marketing baselines, success metrics, and guardrails
Authority	Who can approve scope, merge, deploy, publish, spend, and change accounts

If any load-bearing field is unknown, record an owner and resolution gate rather than filling it with an assumption.

Phase 1: establish market and launch evidence

Use Marketing ak:marketing-research for sourced, dated evidence.
Add ak:competitor, ak:persona, or ak:pricing-strategy only when the decision requires them.
Use ak:marketing-planning to create the accepted launch brief and measurement plan.
Use Marketing ak:handoff to transfer the product requirements to Engineer.

The handoff must contain the audience problem, accepted claims, desired product behavior, non-goals, asset requirements, target window, metrics, dependencies, open questions, and the owner of each approval.

Phase 2: plan and deliver the product change

Use Engineer ak:brainstorm when the brief still allows multiple technical directions.
Use ak:scout to verify repository constraints and existing behavior.
Use ak:plan to map the accepted product outcome to phases, risks, tests, release gates, and observable stop conditions.
Use ak:cook to implement the approved plan.
Use ak:test and ak:code-review to verify behavior and production risk.
Use Engineer ak:handoff to return release evidence to Marketing.

Engineer must not silently change the audience claim, launch promise, metric, or timing. Return conflicts to the shared contract and have the responsible owner decide.

The return handoff includes implemented behavior, known limitations, user-facing changes, screenshots or demos, test evidence, rollout constraints, rollback notes, release status, and any claim the implementation no longer supports.

Phase 3: prepare launch execution

Use Marketing ak:launch-strategy to reconcile the accepted brief with actual release evidence.
Use ak:campaign to prepare the campaign plan and ak:content-marketing or ak:write for scoped content.
Route channel-specific drafts through the relevant Marketing Skill.
Review claims against the Engineer handoff before publication.
Obtain explicit approval for provider access, publication, spend, or production changes.

No launch asset should promise behavior that is absent, gated, deferred, or limited in the release evidence.

Phase 4: launch and learn

After authorized release and publication, use ak:analytics to compare product and marketing signals with their baselines. Record data quality, attribution limits, guardrails, and the decision rule before interpreting results.

Route technical regressions through the software delivery workflow. Route funnel or message opportunities through the marketing growth workflow. Material scope or audience changes return to the shared contract and require a new decision.

Completion checklist

The cross-Kit workflow is complete when:

product behavior and launch claims match;
required tests, reviews, and readiness gates passed;
launch artifacts and measurement definitions were approved;
deploy, publish, spend, and provider actions have named owners;
open risks, rollback conditions, and post-launch decisions are recorded.