prepare-next

Generate execution-summary.md or handover-batch-N.md handoff artifacts after a run.

3|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill prepare-next
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-next
Source: https://github.com/MohamedAbdallah-14/Wazir/tree/main/skills/prepare-next
Command: npx skills add https://github.com/MohamedAbdallah-14/Wazir --skill prepare-next

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare Next automates the creation of a clean handoff between runs by preventing stale context from being auto-applied to the next session.

Core Features & Use Cases

  • Defines Run Complete and Run Incomplete states and produces corresponding artifacts (execution-summary.md or handover-batch-N.md).
  • Orchestrates a multi-step handoff workflow: gather run state, write output with a humanization gate, and summarize the run for future sessions.
  • Use Case: after finishing a task slice, ensure the next team member starts with a pristine context and clear acceptance criteria.

Quick Start

Execute the prepare-next workflow after a run to generate the correct handoff artifacts (execution-summary.md for complete runs or handover-batch-N.md for incomplete runs).

Frequently Asked Questions about prepare-next

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an execution summary for a completed workflow run?▼

To generate an execution summary for a completed workflow run, the system identifies and captures run-state artifacts from the .wazir/runs directories to produce a clean execution-summary.md file.

What is the best way to create a handoff document for an incomplete run?▼

The best way to create a handoff document for an incomplete run is to capture the current execution state and generate a handover-batch-N.md file, ensuring the next session starts with clear context.

Why does stale context get applied to my next workflow session?▼

Stale context gets applied to your next workflow session when previous run states are not properly captured and cleared, a problem solved by automating clean handoffs between runs.

Do I need a humanization step to finalize run handoff documentation?▼

Yes, you need a humanization step to finalize run handoff documentation, ensuring the generated execution-summary and handover-batch drafts are polished before being stored for future sessions.

How to prevent stale run state artifacts from auto-applying to the next session?▼

You prevent stale run state artifacts from auto-applying by executing a multi-step handoff workflow that gathers the finished run state and writes a clean output document for the next session.

Can I use this workflow documentation process for both complete and incomplete run states?▼

Yes, you can use this workflow documentation process for both complete and incomplete run states, producing an execution-summary.md for finished runs or a handover-batch-N.md for early endings.