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:sowat

Product Impact Priority Call

Reviews recent implementation and related issues like a product owner, turning evidence into a concise so-what judgment, priority correction, and at most three next steps.

01

Establish outcome

02

Connect only related work

03

Score candidates

04

Cut busywork

Rule 01

Outcome beats activity

Rule 02

Evidence beats contrarian performance

Rule 03

Recommend fewer, higher-impact next steps

Rule 04

Separate fact from inference and name missing evidence

Execution Map

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

01

Start

Input, scope, route

  1. 1 Establish outcome Identify the intended user or business outcome and the strongest evidence of what was implemented, verified, shipped, and still open.
  2. 2 Connect only related work Bring in genuinely connected issues, blockers, regressions, dependencies, adoption risks, and follow-on opportunities.
02

Work

Agent / skill execution

  1. 3 Score candidates Judge actions by impact, urgency, confidence, effort, risk, dependency leverage, and learning or delivery value.
  2. 4 Cut busywork Deprioritize polish, internal elegance, or activity that does not change the user outcome.
03

Verify

Gate, review, validation

  1. 5 Correct priority If evidence supports it, state what the current focus gets wrong and what deserves attention instead.
  2. 6 Recommend next steps Return no more than three ordered actions, each with why now and an observable success signal.

Syntax, arguments, subcommands

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

Syntax

/ak:sowat [priority question or evidence]

Arguments

[priority question or evidence] Required

Priority question or evidence

Natural-language product priority request with the intended user outcome, implemented work, verification or shipment evidence, and related issues to evaluate. It guides analysis only; it does not authorize code changes or issue updates.

/ak:sowat "Review the completed onboarding changes and related open issues. Tell me what matters now, correct my priority if needed, and give at most three next steps with success signals."

Sample Prompt

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

Post-implementation priority call Recommended 
/ak:sowat Review the completed onboarding changes and related open issues. Tell me what matters now, correct my priority if needed, and give at most three next steps with success signals.
Use when:
After implementation, when you need the user or business meaning of the work and what matters next.
Expected:
Separates implemented, verified, shipped, and still-open evidence; connects only related issues; then returns a brief so-what judgment with up to three ordered next steps and observable success signals.
Challenge weak focus 
/ak:sowat Are we focusing on the wrong thing after this release, or should the remaining adoption blockers take priority?
Use when:
When polish or internal improvements may be distracting from blockers, regressions, or higher-impact outcomes.
Expected:
Judges candidates by impact, urgency, confidence, effort, risk, dependency leverage, and learning value, then corrects the current focus only if evidence shows a concrete trade-off.
Rank related issues 
/ak:sowat Compare the follow-on checkout issues with the regression reports and tell me the top product-impact actions to take next.
Use when:
When several related dependencies, regressions, blockers, or opportunities compete for attention.
Expected:
Connects only genuinely related work, deprioritizes busywork that does not change the outcome, and recommends no more than three actions with why-now rationale and success signals.
Name missing evidence 
/ak:sowat We shipped the trial upgrade flow, but analytics are incomplete. What can we conclude, what is inference, and what should we do next?
Use when:
When shipment, usage, customer, or verification evidence is incomplete but you still need a priority call.
Expected:
Keeps facts separate from inference, refuses to invent product evidence, names what evidence is missing, and frames next steps around observable learning or delivery signals.

Handled Scope

  • product impact
  • priority correction
  • issue triage
  • outcome framing
  • success signals

Next