session-control_skill

Overview

This skill controls session resume and fork behavior for the /work workflow. It toggles session state based on --resume and --fork flags and updates session artifacts used inside autonomous development cycles. Do NOT load this skill for user session management, login state, or general app state handling.

How this skill works

The skill inspects variables passed from the workflow to determine whether to resume or fork the current session. It runs a shell helper (scripts/session-control.sh) with the appropriate arguments, then validates that session.json and session.events.jsonl were updated as expected. It is designed strictly for internal workflow orchestration within the Plan→Work→Review loop.

When to use it

• Switching a work session into resume mode from a workflow step
• Forking a session to create an independent branch of work state
• Automating session-state transitions inside CI-style development pipelines
• Coordinating session artifacts between autonomous task stages

Best practices

• Only invoke from trusted workflow steps; do not expose to end-user flows
• Pass explicit flags (--resume or --fork) and validate inputs before execution
• Ensure scripts/session-control.sh is executable and checked into the workflow image
• Verify session.json and session.events.jsonl integrity after the script runs
• Keep this skill out of authentication, login, or general app state code paths

Example use cases

• A workflow step resumes a paused developer session to continue a Plan→Work→Review cycle
• Creating a forked session when branching experiment work without altering the main session
• Automating session artifact updates as part of nightly autonomous testing
• Chaining multiple autonomous tasks where each task may resume or fork state