Menu

Individual skill

work-state-and-delivery

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.

plugins/yfge/agent-harness-skills/skills/work-state-and-delivery/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,533
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.