start-work

by code-yeongyu 68k Other Updated Aug 17, 2026
Workflow ⚠ No license
start-work skill by code-yeongyu
start-work — Workflow skill by code-yeongyu

start-work is an open-source workflow skill for Claude Code and compatible agents, published by code-yeongyu. Its author describes it as: “Execute a Prometheus work plan with Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and Stop-hook continuation. Use after planning when the user says start work, execute plan, continue…”. The project has 68k stars on GitHub and ships custom license terms, so review them before reuse. Add it to your setup with `git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/start-work`.

What start-work does

**YOU DO NOT WRITE CODE. YOU DO NOT EDIT PRODUCT FILES. YOU DO NOT RUN QA YOURSELF. EVERY unit of implementation, test, QA, and review work MUST be delegated to a spawned subagent. NO EXCEPTIONS.** Your hands touch only plan selection, `.omo/` state (Boulder, ledger, plan checkboxes), decomposition, dispatch, verdicts, and evidence records. About to edit a product file or run an implementation command yourself? **STOP. SPAWN A WORKER INSTEAD.** Orchestrate at **MAXIMUM PARALLELISM**: every independent unit runs concurrently; only named dependencies serialize.

Installation

Add start-work to your agent with:

git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/start-work

Always review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.

What's inside

The SKILL.md for start-work is organised into these sections:

  • ABSOLUTE RULE: YOU ARE AN ORCHESTRATOR — NEVER THE IMPLEMENTER
  • Codex Harness Tool Compatibility
  • Codex tier mapping for the delegation router
  • Codex Subagent Reliability
  • Usage
  • Goal and todo discipline (MANDATORY)
  • Phase 1: Select the plan
  • No-plan bootstrap
  • Phase 2: Create or update Boulder state
  • Parallel delivery lanes (teams and worktrees)
  • Phase 3: Execute the next checkbox
  • Monitor every dispatched subagent to its completion condition

When to use it

Reach for start-work when you want workflow help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.

Strengths

  • Ships in code-yeongyu/oh-my-openagent, an established project with 67,982 GitHub stars
  • Actively maintained (recent commits)

Things to check

  • No license declared — confirm terms with the author before reuse

Topics

aiai-agentsanthropicchatgptclaudeclaude-skillscodexcursorgeminiideopenaiopencodeorchestrationtuitypescript

Frequently asked questions

What does start-work do?
Execute a Prometheus work plan with Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and Stop-hook continuation. Use after planning when the user says start work, execute plan, continue plan, resume plan, or asks to run a .omo/plans plan.
How do I install start-work?
Run git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/start-work in your agent, then reload your skills. Review the source at https://github.com/code-yeongyu/oh-my-openagent before installing.
Is start-work free to use?
start-work is publicly available on GitHub, but code-yeongyu has not declared a standard open-source license (Other). Confirm the terms with the author before reusing it.
Where does start-work come from?
start-work ships inside code-yeongyu/oh-my-openagent, a repository that contains 46 catalogued skills in total. The repository's 67,982 GitHub stars apply to that whole collection, not to this skill on its own.

Related skills

More Workflow →

Binding ultrawork mode directive for omo-senpi. When a prompt contains ultrawork or ulw, the omo input hook injects the full directive as a hidden custom message (customType omo-ultrawork:directive, display false) ahead of the user's text, which is left untouched; a prompt queued while the agent is streaming instead carries the directive appended inside that same message. The directive is present in the conversation context; on the idle path it is not shown in the visible prompt, while a queued prompt carries the directive visibly (exactly as before this change). When the directive is already present in the conversation, do not read this file again - this file is that same directive. Read this file only when ultrawork mode is requested and the directive is not already present in the conversation.

68k code-yeongyu Other

Team-first maximum-saturation research orchestration for omo-senpi. Scopes solo, ALWAYS asks which final format to render (PDF+DOCX default), then stands up a max-size cooperating team (team_create): one member per axis plus skeptic/red-team members for ultradebate/hyperdebate cross-critique, explore/librarian lanes, live ulw-loop journaling, an EXPAND loop until leads run dry, claims proven by code or the claim-graph gate, and a cited synthesis with charts/Mermaid/assets behind visual-QA and `writing` proofread gates. ACTIVATES ONLY on an explicit user demand for research: the word 'ulw-research' ('/ulw-research', '$ulw-research'), any 'ulw' research wording, 'ultradebate' or 'hyperdebate' research requests, or an explicit request for research / deep research / an ultra-precise investigation, in any language. Never self-activates for ordinary questions, debugging, or implementation context-gathering. While active it overrides exploration-bounding defaults: exhaustive coverage is the goal.

68k code-yeongyu Other

Persistent Codex-style goal tracking for pi. Use when the user explicitly asks to set, continue, audit, pause, resume, complete, or inspect a long-running goal.

68k code-yeongyu Other

MUST USE when asked to find, read, list, search, inspect, fetch, export, or reconstruct coding-agent sessions across Codex, Claude Code/Desktop, OpenCode, OMO/Senpi/pi, oh-my-pi (omp), gajae-code (gjc), OpenClaw, Factory Droid, Amp, Gemini/Kimi/Qwen CLIs, Codebuff, Roo/Kilo/Cline, Kodu, Cursor CLI, Aider, Aside browser-agent sessions, or unknown local agent logs. Covers transcripts, session IDs, rollout JSONL, state SQLite, Claude projects/pre-compact histories, OpenCode messages/parts, child/subagent linkage, cwd/model/time/token filters, archives, and cost clues. Expands fuzzy recall into parallel query lanes and first probes known stores so absent platforms are skipped cheaply. Triggers: coding agent sessions, Codex/Claude/OpenCode/OMO/Senpi/pi/oh-my-pi/omp/gajae-code/gjc/OpenClaw/Droid/Amp/Kodu/Cursor/Aider/Aside sessions, transcript search, session history, session ID, read transcript, token usage, subagent sessions, what did I do yesterday, did we already do this.

68k code-yeongyu Other