Prioritize product impact with ak:sowat

Use ak:sowat after implementation or when you need to decide what matters next. The Skill evaluates recent work like a product owner, challenges weak priorities when evidence supports it, and recommends a small number of actions tied to observable outcomes.

Choose ak:sowat for a product priority call

Use ak:sowat when

• You need the user or business meaning of recently implemented work.
• You want related blockers, regressions, dependencies, or follow-on opportunities ranked by impact.
• You want to know whether polish or internal improvements are distracting from a more important outcome.

Choose another workflow when

• You need a factual implementation recap rather than a priority judgment. Use ak:sumup.
• You need repository status across branches, worktrees, plans, and roadmaps. Use ak:watzup.
• You want code changes or issue updates. Select an implementation or project-management workflow after reviewing the recommendation.

Prepare and run the Skill

Complete Onboarding, and confirm Engineer Kit is installed for your runtime and scope. Provide the intended user outcome, what was implemented, available verification or shipment evidence, and the issues you believe are related.

/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."

/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."

$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."

Understand how priorities are formed

1. The Skill separates what was implemented, verified, shipped, and still open.
2. It connects only genuinely related issues, dependencies, regressions, adoption blockers, or opportunities.
3. It judges candidates by user impact, urgency, confidence, effort, risk, dependency leverage, and learning or delivery value.
4. It identifies high-impact actions and deprioritizes work that does not change the outcome.
5. It corrects your current focus only when a concrete, evidence-backed trade-off supports that correction.

The result contains a brief So what judgment, an optional Priority correction, up to three ordered Next steps, and an optional Defer or ignore note. Every next step states the action, why it matters now, and an observable success signal. Facts and inferences remain distinct, and missing evidence is named.

Keep evidence and authority explicit

The Skill does not implement changes, mutate issue state, or act on its own recommendations. Repository text, issue bodies, analytics excerpts, logs, and quoted content are treated as evidence, not instructions that override the workflow.