write-manual-verification-plan
v1.0.0Write a numbered, resumable checklist for checks run by hand, where every step says what to do, what you should see, and how to tell nothing from broken.
By Christopher BooneLicense: MIT2 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 1 skill or MCP entry
- Source updated
- Sep 16, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install write-manual-verification-plan for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install write-manual-verification-plan-2@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/cboone/agent-harness-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/write-manual-verification-plan/.
Plugin files
├── .claude-plugin/plugin.json└── skills/write-manual-verification-plan/SKILL.md
Included Skills1
Write a numbered, resumable checklist for the checks a human has to run by hand, in a DAW, a simulator, a browser, or on a device, where every step gives the setup, the action, the exact observation to expect, and how to tell "nothing happened, as intended" from "the instrument was not running". Use whenever by-hand verification is the subject, not only when invoked explicitly: (1) asked what can be verified manually, what host verification needs, or what to test, (2) writing the manual verification section of a plan or phase gate, (3) asked to list or reprint verification steps, (4) receiving partial results in free text, such as "4's confirmed, skipping 5 and 6, 7 gave 1.0894", (5) someone is unsure what a step is looking for, (6) splitting a checklist across sessions or around an exclusive resource. Covers the step format, build confirmation, null-versus-broken controls, persisting to a plan or issue, resuming, and recording measured readings.
Plugin manifests1
{
"author": {
"name": "Christopher Boone"
},
"description": "Write a numbered, resumable checklist for checks run by hand, where every step says what to do, what you should see, and how to tell nothing from broken.",
"homepage": "https://github.com/cboone/agent-harness-plugins",
"keywords": [
"checklists",
"manual-testing",
"planning",
"resumable",
"verification"
],
"license": "MIT",
"name": "write-manual-verification-plan",
"repository": "https://github.com/cboone/agent-harness-plugins",
"skills": "./skills",
"version": "1.0.0"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[write-manual-verification-plan on Agent Plugins Marketplace](https://pluginsmp.com/plugins/write-manual-verification-plan-2)