PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
A skill your agent uses when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or…
Install Work State And Delivery
$ npx skills add hashgraph-online/awesome-codex-plugins --skill work-state-and-delivery -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins work-state-and-delivery --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/yfge/agent-harness-skills/skills/work-state-and-delivery .claude/skills/work-state-and-delivery && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "work-state-and-delivery" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/yfge/agent-harness-skills/skills/work-state-and-delivery into .claude/skills/work-state-and-delivery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-state-and-delivery", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/yfge/agent-harness-skills/skills/work-state-and-deliveryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill work-state-and-delivery -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins work-state-and-delivery --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/yfge/agent-harness-skills/skills/work-state-and-delivery .agents/skills/work-state-and-delivery && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "work-state-and-delivery" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/yfge/agent-harness-skills/skills/work-state-and-delivery into .agents/skills/work-state-and-delivery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-state-and-delivery", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill work-state-and-delivery -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins work-state-and-delivery --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/yfge/agent-harness-skills/skills/work-state-and-delivery .cursor/skills/work-state-and-delivery && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "work-state-and-delivery" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/yfge/agent-harness-skills/skills/work-state-and-delivery into .cursor/skills/work-state-and-delivery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-state-and-delivery", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hashgraph-online/awesome-codex-plugins.git --path plugins/yfge/agent-harness-skills/skills/work-state-and-delivery--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill work-state-and-delivery -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins work-state-and-delivery --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/yfge/agent-harness-skills/skills/work-state-and-delivery .gemini/skills/work-state-and-delivery && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "work-state-and-delivery" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/yfge/agent-harness-skills/skills/work-state-and-delivery into .gemini/skills/work-state-and-delivery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-state-and-delivery", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hashgraph-online/awesome-codex-plugins work-state-and-deliveryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hashgraph-online/awesome-codex-plugins --skill work-state-and-delivery -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/yfge/agent-harness-skills/skills/work-state-and-delivery .github/skills/work-state-and-delivery && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "work-state-and-delivery" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/yfge/agent-harness-skills/skills/work-state-and-delivery into .github/skills/work-state-and-delivery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-state-and-delivery", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill work-state-and-delivery -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins work-state-and-delivery --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/yfge/agent-harness-skills/skills/work-state-and-delivery .opencode/skills/work-state-and-delivery && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "work-state-and-delivery" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/yfge/agent-harness-skills/skills/work-state-and-delivery into .opencode/skills/work-state-and-delivery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "work-state-and-delivery", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
work-state-and-delivery- GitHub stars
- 1.3k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 602 words
- Files
- 3 (incl. references)
- Skills in repo
- 716
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or…
- Works in 7 steps: Search for design docs, tasks.md, issue… → Map each existing surface by… → If a required role is missing, bootstrap… → …
- Reconciling design docs
- SKILL.md covers Overview, When To Use, Inputs Needed and Execution Order, plus 5 more sections
- Calls git
What it does
Work State And Delivery is an agent skill from hashgraph-online/awesome-codex-plugins. Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/build-when-missing.md` and `references/delivery-and-commit-policy.md`).
It sits in Development, covering Architecture decision records. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.
When your agent uses it
- Reconciling design docs
- External trackers
- Execution plans
- Delivery records
Example prompts
- “/work-state-and-delivery”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Search for design docs, tasks.md, issue references, execution plans, review templates, ledgers, release notes, and commit guidance.
- Map each existing surface by responsibility rather than filename: design explains why and how; work state owns current status and…
- If a required role is missing, bootstrap only the minimum surface from references/build-when-missing.md; do not add a ledger or repo-local…
- Define update order: design decision first, work-state and acceptance second, execution-plan status third, delivery evidence after…
- When a change completes, changes, or invalidates a tracked task, include its task-state update in the same logical commit or authoritative…
- Define exact-path staging, validation evidence, artifact identity, and explicit skip rules in repository guidance; avoid a standalone…
- Keep delivery records concise and evidence-oriented; reference prompts or goals, changes, validation, artifacts, risks, tasks, reviews…
What it can do on your machine
Read from SKILL.md and the folder at commit 3e1456a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Work State And Delivery loads about 1.3k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 602 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from hashgraph-online/awesome-codex-plugins at commit 3e1456a, republished under its Apache-2.0 licence (© hashgraph-online). 602 words, ~1,283 tokens.
Download SKILL.mdSave it as
.claude/skills/work-state-and-delivery/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- work-state-and-delivery
- description
- Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
Work State And Delivery
Overview
Keep intent, current work state, acceptance criteria, and delivery evidence connected without creating duplicate sources of truth.
This optional governance skill combines planning surfaces and delivery ledgers because they meet at task-to-change traceability. It also owns repository commit-coupling policy, but it should not load for an ordinary commit that already follows clear repository rules. For shared harness terms, see ../../references/harness-patterns.md; when governance surfaces are missing, use references/build-when-missing.md; for delivery, skip, artifact, and commit rules, use references/delivery-and-commit-policy.md.
When To Use
- The user asks where requirements, design decisions, tasks, acceptance criteria, or execution plans should live.
- A repository needs a task board, external-tracker mapping, delivery record, handoff note, or review evidence policy.
- Design docs, task state, ledgers, reviews, and commits duplicate or contradict each other.
- The user asks to design commit coupling, exact-path staging, task-state updates, or delivery-artifact policy for the repository.
Do not use this skill solely for git status, a read-only diff, or a normal commit when the repository already defines those rules.
Inputs Needed
- Current requirement or delivery goal.
- Existing design docs, issue tracker or task file, execution plans, review template, ledger, and commit policy.
- Validation results, artifact references, task IDs, commits, risks, and required audit level.
Execution Order
- First: Map existing design, work-state, execution-plan, ledger, review, and commit-policy surfaces.
- Then: Assign one owner for each kind of truth and define update, coupling, skip, and redaction rules.
- Finally: Output the minimum governance changes, acceptance criteria, and delivery evidence required for the repository profile.
Step-by-Step Process
- Search for design docs,
tasks.md, issue references, execution plans, review templates, ledgers, release notes, and commit guidance. - Map each existing surface by responsibility rather than filename: design explains why and how; work state owns current status and acceptance; an execution plan coordinates complex work; delivery evidence records what changed and what was proved.
- If a required role is missing, bootstrap only the minimum surface from
references/build-when-missing.md; do not add a ledger or repo-local task file when an external system already satisfies the role. - Define update order: design decision first, work-state and acceptance second, execution-plan status third, delivery evidence after validation.
- When a change completes, changes, or invalidates a tracked task, include its task-state update in the same logical commit or authoritative external-tracker update.
- Define exact-path staging, validation evidence, artifact identity, and explicit skip rules in repository guidance; avoid a standalone commit skill for routine execution.
- Keep delivery records concise and evidence-oriented; reference prompts or goals, changes, validation, artifacts, risks, tasks, reviews, and commits without storing private transcripts.
Show full SKILL.md (177 more words)Show less
Checks
- Ownership: each conclusion, status, and delivery claim has one authoritative surface.
- Acceptance: active tasks have executable acceptance criteria.
- Coupling: relevant task-state and delivery updates travel with the logical change or authoritative tracker update.
- Scope: exact-path staging and one-logical-purpose commits prevent unrelated work from entering delivery.
- Evidence: delivery claims match commands and artifacts that actually exist.
- Privacy: records omit secrets, private transcripts, sensitive payloads, and large temporary artifacts.
- Overhead: optional ledgers, local task files, and execution plans are not added without a repository need.
Output Format
# Work State And Delivery
## Detected Mapping
- design source:
- work-state:
- execution plan:
- ledger / review:
- commit policy:
- validation / artifacts:
## Source-Of-Truth Responsibilities
-
## Update And Commit Coupling
-
## Acceptance Criteria
-
## Delivery Evidence
-
## Skip / Redaction Policy
-Common Mistakes
- Creating
tasks.mdwhen a reliable external tracker already owns work state. - Letting a ledger replace task status or acceptance criteria.
- Writing diaries instead of concise validation and risk evidence.
- Requiring every small commit to create task, plan, and ledger churn.
- Using
git add .in a mixed worktree or recording delivery claims without proof.
Example Prompts
- "Should this requirement live in a design doc, issue tracker, or execution plan?"
- "Unify our task state, review evidence, and handoff policy."
- "Define how tracked task updates and delivery artifacts should couple to commits."
© hashgraph-online, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in plugins/yfge/agent-harness-skills/skills/work-state-and-delivery of hashgraph-online/awesome-codex-plugins.
- SKILL.md
- references/build-when-missing.md
- references/delivery-and-commit-policy.md
Open the folder on GitHubat commit 3e1456a
Compare with similar skills
Work State And Delivery next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Work State And Delivery this skillhashgraph-online/awesome-codex-plugins | 1.3k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 381 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Architecture DecisionDonchitos/Claude-Code-Game-Studios | 26k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Improve Codebase Architectureywwynm/EverythingDone | 144 | 15 repos | ~1.3k | Automated safety check: Pass | GPL-3.0 | |
| Domain Modelingbrim-borium/spotify_sdk | 166 | 5 repos | ~806 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Architecture Decision
Donchitos/Claude-Code-Game-Studios
Create an ADR documenting a technical decision: context, alternatives considered, consequences.
Improve Codebase Architecture
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
Design Doc Mermaid
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
More from hashgraph-online/awesome-codex-plugins
All 716 skills in this repoAnime Reaction Gif
hashgraph-online/awesome-codex-plugins
Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.
Calibredb
hashgraph-online/awesome-codex-plugins
Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).
Rust API Test Harness
hashgraph-online/awesome-codex-plugins
A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…
Art
hashgraph-online/awesome-codex-plugins
Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…
Calle
hashgraph-online/awesome-codex-plugins
Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.
Game Balance Economy
hashgraph-online/awesome-codex-plugins
Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.
Related
Categories
Questions about Work State And Delivery
What does Work State And Delivery do?
A skill your agent uses when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or…. Work State And Delivery is an agent skill from hashgraph-online/awesome-codex-plugins. Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
When should I use Work State And Delivery?
Work State And Delivery fits situations like: reconciling design docs; external trackers; execution plans; delivery records.
How do I install Work State And Delivery in Claude Code?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill work-state-and-delivery -a claude-code`. Or copy the skill folder (plugins/yfge/agent-harness-skills/skills/work-state-and-delivery in hashgraph-online/awesome-codex-plugins) into .claude/skills/work-state-and-delivery in your project. Claude Code loads it when a task matches its description.
How do I install Work State And Delivery in Codex?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill work-state-and-delivery -a codex`. Or copy the skill folder (plugins/yfge/agent-harness-skills/skills/work-state-and-delivery in hashgraph-online/awesome-codex-plugins) into .agents/skills/work-state-and-delivery in your project. Codex loads it when a task matches its description.
Can I use Work State And Delivery in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill work-state-and-delivery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/work-state-and-delivery, .gemini/skills/work-state-and-delivery, .github/skills/work-state-and-delivery and .opencode/skills/work-state-and-delivery in your project.
What does Work State And Delivery need to run?
Going by SKILL.md and its folder, Work State And Delivery needs the command-line tools its instructions call (git).
Does Work State And Delivery access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Work State And Delivery safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Work State And Delivery use?
Work State And Delivery is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Work State And Delivery use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.
What are the alternatives to Work State And Delivery?
Skills that share tags, products or a category with Work State And Delivery: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars), Architecture Decision (Donchitos/Claude-Code-Game-Studios, 26k stars) and Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Work State And Delivery?
hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,267 GitHub stars. The repository holds 716 skills in this directory. The repository was last updated on October 10, 2026.
Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.