handoff

Generates a short orientation prompt pointing a fresh agent to a Jira ticket plan and branch.

Updated May 11, 2026
One-click install
npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill handoff-thachrocky12345
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill handoff-thachrocky12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new agent session on an existing ticket usually requires re-explaining context or pasting large amounts of plan content. This Skill produces a compact 3-6 sentence prompt that tells a fresh agent exactly what to do, where the implementation plan lives, which documentation indexes to read first, and which branch to use. ## Core Features & Use Cases - Argument Parsing: Accepts a Jira ticket key (RGDEV-NNN), an optional base branch via --branch, and scope flags --be or --fe. - Lightweight Context Fetch: Checks the current git branch and queries the Jira ticket only for summary, status, parent epic, and whether an implementation plan comment exists. - Structured Prompt Output: Emits a single copyable prompt covering the task, plan location, reading starting points (CLAUDE.md, Docs/TopicTagMap.md), branch, and scope. - Use Case: After running a planning pipeline on RGDEV-187, generate a handoff prompt so a new Claude Code session can start implementation immediately without re-reading the whole ticket history. ## Quick Start Ask the agent to create a handoff prompt for ticket RGDEV-187 with backend scope, then paste the output into a fresh session.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I hand off a Jira ticket to a new agent session?

Run the handoff skill with the ticket key, for example RGDEV-187, optionally adding --branch, --be, or --fe. It outputs a 3-6 sentence prompt you paste into the new session, pointing the agent to the plan comment, documentation indexes, and branch.

What information does the handoff prompt include?

The prompt covers five points: the ticket key and core task, where the implementation plan lives on Jira, which documentation indexes to read first (CLAUDE.md, Docs/TopicTagMap.md), the branch to use, and a one-line backend or frontend scope reminder.

Does the handoff prompt include the full plan or ticket description?

No. The prompt deliberately excludes plan content, ticket description body, git logs, and file contents. It only points the receiving agent to where those live, so the agent reads them itself in its own session.

What happens if no implementation plan exists on the Jira ticket?

The generated prompt tells the receiving agent that no plan exists yet and directs it to read the ticket description at the Jira URL to understand the requirements before starting work.

Can I limit the handoff to backend or frontend work only?

Yes. Pass --be for backend only or --fe for frontend only. If neither flag is given, the prompt covers both scopes, and the output includes a one-line scope reminder for the receiving agent.