Quick Ref / Command

Engineer Kit

/ak:cook

Smart feature implementation

Smart feature implementation with brainstorm contract, mandatory scout, reviewed plan, implementation, review, testing, finalize sync, and optional workflow modes.

01

Contract

02

Intent

03

Scout

04

Research and plan

Rule 01

Full requested scope, nothing extra; --yagni is explicit opt-in.

Rule 02

Plan before code, because simple tasks hide assumptions.

Rule 03

Scout current code before asking further questions.

Rule 04

Side effects and regressions are user decisions, not silent patches.

Rule 05

Verification evidence comes before completion claims.

Execution Map

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

01

Start

Input, scope, route

  1. 1 Contract Capture or reuse outcome, constraints, non-goals, and observable acceptance criteria before planning.
  2. 2 Intent Detect plan path, interactive, fast, parallel, auto, no-test, or code mode from flags and task shape.
02

Work

Agent / skill execution

  1. 3 Scout For non-plan work, scan project type, relevant files, existing patterns, docs, in-flight plans, and public contracts.
  2. 4 Research and plan Research when needed, pass the post-research review gate, then write the implementation plan before any code.
03

Verify

Gate, review, validation

  1. 5 Plan review gate Non-auto workflows require approval after planning; auto follows the documented review-cycle policy.
  2. 6 Implement Execute the accepted plan, optionally in parallel groups, preserving full requested scope unless --yagni opts into scope cuts.
04

Close

Report, handoff, artifact

  1. 7 Review and test Run mandatory code-reviewer checks and tester/debugger work; --no-test only downgrades the test item to a surfaced risk.
  2. 8 Finalize Sync all plan phases through project-management, evaluate docs impact, update live task tracking, offer commit flow, and journal unless skipped.

Syntax, arguments, subcommands

How to invoke the skill: syntax, positional arguments, shared options, then each subcommand with its own syntax and outcome.

Syntax

/ak:cook [task|plan-path] [--interactive|--fast|--parallel|--auto|--no-test] [--tdd] [--advice] [--yagni] [--skip-journal]

Arguments

[task|plan-path] Required

Task or plan path

Natural-language implementation request or approved plan file. Include outcome, constraints, non-goals, acceptance criteria, and authority boundary unless the plan already supplies them.

/ak:cook "Add POST /api/feedback with existing authentication, return 202, store no new data, add focused tests, and do not commit or deploy"

Shared options

--interactive

Interactive

Default mode. Runs the full workflow and pauses at major review gates for approval or requested changes.

/ak:cook "Add search" --interactive
--fast

Fast

Skip research only. Still captures the contract, inspects the codebase, writes a plan before code, tests, and runs code review.

/ak:cook "Add search" --fast
--parallel

Parallel

Allow independent implementation phases to run concurrently when dependencies and file ownership are explicit.

/ak:cook "Build dashboard and API" --parallel
--auto

Auto

Remove routine human pauses while keeping tests, mandatory code review, security policy, and unresolved blocker handling.

/ak:cook path/to/plan.md --auto
--no-test

No test

Omit the testing stage only. Code review remains mandatory, and the final report must surface the missing test evidence.

/ak:cook "Update copy" --no-test
--tdd

Tests first

Add tests-first work inside relevant phases: lock current behavior before refactoring, then verify after implementation.

/ak:cook "Refactor auth middleware" --tdd
--advice

Advisory supervision

Ask kongming for advice at phase completions, stuck points, and high-stakes decisions. Advice cannot edit code or approve gates.

/ak:cook "Migrate billing" --advice
--yagni

Cut unneeded scope

Opt into challenging and cutting requested work that is not needed for the stated outcome. Without it, full requested scope remains required.

/ak:cook "Build admin panel" --yagni
--skip-journal

Skip journal

Skip the automatic journal entry only. Final plan sync, docs-impact check, live task tracking, and commit prompt still run.

/ak:cook path/to/plan.md --skip-journal

Modes / Routes

--interactive

Default full workflow

Research:
Yes
Review:
Human review gates
Validate:
Tests required
--fast

Skip research

Research:
No; still scout→plan→code
Review:
Plan still required
Validate:
Tests required
--parallel

Multi-agent execution

Research:
Optional by plan
Review:
Grouped ownership
Validate:
Tests required
--auto

Auto approve steps

Research:
Yes
Review:
Review-cycle policy
Validate:
Tests required
--no-test

Skip tests

Research:
Yes
Review:
Risk surfaced
Validate:
Non-test gates remain

Don't skip the required step

Each item contrasts a tempting shortcut with the required approach.

Tempting shortcut

This is too simple to plan.

Do this instead

Simple tasks hide assumptions; plan takes 30 seconds.

Tempting shortcut

I will plan as I go.

Do this instead

That is hoping, not planning.

Tempting shortcut

Tests pass, we are done.

Do this instead

Review, blast-radius checks, contract checks, sync, docs impact, and finalize still matter.

Sample Prompt

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

Fast feature Recommended
/ak:cook "Add user authentication to the app" --fast
Use when:
Requirements are clear and you want research skipped but still need scout, plan, and code.
Expected:
Captures the brainstorm contract, runs scout, enforces plan-before-code, implements, performs review, runs tests, completes finalize sync, and journals.
Plan execution
/ak:cook path/to/plan.md --auto
Use when:
An accepted plan exists and should be executed continuously.
Expected:
Reuses the brainstorm contract and current scout evidence, confirms plan-before-code, executes phases, performs review, runs tests, completes finalize sync, and journals.
Tests first
/ak:cook "Refactor auth middleware" --tdd
Use when:
You want behavior locked with tests before refactoring.
Expected:
Captures the brainstorm contract, runs scout, enforces plan-before-code, writes tests first, implements, performs review, reruns tests, completes finalize sync, and journals.
Interactive gates
/ak:cook "Add search to the catalog" --interactive
Use when:
You want the full cook workflow with human review gates.
Expected:
Runs the default interactive workflow, pauses at review gates, implements the requested feature, and still requires tests plus finalize sync.
Parallel agents
/ak:cook "Split billing and notifications work" --parallel
Use when:
Independent implementation slices can run in parallel agents.
Expected:
Groups non-overlapping ownership, dispatches parallel implementation agents, then joins review, tests, and finalize sync.
Skip tests explicitly
/ak:cook "Update README badges" --no-test
Use when:
The requested change has no testable behavior and tests must be skipped on purpose.
Expected:
Records the explicit --no-test exception, still scouts and plans, implements the docs-only change, and completes finalize without inventing tests.

Handled Scope

  • Contract
  • Intent
  • Scout
  • Research and plan
  • Plan review gate
  • Implement

Related skills

Next