crowi-handoff

Generates standardized HANDOFF documents, memory pointers, and notifications when pausing development sessions.

1.1k|165|Updated Aug 18, 2014
One-click install
npx skills add https://github.com/crowi/crowi --skill crowi-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crowi-handoff
Source: https://github.com/crowi/crowi/tree/main/.claude/skills/crowi-handoff
Command: npx skills add https://github.com/crowi/crowi --skill crowi-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a development session ends or is interrupted mid-task, work state is often lost or recorded inconsistently, causing integration debt and duplicated effort. This Skill standardizes session handoffs by capturing verified progress, remaining tasks, and next steps in a structured HANDOFF document.

Core Features & Use Cases

  • Structured HANDOFF generation: Collects git state (branch, commits, dirty files) and conversation context, then writes a fact-based HANDOFF markdown file distinguishing verified from unverified work.
  • Completion detection: Detects when a worktree task is actually finished and redirects to the complete-feature flow instead of a handoff, preventing missed integration signals.
  • Memory and notification integration: Writes a memory pointer in the main project's memory directory and optionally sends an agmsg team notification, then drops the session's agmsg role.
  • Use Case: You are mid-way through a feature in a git worktree and need to stop for the day. Run the handoff to produce a HANDOFF file with exact resume commands, gate status, and known pitfalls so the next session continues without rediscovery.

Quick Start

Ask the assistant to run the crowi-handoff skill to record the current session's work state as a resumable handoff document.

Frequently Asked Questions about crowi-handoff

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

FAQPage Schema
How do I hand off an unfinished coding session to another session?

Run the handoff workflow, which collects branch, commit, and working-tree state plus conversation context, then writes a HANDOFF markdown file with completed work, remaining tasks, exact next commands, and verification commands for resuming.

What should a session handoff document include?

A handoff document should include the branch and commit state, gate results (type-check, test, lint), verified versus unverified work, completed commits, concrete remaining tasks, command-level next steps, and known pitfalls.

Does the handoff skill work in git worktrees and the main branch?

Yes, it works in both. Worktree sessions write HANDOFF-<id>.md at the worktree root without committing, while main sessions write to .feature-state/ with a dated topic filename.

What happens if the work is actually complete when I run a handoff?

The skill detects completed worktree work (clean tree, commits ahead of main, gates passing) and redirects to the complete-feature flow first, so integration signals are not missed. If gates fail, it falls back to a normal handoff.

Will the handoff process commit or push my changes?

No, the handoff never pushes or commits. Dirty working-tree state is recorded as-is in the HANDOFF document, and all git inspection commands are read-only.

What happens if the memory directory or notification tool is unavailable?

Missing memory directories or absent agmsg tooling are skipped gracefully and noted in the final report. The HANDOFF file itself is still written, so the handoff never fails on optional steps.