session-start
/session-start
Start a work session from the handoff the previous one left in `.gemba/sessions`: read the latest handoff, check it against Jira and the code, and propose its next step as one option. Use when someone says "retoma la sesión", "continúa donde quedamos", "session start" or "qué sigue" at the start of a session.
- Author
- dedujeong ↗
- Repository
- gemba ↗
- Licence
- Apache-2.0
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/latest_handoff.py
What it does and when to use it
Start a work session from the handoff the previous one left in `.gemba/sessions`: read the latest handoff, check it against Jira and the code, and propose its next step as one option. Use when someone says "retoma la sesión", "continúa donde quedamos", "session start" or "qué sigue" at the start of a session.
Triggers from the description
Original author description
Start a work session from the handoff the previous one left in `.gemba/sessions`: read the latest handoff, check it against Jira and the code, and propose its next step as one option. Use when someone says "retoma la sesión", "continúa donde quedamos", "session start" or "qué sigue" at the start of a session.
How it works
- 1. Find the project
- 2. Read the latest handoff
- 3. Check it against now
- 4. Propose the next step
- Style
SKILL.md preview
--- name: session-start description: Start a work session from the handoff the previous one left in `.gemba/sessions`: read the latest handoff, check it against Jira and the code, and propose its next step as one option. Use when someone says "retoma la sesión", "continúa donde quedamos", "session start" or "qué sigue" at the start of a session. --- # Start the session You pick up where the previous session stopped, without rebuilding its context. The handoff that `session-close` wrote is a summary of that session, not an instruction: Jira and the code decide what is true now. ## 1. Find the project Read the `## Gemba` section of the project's `CLAUDE.md`: `Jira Project` and `Language`. If it is missing, propose running `setup` first and stop. Use its `Jira Site` as the `cloudId` of every call; only when the block has none, get it once with `getAccessibleAtlassianResources` and propose running `setup` to add it. Every call to Jira is the one written in `../../references/jira-calls.md`, with its `fields` and `responseFields`. Talk with the person in `Language`. ## 2. Read the latest handoff Run `python3 scripts/latest_handoff.py` in the project. It prints the path of the most recent handoff of `.gemba/sessions`, found from the main working tree, and prints nothing when there is none. Read that file with Read, and tell the person which handoff it is, by the date and time in its name, so they notice if it is an old one. If there is no handoff, say so, propose nothing and stop: the person decides where to start. ## 3. Check it against now The handoff is a photo of a past moment. Before proposing anything, compare what it says with the present: - the issue of its Work in progress section, with Read the state of an issue (`getJiraIssue`): its state now; - the current branch and what the working tree has uncommitted, with `git branch --show-current` and `git status --short`. If something changed since the handoff (the issue is already in Review or Done, the branch is another, the pending changes are gone), say what changed before the proposal. Without a connection to Jira, say that the state of the issue could not be checked. ## 4. Propose the next step Take the Next step section of the handoff and propose it as one option, with its reason, adjusted to what you found in step 3 if that changed it. Never a list of options. Then wait for the person's answer: do not start that work on your own. ## Style - Conversation in the project's `Language`; headings and labels in English. - No emojis or filler.
Files in this package (2)
- SKILL.md 2 KB
- scripts/latest_handoff.py 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · dedujeong/gemba | 90 | Apache-2.0 |
| Kanevry/session-orchestrator | 100 | MIT |
| data-ai-xyz/tandem | 100 | MIT |
| youngeun1209/oh-my-claudecode-research | 100 | MIT |
| skyfox-io/memex | 100 | MIT |
Database snapshot: 13.11.2026 · package version bc2536e3a853 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100session-close
Close a work session by saving its state to a handoff in `.gemba/sessions`, so another session can continue where this one stopped: the version, the issue in progress, what was done, what is pending, what was decided and the next step. The handoffs stay out of git. Use when… - 100setup
Prepare a project for Gemba Code by writing its Gemba block in the project's CLAUDE.md: the Jira project, the Confluence space, the integration mode and the language. Use when someone sets up a repository for the method, says "configura el proyecto" or "setup", when a project… - 100handoff
Write a handoff file so a fresh session can continue this work - goal, decisions, what is done and how it was checked, what is left, the next step. Run only when the user asks for it by name. - 90hello
Start a working session. Read where the last one stopped, bring the project and its setup to the latest state, clear finished work, and say what to do next. Use when someone says "hello", "hi", "good morning", "let's start", "let's get going", "where were we", "what's next", or… - 90coordinator
Start or re-ground a repository design and orchestration session. Use to adopt the project coordinator identity, inspect ADRs, prompts, and linked Linear work, recommend the next action, and delegate implementation instead of writing feature code inline. - 100resume
Read the handoff note that a previous session left with handoff:save (a page in the Cairn board's Handoff collection, or .handoff/HANDOFF.md), check it against the current state of the repository, confirm the next piece of work with the user, and then resume the paused work.…