Keep marketing project knowledge current with ak:docs

Use ak:docs to create, reconcile, or summarize project documentation without forcing a standard folder tree. The Skill keeps decisions, constraints, terminology, and navigation in prose while pointing current behavior to its executable evidence.

Choose ak:docs for evidence-backed documentation

Use ak:docs when

• A marketing project needs a minimal documentation route for people, AI collaborators, or both.
• An approved workflow, configuration, public contract, or operating constraint changed and nearby documentation may be stale.
• You need a focused summary of current project evidence.
• Existing docs copy mutable commands, inventories, or implementation behavior.

Choose another workflow when

• Your own vision or decisions should become the document through an interview. Use ak:interview-docs.
• You need a research assignment. Use ak:research-prompt.
• You want product code implemented. ak:docs explicitly excludes that work.
• You only need a diagram. Use ak:mermaidjs-v11 or ak:tech-graph.

Prepare the project and runtime

Identify the audience, the decision the docs must support, the sources that prove current behavior, and the acceptance criteria. Run from the project whose instructions and evidence should govern the result.

The Skill reads repository instructions such as AGENTS.md or CLAUDE.md, the root README.md, existing docs navigation, nearby docs, then relevant source, tests, scripts, generated artifacts, and live state. It does not assume a filename, file count, or universal docs tree.

See Runtime adapters for component-level differences.

Run the Skill

The first argument selects init, update, summarize, or agent-context. Empty or unclear input makes the Skill ask; it never assumes init.

/ak:docs update Reconcile the launch docs with the approved campaign workflow. Change only claims proven by current project evidence, preserve unrelated docs, and do not publish

/ak:docs update Reconcile the launch docs with the approved campaign workflow. Change only claims proven by current project evidence, preserve unrelated docs, and do not publish

$ak:docs update Reconcile the launch docs with the approved campaign workflow. Change only claims proven by current project evidence, preserve unrelated docs, and do not publish

For root context, /ak:docs agent-context --advice asks kongming before a proposed write. /ak:docs agent-context --audit presents one keep, cut, fix, or migrate decision at a time and applies only confirmed changes. Use $ak:docs in Codex. Deterministic settings and Hook configuration are recommend-only, and no Cursor root context filename is defined. Use ak:folder-context only for subfolders.

Follow the evidence-first stages

1. Set the contract. Bound audience, outcome, authority, evidence, scope, and acceptance criteria.
2. Discover the route. Read project instructions and navigation before selecting documents.
3. Map claims to owners. Use source, tests, schemas, manifests, generators, and live state for current behavior.
4. Choose the smallest change. Reuse coherent routes; avoid empty indexes, speculative roadmaps, and automatic ADR collections.
5. Author or summarize. Point to executable owners instead of copying mutable behavior.
6. Validate. Check links, paths, examples, configuration keys, commands, and owning scripts where practical.

Keep documentation changes within authority

Do not place credentials, private customer data, or secret URLs in docs. Keep plans, audits, research, and release evidence separate from evergreen authority. Review any proposal that would replace an established docs route before writing.

Verify outputs and evidence

There is no fixed output filename. A complete run should identify:

• docs created, changed, retained, or removed;
• the audience and decision served by each changed document;
• the evidence owner for each current claim;
• links, paths, examples, and validators checked; and
• remaining uncertainty or actions that still need approval.

For summarize, expect a response unless you named a durable target. For init or update, inspect the diff and confirm no product code or unrelated documentation changed.

Troubleshoot and understand limits

The Skill can verify only evidence and live state accessible in the current session. It cannot make unsupported claims true or decide publication policy.

Continue with the Marketing Kit overview, Marketing Kit Agents, or Installing kits.