Quick Ref / Command

Marketing Kit

/ak:brainstorm

Bounded outcome and option design

Turn incomplete intent into a bounded delivery contract, inspect evidence, compare real options, choose the smallest sufficient direction, and hand off cleanly to plan, cook, or fix.

01

Capture contract

02

Stay proportional

03

Inspect evidence

04

Route bugs differently

Rule 01

Brainstorming shapes intent and choices; it does not replace implementation, diagnosis, or verification.

Rule 02

Clear requests should not be converted into ceremonial interviews.

Rule 03

Options are useful only when they are grounded in inspected evidence and real trade-offs.

Rule 04

KISS, DRY, and --yagni keep the accepted contract from absorbing nearby unrequested work.

Execution Map

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

01

Start

Input, scope, route

  1. 1 Capture contract For multi-step delivery, record outcome, constraints, non-goals, and acceptance criteria unless an accepted design already contains them.
  2. 2 Stay proportional For concrete requests, summarize briefly and continue; ask only when a missing answer materially changes outcome, safety, or public contract.
  3. 3 Inspect evidence Read the smallest relevant source, docs, tests, plans, or live state before judging options or feasibility.
02

Work

Agent / skill execution

  1. 4 Route bugs differently For bugs, frame the repaired behavior, scout the failing path, prove root cause, then compare cause-aligned fixes only if there are real choices.
  2. 5 Compare options When a design choice remains, present up to three viable approaches with trade-offs, main assumption, and first failure condition.
  3. 6 Recommend small Recommend the smallest approach that satisfies the contract; if an assumption cannot be resolved, prefer the option cheapest to abandon.
03

Verify

Gate, review, validation

  1. 7 Handle modes Apply --html, --report, --advice, --ultra, or --yagni only when requested, preserving the core contract and downstream handoff.
  2. 8 Handoff owner Pass contract fields, chosen direction, evidence, and unresolved risks to ak-plan, ak-cook, ak-fix, or stop with an exploration report.
  3. 9 Report unresolved List unresolved questions last; write durable summaries only when decisions must survive the session or feed a plan.

Output / publish flags

Only flags that change the artifact or publish it. Not the full option set.

--advice

Advisory supervision

Run under kongming supervision at phase checkpoints, stuck points, high-stakes decisions, and downstream PR review handoff.

--html

HTML brief

Write a self-contained brainstorm.html with contract fields, options, recommendation, risks, and required implementation diagram.

--report

Markdown report

Persist a timestamped markdown report in the configured reports location with summary, contract, trade-offs, recommendation, and unresolved questions.

--ultra

Best-of-5 verifier

Dispatch five independent read-only candidate brainstorms, then let one verifier rank and select or reject the candidates.

--yagni

Scope cutter

Challenge and remove scope not needed for the stated outcome, and pass the flag to downstream handoffs.

--no-antv

Disable AntV visuals

Disable the AntV infographic tile layer when HTML/editorial visual output would otherwise use it.

--no-diagram-design

Disable diagram-design

Disable the diagram-design Quadrant vernacular for approach comparison visuals.

--no-editorial-visuals

Disable editorial visuals

Disable the additive editorial visual layer for brainstorm HTML output.

Sample Prompt

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

Bound a launch Recommended
/ak:brainstorm launch campaign for the new feature
Use when:
The work is multi-step and needs outcome, constraints, non-goals, and acceptance before execution.
Expected:
A bounded delivery contract plus the smallest recommended route that still satisfies the accepted outcome.
Preview as HTML
/ak:brainstorm landing page redesign --html
Use when:
The decision should be previewed as a self-contained HTML brief before delivery.
Expected:
A self-contained HTML brief with contract fields, compared approaches, recommendation, risks, and implementation diagram.
Cut scope
/ak:brainstorm onboarding flow --yagni
Use when:
The request may attract unnecessary abstractions or adjacent work.
Expected:
A contract that challenges and removes scope not needed for the stated outcome.

Handled Scope

  • Outcome framing
  • Constraints and non-goals
  • Acceptance criteria
  • Option comparison
  • Bug diagnosis routing
  • HTML or report briefs
  • Verifier mode

Next