OpenParable
Skip to content
← Back to skills

Session Opening

Productivity
session-opening

Session Opening is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Start a session with context from previous work. Triggers on /open, 'what were we working on', 'where did we leave off', or session start. Pairs with /ground and /close. (user)

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/session-opening/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/session-opening, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

/open

Orient to previous work, then act on what's next.

Structure

Gather  → script + optional beads gate
Orient  → "here's where we left off"
Decide  → user picks direction
Act     → draw-down to TodoWrite

1. Gather

Run the context gathering script (from the session-management skill directory):

~/.claude/skills/session-management/scripts/open-context.sh

Script outputs: HANDOFF, GIT, BEADS (if present), UPDATE_NEWS context.

Gate check: If GATE_REQUIRED=true and beads skill is available:

Skill(beads)

Do not proceed until loaded. This ensures draw-down patterns are available.


2. Orient

Synthesize what matters from script output:

  • Lead with handoff — Done, Next, any Gotchas
  • Surface commands — if Commands section exists, offer to run them
  • Note scope mismatches — if handoff "Next" doesn't match bd ready, flag it
  • Beads ready — what's unblocked

Keep it brief. Orientation, not full briefing.


3. Decide

User picks direction:

  • A specific bead from ready list
  • Continue from handoff's "Next"
  • Something else entirely

4. Act

Draw-down is mandatory. When user picks a bead:

  1. bd show <bead-id> --json — read design and acceptance criteria
  2. Create TodoWrite items from acceptance criteria
  3. Show user: "Breaking this down into: [list]. Sound right?"
  4. Mark bead in_progress: bd update <id> --status in_progress

No TodoWrite items = No work. This creates checkpoints where drift gets caught.


Graceful Degradation

Not all features require all dependencies:

ComponentIf missing...
Handoff archiveSkip handoff section
Beads/bdSkip beads section, no gate required
Update newsSkip news section

The core pattern (Gather → Orient → Decide → Act) works with just git status.


Mirrors

Phase/open/ground/close
GatherHandoff, beads, scriptTodos, beads, driftTodos, beads, git, drift
Orient"Where we left off""What's drifted"Reflect (AskUserQuestion)
DecideUser picks directionContinue or adjustCrystallize actions (STOP)
ActDraw-down → TodoWriteUpdate beads, resetExecute, handoff, commit