forward

Create a session handoff markdown file with accomplishments, pending items, and next steps.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill forward-tinner-deinno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forward
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/forward
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill forward-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of ending a work session without clear continuity by packaging what happened, what remains, and what to do next for the next run.

Core Features & Use Cases

  • Creates a session handoff file with session summary, pending items, and next steps.
  • Enables plan-mode handoff approval so you can review and confirm the carried-forward plan before moving on.
  • Optionally creates GitHub issues from actionable pending items, then records an outbox entry even if issue creation is skipped.
  • Use case example: You finish a coding session, want the next session to continue immediately, and want remaining tasks tracked as issues while keeping the shared vault updated.

Quick Start

Run the command /forward to create a handoff, extract pending next-step checkboxes, optionally create GitHub issues with your approval, and enter plan mode for the next session.

Frequently Asked Questions about forward

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

FAQPage Schema
How do I create a session handoff for pending tasks and next steps?

A session handoff captures accomplishments, pending items, and next steps into a markdown file for continuity. It ensures the next session resumes immediately by packaging what happened and what remains into a structured vault inbox entry.

Can I create GitHub issues from pending actionable items during a session wrap up?

Yes, during a session wrap up, actionable checkbox items from the handoff file can be optionally converted into GitHub issues. The Skill requires user confirmation before creating issues and records an outbox entry even if issue creation is skipped.

What is a plan-mode handoff approval workflow for developer productivity?

A plan-mode handoff approval workflow uses an approval-table flow to let you review and confirm carried-forward plans before ending a session. It transitions the current session into a structured plan mode for the next run.

Does session handoff work with versioned workflows in a shared vault?

Yes, session handoff supports versioned workflows by producing handoff markdown files in the resolved vault inbox path. This keeps a shared vault updated with outbox entries and maintains task continuity across different session runs.

When do I need to use a session handoff for task continuity?

You need a session handoff when you finish a coding session and want the next session to continue immediately. It solves the problem of ending work without clear continuity by packaging what happened and what remains.