Establish marketing project context with ak:init

Use ak:init when a new or existing project needs an agreed marketing brief, brand constraints, audience context, objectives, and a clear documentation home. The Skill inspects what the project already treats as authoritative, interviews you for missing information, and then proposes the smallest useful documentation update.

Choose ak:init for project onboarding

Use ak:init when

• You are starting a marketing project and need a structured brief.
• An existing repository has scattered or outdated marketing context that must be checked with a stakeholder.
• Future sessions need durable product, audience, brand, objective, timeline, and resource context.
• You want the project’s current documentation structure preserved instead of receiving a fixed folder template.

Choose another workflow when

• The project already has approved context and you only need a campaign or deliverable. Use the relevant planning or creation Skill.
• You need a read-only repository summary. Use ak:watzup; it reports status without establishing marketing authority.
• You need to preserve the current conversation for another session. Use ak:handoff.
• You only need folder-local agent conventions. Use ak:folder-context.

Prepare the project and evidence

Before starting:

• Complete Onboarding and install Marketing Kit for the runtime and scope you are using.
• Open the project whose documentation you are willing to update.
• Identify the people allowed to confirm product, brand, legal, audience, budget, and timeline information.
• Gather approved source material such as the root README, current strategy, brand guidance, product assets, customer evidence, and public website URLs.
• Remove credentials, private customer data, and personal data that the brief does not require.

The Skill may inspect repository instructions, documentation navigation, manifests, assets, and relevant project files. It may also read a website or other supplied external source when the current runtime has an appropriate tool and you approve that network access.

Invoke the Skill

Read Runtime adapters before assuming that interactive prompts, Agents, browser tools, or Hooks behave identically.

/ak:init "Onboard this existing product repository for launch planning. Reuse current documentation, treat supplied interviews as private, do not initialize Git, create a remote, commit, publish, or spend"

/ak:init "Onboard this existing product repository for launch planning. Reuse current documentation, treat supplied interviews as private, do not initialize Git, create a remote, commit, publish, or spend"

$ak:init "Onboard this existing product repository for launch planning. Reuse current documentation, treat supplied interviews as private, do not initialize Git, create a remote, commit, publish, or spend"

State the authority boundary in the initial prompt. In particular, distinguish permission to read and draft from permission to initialize a repository, create a hosted remote, write project documentation, or commit the result.

Understand the stages

1. Check repository state. The Skill runs git status. If the directory is not a Git repository, it asks before git init.
2. Evaluate existing context. Research lanes examine product or service evidence, existing marketing assets, public presence, and competitive context. The Skill summarizes findings and asks whether they remain current.
3. Run the brief interview. It progressively gathers basic information, products and services, objectives, audience, competitors, brand assets, design sources, social presence, timeline, and budget.
4. Route durable facts. The workflow maps each confirmed fact to the project’s existing authority surface and proposes new purpose-based files only where an owner is missing.
5. Write approved documentation. It updates only the agreed files and navigation, then reports the actual paths and unresolved context.
6. Offer separate follow-up actions. It asks separately before committing and suggests a small set of relevant Marketing Skills for the next outcome.

The interview is intentionally progressive. Optional answers may remain TBD, but the completion report should make those gaps visible.

Keep mutations and external effects explicit

• git init changes repository state. The Skill asks first when Git is absent.
• Creating a remote with gh repo create uses credentials and a networked provider, creates external state, and requires an explicit visibility and ownership decision.
• Reading supplied websites, videos, or social profiles can contact external providers and disclose request metadata.
• Budget, customer, follower, competitive, and brand information can be sensitive. Store only what the project is allowed to retain.
• Documentation generation writes files. Review the proposed outline and paths before allowing the write.
• The commit stage is optional and separately approved. The Skill does not authorize push, merge, publication, campaign launch, outreach, or spend.

Verify the output

A complete run should provide:

• A confirmed summary of existing product, audience, brand, objectives, and marketing assets.
• A completed or explicitly incomplete marketing brief.
• Minimal updates to the project’s existing documentation authorities, or purpose-based files only for roles that had no owner.
• Updated documentation navigation when the project uses one.
• A completion summary listing evidence checked, exact paths changed, skipped sections, and unresolved questions.
• A separate record of whether Git initialization, remote creation, and commit were declined, skipped, or approved.

Inspect the diff and validate every durable claim with its owner. The generated brief is project context, not proof that market claims, prices, audience sizes, or competitive statements are current.

Troubleshoot safely

Continue with the Marketing Kit overview, or review Installing kits when runtime discovery or scope is uncertain.

Know the current limits

• The source workflow can delegate research and documentation work, but actual Agent concurrency, question UI, and browser capability depend on the runtime.
• The Skill’s next-step phase still refers to a legacy command-catalog script and legacy slash examples. Marketing Kit ships zero commands; verify the installed Skill catalog and use the runtime invocation shown on each Skill page instead of assuming those examples are available.
• Website, social, competitor, price, follower, and budget information can change. The Skill cannot make it current without suitable evidence and access.
• It does not guarantee campaign performance, revenue, conversion, market fit, provider availability, or commercial results.