forward

Create a session handoff document and enter plan mode.

116|56|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/Soul-Brews-Studio/oracle-skills-cli --skill forward
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forward
Source: https://github.com/Soul-Brews-Studio/oracle-skills-cli/tree/main/src/skills/forward
Command: npx skills add https://github.com/Soul-Brews-Studio/oracle-skills-cli --skill forward

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-of-session handoff by generating a concise handoff document and immediately entering plan mode for the next session.

Core Features & Use Cases

  • Handoff generation: compiles session summary, outstanding items, and context into a ready-to-share document.
  • Plan mode initiation: transitions the workflow into planning for the next session after the handoff.
  • Use Case: Imagine concluding a session with a handoff and a ready-to-plan agenda.

Quick Start

Use the /forward command to create a handoff and enter plan mode for the next session. Use /forward --only to create the handoff without entering plan mode.

Frequently Asked Questions about forward

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

FAQPage Schema
How do I automate context transfer for an AI workflow session handoff?

Automating context transfer compiles your session summary and outstanding items into a handoff document. This skill writes the context transfer file to a specific inbox directory, commits the changes, and pushes them to your repository.

What is the best way to plan the next AI session after concluding work?

Planning the next AI session involves generating a handoff document and immediately entering plan mode. This skill creates your session agenda and automatically transitions the workflow into a planning state via the EnterPlanMode tool.

Can I generate a handoff document without automatically entering plan mode?

Yes, you can generate a handoff document without entering plan mode by using the /forward --only command. This creates the session summary and commits the changes without triggering the plan-mode setup.

Where are session handoff documents saved during an AI workflow transition?

Session handoff documents are saved as markdown files in the psi/inbox/handoff directory. The file is named using a timestamp and slug format, such as YYYY-MM-DD_HH-MM_slug.md, to organize transition scenarios chronologically.

Does creating a handoff document automatically commit and push changes to my repository?

Yes, creating a handoff document automatically commits and pushes the changes to your repository. This ensures the session context transfer is permanently saved before the workflow enters plan mode for the next session.