VividKit Crystal clear AI coding
VI
Choose Your Setup Get Started with AgentKit Continue with ClaudeKit Migrate from ClaudeKit to AgentKit Clean cutover from ClaudeKit What Is AgentKit? How AgentKit Works AgentKit Kits, Skills, Agents & Hooks AgentKit Runtime Support AgentKit Desktop App AgentKit Configuration AgentKit CLI Quick Reference AgentKit Skills Cheatsheet AgentKit Workflows AgentKit Statusline Update AgentKit CLI & Kits AgentKit Helper Clean reinstall of AgentKit AgentKit Troubleshooting What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence ClaudeKit x Codex CK → Other coding tools How ClaudeKit Works Inside ClaudeKit Finding Your Unknowns Session Recovery Fix from Logs UI/UX Guide Accounts Switcher IDE Config Remote Control Codex App System Diagramming UI Review Gate Promotions Support VividKit

Quick Ref / Command

Engineer Kit

/ak:interview-docs

Interview-Driven Docs

Turn the user’s own vision, decisions, and wording into durable README, ADR, principles, strategy, review, or framework documents through a guided interview.

01

Select mode

02

Ask if ambiguous

03

Read nearby docs

04

Interview from user

Rule 01

The document should preserve the user’s knowledge, taste, and decisions.

Rule 02

Ask before ranking, sequencing, or prioritizing user-provided material.

Rule 03

Use ak-brainstorm for AI proposals and ak-docs for code-derived documentation.

Execution Map

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

01

Start

Input, scope, route

  1. 1 Select mode Choose vision mode for project vision, README direction, and ADR decisions; choose structured-doc mode for one user-authored principles, strategy, review, or framework document.
  2. 2 Ask if ambiguous If both modes fit, ask one concise question before writing.
02

Work

Agent / skill execution

  1. 3 Read nearby docs In vision mode, read README.md and docs/adr first; in structured mode, read nearby documents and create only a minimal skeleton once.
  2. 4 Interview from user Ask five high-variety questions in vision mode, or exactly one specific open question at a time in structured-doc mode.
03

Verify

Gate, review, validation

  1. 5 Patch after each answer After every answer, re-read the affected document or section and patch the user’s words before asking the next question.
  2. 6 Preserve decisions Keep README to vision and record explicit architectural decisions in short numbered ADRs with Status, Context, Decision, and Consequences.
04

Close

Report, handoff, artifact

  1. 7 Respect unordered lists Treat a user-provided list as unordered until the user explicitly approves rank, sequence, or priority.
  2. 8 Stop speculation Never invent content, overwrite existing docs, add speculative sections, or use ADRs to make unapproved architecture decisions.

Syntax, arguments, subcommands

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

Syntax

/ak:interview-docs <vision | document-path | topic>

Arguments

<vision | document-path | topic> Required

Interview target

Intent hint for the interview: name vision mode, a document path, or a topic, plus audience, scope, protected sections, and when to stop. It is not a fixed parser and does not authorize the Skill to invent decisions.

/ak:interview-docs ./docs/product-principles.md "Interview me to capture five product principles in my wording."

Don't skip the required step

Each item contrasts a tempting shortcut with the required approach.

Tempting shortcut

The user listed five ideas; order them by importance.

Do this instead

A user list is unordered unless they approve rank or priority.

Tempting shortcut

The code reveals the architecture; write an ADR.

Do this instead

ADR records only decisions the user explicitly made.

Sample Prompt

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

Vision interview Recommended 
/ak:interview-docs vision for README direction and first ADRs
Use when:
The user’s own answers should become the project vision, README direction, and recorded decisions.
Expected:
Reads README.md and docs/adr first, asks a batch of five varied questions, then patches user wording into README or numbered ADRs after each answer.
Focused vision area 
/ak:interview-docs vision focused on product principles
Use when:
The interview should stay on a requested focus area instead of a broad project vision pass.
Expected:
Uses vision mode with the requested focus, asks an adjusted question batch, and keeps README content separate from explicit ADR decisions.
Structured document 
/ak:interview-docs docs/principles.md
Use when:
One durable user-authored document should be built through one-question-at-a-time interviewing.
Expected:
Reads nearby documents, creates the minimal skeleton once, asks exactly one specific open question, then re-reads and patches the target section.
Decision capture 
/ak:interview-docs ADR for the deployment approach
Use when:
A user-approved architectural decision should be recorded without letting the assistant decide architecture.
Expected:
Confirms the decision from the user’s answer and records only approved content in a short ADR with Status, Context, Decision, and Consequences.

Handled Scope

  • Guided documentation interviews
  • README vision updates
  • ADR capture
  • Principles and strategy documents
  • User-wording preservation

Artifacts Produced

Interview-docs output

Pattern

Updated README, ADR, or target document with user-sourced wording and explicit decisions only.

The process continues answer by answer until the user ends the interview.

Next