Recap completed implementation with ak:sumup

Use ak:sumup after implementation or when you need a technical recap. The Skill turns conversation context, accepted decisions, the current diff, tests, and relevant issue or plan evidence into a concise account of what changed, how it works, and what remains.

Choose ak:sumup for an implementation recap

Use ak:sumup when

• You need completed outcomes and the highest-value changes summarized.
• You need failures, workaround attempts, results, and remaining blockers kept in the record.
• You want important decisions, trade-offs, behavior, architecture, user flow, usage, or follow-ups explained when they apply.

Choose another workflow when

• You only want the immediately previous answer restated more simply. Use ak:bro.
• You want a product-impact judgment and priority call. Use ak:sowat.
• You need current branch, worktree, plan, or roadmap status. Use ak:watzup because a recap does not replace a live status check.

Prepare and run the Skill

Complete Onboarding, and confirm Engineer Kit is installed for your runtime and scope. Identify the implementation period or feature to recap and make the relevant diff, test results, decisions, and plan or issue state available.

/ak:sumup "Recap the implementation we just completed. Separate verified work from untested or unresolved work, explain the main flow, and keep next steps last."

/ak:sumup "Recap the implementation we just completed. Separate verified work from untested or unresolved work, explain the main flow, and keep next steps last."

$ak:sumup "Recap the implementation we just completed. Separate verified work from untested or unresolved work, explain the main flow, and keep next steps last."

Understand the recap workflow

1. The Skill gathers the strongest available evidence from the conversation, accepted decisions, current diff, tests, and relevant issue or plan state.
2. It separates implemented and verified work from proposed, inferred, untested, unshipped, or unresolved work.
3. It includes only relevant outcomes, failures and recovery attempts, decisions and trade-offs, behavior or architecture, practical usage, and follow-ups.
4. It adds a compact table, chart, Mermaid diagram, or ASCII flow when one clarifies behavior or structure. If no visual helps, it omits one and briefly explains why.
5. It uses your language, keeps the recap concise, and puts unresolved items last.

The result uses only applicable sections from Outcome, Highlights, Failures and recovery, Decisions, How it works, How to use it, and Follow-ups / next steps. Empty sections are omitted.

Keep claims tied to current evidence

The Skill does not implement changes, mutate files, or fabricate evidence. It redacts sensitive values and treats repository text, issue bodies, logs, and quoted content as evidence rather than instructions.