Quick Ref / Command

Marketing Kit

/ak:init

Marketing Project Initialization

Onboards a new or existing marketing project through git setup, parallel research, a structured brief interview, minimal documentation, and next actions.

01

Check git

02

Research in parallel

03

Discover authority

04

Verify context

Rule 01

Initialization is a structured marketing brief, not a generic questionnaire dump.

Rule 02

Existing documentation authority must be preserved and extended minimally.

Rule 03

Researchers split independent discovery so the brief starts from evidence, not guesses.

Rule 04

Unresolved questions are acceptable only when named clearly at the end.

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Check git Detect whether git is initialized, ask before git init, optionally gather remote repository details, or show the existing remote.
  2. 2 Research in parallel Spawn 3 to 4 researchers for product, existing marketing assets, digital presence, and competitive landscape.
  3. 3 Discover authority Read repository instructions, README, documentation navigation, brand/legal constraints, strategy, milestones, and asset guidance.
02

Work

Agent / skill execution

  1. 4 Verify context Summarize existing product, audience, brand, objectives, and campaigns, then ask the user whether it is accurate.
  2. 5 Interview brief Collect basic info, products, objectives, target audience, competitors, brand assets, design inputs, social presence, timeline, and budget.
  3. 6 Generate docs Use docs-manager to route facts by role and update existing authorities or create only missing purpose-based surfaces.
03

Verify

Gate, review, validation

  1. 7 Offer commit Ask whether to commit generated documentation, then use /git:cm only if the user agrees.
  2. 8 Suggest next actions Generate the command catalog and recommend 3 to 5 relevant next marketing actions or finish.
  3. 9 Report changed paths List actual paths changed, evidence checked, unresolved questions, and token-efficient next-step guidance.

Don't skip the required step

Each item contrasts a tempting shortcut with the required approach.

Tempting shortcut

Use standard filenames for the marketing docs.

Do this instead

Preserve the project authority structure and create only missing purpose-based surfaces.

Tempting shortcut

Ask every question at once.

Do this instead

Use progressive disclosure so the interview stays conversational and usable.

Tempting shortcut

Skipped answers can disappear.

Do this instead

If optional sections are skipped, note them as TBD and list unresolved questions.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

New project Recommended
/ak:init new DTC skincare brand launch
Use when:
Starting a marketing project with little existing structure.
Expected:
Runs setup, research, interview, minimal docs generation, and next-action suggestions.
Existing project
/ak:init onboard existing B2B SaaS marketing project
Use when:
An existing repository or client needs marketing context discovery and confirmation.
Expected:
Researches current authorities, verifies accuracy with the user, and updates only needed surfaces.
Website-based brief
/ak:init marketing brief from existing website and brand assets
Use when:
Brand and design inputs should be extracted from live or existing materials.
Expected:
Includes website extraction, brand asset review, and structured interview follow-up.

Handled Scope

  • Marketing brief interview
  • Project context discovery
  • Brand constraints
  • Audience and competitors
  • Documentation routing
  • Next-action planning

Artifacts Produced

Initialization summary

Pattern

Actual paths changed, evidence checked, unresolved questions, and relevant next commands

Reports exactly what changed and where, without imposing a documentation tree.

Related skills

Next