Skip to content
Skills Library
AI & agents · Planning

work-session

/work-session

Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).

Repository
pokayokay ↗
Licence
MIT
Last repository change
28.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
21
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).

Original author description

Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).

How it works

  1. When NOT to Use
  2. Key Principles
  3. Quick Start Checklist
  4. Operating Modes
  5. References
  6. Runtime Notes
Original SKILL.md headings · 67 lines, 534 words
SKILL.md preview
---
name: work-session
description: Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).
disable-model-invocation: true
---

# Work Session

Orchestrate AI-assisted development with configurable human control, using ohno for task management via MCP.

## When NOT to Use

- **Planning work** — Use `planning` to create epics/stories/tasks before starting sessions
- **Quick one-off tasks** — Use `/quick` for simple tasks that don't need the full subagent pipeline
- **Revising a plan** — Use `plan-revision` to modify scope, dependencies, or task hierarchy
- **Running a spike** — Use `spike` for time-boxed investigation before committing to implementation

## Key Principles

- Fresh context per task via subagent dispatch (no context degradation)
- Configurable checkpoint control: supervised, semi-auto, auto, or unattended
- Smart worktree isolation by task type (feature/bug → worktree, chore/docs → in-place)
- Hooks handle lifecycle automatically (sync, commit, tests)
- ohno MCP provides session continuity across conversations
- Evidence before completion claims (`verification-before-completion`)
- Root-cause-first bug handling (`systematic-debugging`)
- Explicit branch finish choice: merge, PR, keep, or discard (`finishing-branch`)
- Token-aware dispatch: stay inline for tiny work, use focused agents when isolation or parallelism is worth the cost

## Quick Start Checklist

1. Initialize ohno: `npx @stevestomp/ohno-cli init`
2. Get session context: MCP `get_session_context()`
3. Get next task: MCP `get_next_task()`
4. Dispatch subagent for implementation
5. Review results at checkpoints (based on mode)

## Operating Modes

| Mode | Task Complete | Story Complete | Epic Complete |
|------|--------------|----------------|---------------|
| supervised | PAUSE | PAUSE | PAUSE |
| semi-auto | log | PAUSE | PAUSE |
| auto | skip | log | PAUSE |
| unattended | skip | skip | skip |

## References

| Reference | Description |
|-----------|-------------|
| [dispatch-preparation.md](references/dispatch-preparation.md) | Task extraction, brainstorm gate, design review gate, skill routing, template filling |
| [review-pipeline.md](references/review-pipeline.md) | Two-stage review: spec compliance then code quality (+ design compliance) |
| [dispatch-errors.md](references/dispatch-errors.md) | Recovery when ohno, routing, or dispatch fails |
| [checkpoint-types.md](references/checkpoint-types.md) | PAUSE, REVIEW, NOTIFY checkpoint patterns |
| [skill-routing.md](references/skill-routing.md) | Task type to skill mapping |
| [operating-modes.md](references/operating-modes.md) | Supervised, semi-auto, auto, unattended details |
| [worktree-management.md](references/worktree-management.md) | Setup, completion, merge/PR workflows |
| [parallel-execution.md](references/parallel-execution.md) | Parallel Execution: benefits, tradeoffs, dependency handling |
| [hook-integration.md](references/hook-integration.md) | Work loop with hooks, mode-specific behavior |
| [ohno-integration.md](references/ohno-integration.md) | MCP tools and CLI commands reference |
| [error-recovery.md](references/error-recovery.md) | Build failures, blocked tasks |
| [approval-policy.md](references/approval-policy.md) | Runtime approval defaults for safe pokayokay automation |
| [token-budgeting.md](references/token-budgeting.md) | Token/context budgeting rules for agents, skills, parallelism, and handoffs |
| [anti-patterns.md](references/anti-patterns.md) | Common mistakes and fixes |
| [bug-fix-pipeline.md](references/bug-fix-pipeline.md) | Agent pipeline for `/fix --thorough` and `/hotfix` commands |
| [pre-flight-checks.md](references/pre-flight-checks.md) | Checks run before unattended/headless sessions |

## Runtime Notes

- **Claude Code**: the coordinator dispatches yokay-brainstormer, yokay-design-reviewer, yokay-implementer, yokay-fixer, yokay-spec-reviewer, yokay-quality-reviewer, yokay-browser-verifier, and yokay-auditor via the Task tool with `subagent_type: "pokayokay:yokay-<name>"`, as described in [dispatch-preparation.md](references/dispatch-preparation.md).
- **Codex**: there is no subagent dispatch. Run the pipeline inline in the current session — for each stage, read the corresponding `agents/yokay-<name>.md` and follow its Behavioral Defaults, Critical Rules, and Output Contract. Execute stages (design review (conditional) → implement → spec review → quality review) as separate, sequential passes; do not skip review stages because dispatch is unavailable. Parallel batch execution ([parallel-execution.md](references/parallel-execution.md)) is Claude Code-only — process tasks sequentially on Codex.
Files in this package (21)
  • SKILL.md 5 KB
  • eval-log.md 52 KB
  • eval.json 16 KB
  • references/anti-patterns.md 1 KB
  • references/approval-policy.md 2 KB
  • references/bug-fix-pipeline.md 8 KB
  • references/chain-state.md 11 KB
  • references/checkpoint-types.md 10 KB
  • references/dispatch-errors.md 3 KB
  • references/dispatch-preparation.md 12 KB
  • references/error-recovery.md 2 KB
  • references/hook-integration.md 2 KB
  • references/kaizen-review-failures.md 6 KB
  • references/ohno-integration.md 1 KB
  • references/operating-modes.md 1 KB
  • references/parallel-execution.md 3 KB
  • references/pre-flight-checks.md 1 KB
  • references/review-pipeline.md 5 KB
  • references/skill-routing.md 4 KB
  • references/token-budgeting.md 4 KB
  • references/worktree-management.md 3 KB

Versions

RepositoryScoreLicence
This page · srstomp/pokayokay90MIT
seattle78/AgentQuest100Apache-2.0
srstomp/pokayokay85MIT

Database snapshot: 13.11.2026 · package version 92a6021b0f76 (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

  • 81deep-resume
    Use when resuming an interrupted or parked deep-work session from its current phase.
  • 100coordinating-multi-model-work
    Use for coordinated work: multi-phase or multi-component changes, risky or design-dependent work, or any request for a plan. Load it before any Plan, Execute, or Review action and when resuming an interrupted plan. Covers Refract setup, routing, job lifecycle, independent…
  • 90continue-claude-code-work
    Continues interrupted Claude Code work after local history is read and reconciled — reconstructs the original outcome, unfulfilled requests, and the next action. Use when given a Claude Code Session ID, asked to pick up prior Claude work, told a run was interrupted or compacted,…
  • 100session-management
    Manages Claude Code sessions with naming, checkpointing, and resume strategies. Use when organizing long-running work or resuming across sessions.
  • 100orchestrating-session-work
    Use when work will be distributed to sibling Claude Code sessions, before the first cross-session message. Takes the work items plus the session topology; returns a stated distribution strategy, dispatched handoffs, and per-item adjudicated closure with an explicit stand-down to…
  • 100orchestrating-subagent-work
    Use for substantial implementation or review work — multi-file changes, review rounds, verification passes — including when the work arrives as an assignment message from another session; invoke before the first codex dispatch, subagent spawn, or inline write. Takes the task…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.