work-complete is agent-read markdown (skill) from hiroro-work/claude-plugins: Work completion handler. Archives the plan file. Example: /work-complete.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Work Completion Handler
Performs cleanup at the end of a work session.
## Usage
```text
/work-complete
```
## Procedure
### 1. Archive the plan file
Move **only the plan file used in the current session** to `.claude/plans/archive/`.
- The file specified when plan mode started (e.g. `.claude/plans/lazy-riding-willow.md`)
- Do not move plan files belonging to other sessions (parallel runs may exist)
- Skip if the plan file does not exist
- The archived file remains available for reference if follow-up work is needed
```bash
# Create the archive directory if it doesn't exist
mkdir -p .claude/plans/archive
# Move the current session's plan file into the archive
mv .claude/plans/<current-session-plan-file>.md .claude/plans/archive/
```
### 2. Report completion
Report the result of the cleanup.
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_yz3bi65sqhuictmn
GET https://markdownregistry.com/api/v1/resolve?ref=hiroro-work/claude-plugins/work-complete
GET https://markdownregistry.com/api/v1/blob/6da0fafd21cef31e778dc34e57e7f1bbeb3cbb6bbedb560f3af20589a4ee8d3c
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
hiroro-work/claude-plugins · .claude/skills/dev-workflow-triage/SKILL.md · Triage open issues in the retrospective issue repo populated by the dev-workflow producer (v1 and v2 issue formats)…
hiroro-work/claude-plugins · .claude/skills/extract-skill-section/SKILL.md · Extract a named SKILL.md section's body verbatim into a references/<name>.md file, replace the body with a skeleton…
hiroro-work/claude-plugins · .claude/skills/inbox-add/SKILL.md · Read .claude/inbox-add.local.md and append one task line to the Obsidian Vault's inbox.md. Use when the user requests…
hiroro-work/claude-plugins · .claude/skills/publicity-review/SKILL.md · Review uncommitted diff for content unsuitable for publication to a public repository — secrets/credentials…
hiroro-work/claude-plugins · .claude/skills/review-with-untracked/SKILL.md · Temporarily visualize untracked new files into the git diff so a chain of diff-deriving review callees can see them…
hiroro-work/claude-plugins · .claude/skills/run-node-tests/SKILL.md · Run the repository's Node test suite under tests/ via `node --test` and report a structured verdict. Project-local…
hiroro-work/claude-plugins · .claude/skills/run-tests/SKILL.md · Verify plugins marketplace structure, version consistency, and JSON/frontmatter validity via subagent
hiroro-work/claude-plugins · .claude/skills/skill-review/SKILL.md · Review uncommitted skill changes against an internal checklist of skill-creator best practices and apply improvements…
hiroro-work/claude-plugins · .claude/skills/verify-bundle-sync/SKILL.md · Verify the dev-workflow-bundle canonical and bundle copy directories are in sync. Workaround for upstream symlink bug…
hiroro-work/claude-plugins · .claude/skills/verify-diff/SKILL.md · Empirically verify that a code diff achieves its stated objective by dispatching a bias-free executor that actually…
