validate-plan SKILL.md skillA
validate-plan from coalesce-labs/catalyst is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add coalesce-labs/catalyst/validate-plan@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- coalesce-labs/catalyst
- Path
plugins/dev/skills/validate-plan/SKILL.md- Versions recorded
- 7
- Latest version
- v1.0.0, committed Sep 13, 2026
- First version recorded
- Apr 5, 2026
- Size
- 8,644 bytes
- Repository stars
- 20
- License
- none declared
Validate that implementation plans were correctly executed. **ALWAYS use when** the user says 'validate the plan', 'check if the plan was implemented correctly', 'verify the implementation', or after completing /implement-plan to confirm all phases were properly executed and success criteria met.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Validate Plan
You are tasked with validating that an implementation plan was correctly executed, verifying all success criteria and identifying any deviations or issues.
## Prerequisites
```bash
# Thoughts must exist for this skill's documents. CTL-2306: the full host setup check (daemon,
# registry, house rules) belongs to the setup-catalyst skill, not to a skill that must run anywhere.
[[ -e thoughts/shared ]] || echo "⚠️ thoughts/shared is missing in $(pwd) — run \`humanlayer thoughts init\` or the setup-catalyst skill; if the prompt names an output path, write there" >&2
# CTL-2306 explicit-input discovery: begin
# Find the plan to validate on disk for the ticket this run was given: $CATALYST_TICKET under a
# phase, else a ticket named in the skill's argument text (Claude Code substitutes the token in
# the heredoc below; another harness leaves it literal, which names no ticket). Nothing is
# remembered between runs. `[!0-9]` keeps PROJ-1 from matching PROJ-10's documents.
TICKET_ID="${TICKET_ID:-${CATALYST_TICKET:-}}"
if [[ -z "$TICKET_ID" ]]; then
SKILL_ARGS=$(cat <<'CATALYST_SKILL_ARGS'
$ARGUMENTS
CATALYST_SKILL_ARGS
)
…Read the whole file at its exact version.
How to install
mdr add coalesce-labs/catalyst/validate-plan@sha256:3e7801c9cfb7279aThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qaliuzfkm6phfiht)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Apr 5, 2026 and Sep 13, 2026, about one every 27 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-09-13 | 7d94601 | 8,644 B | A | view · diff |
| v1.0.0 | 2026-09-13 | c0de85b | 8,454 B | A | view · diff |
| v1.0.0 | 2026-08-28 | 2202f79 | 7,568 B | A | view · diff |
| v1.0.0 | 2026-04-29 | 870e84e | 7,568 B | A | view · diff |
| v1.0.0 | 2026-04-11 | f9e69f2 | 7,567 B | A | view · diff |
| v1.0.0 | 2026-04-09 | 70a2d8d | 7,541 B | A | view · diff |
| git:20260405.389788d | 2026-04-05 | 389788d | 7,241 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8644 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
coalesce-labs/catalyst · 20 stars · license none declared · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qaliuzfkm6phfiht GET https://markdownregistry.com/api/v1/resolve?ref=coalesce-labs/catalyst/validate-plan GET https://markdownregistry.com/api/v1/blob/3e7801c9cfb7279ae0e6142b5bf08ef3834b73b1b9a65deee3f657eee028a2a6
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from coalesce-labs/catalyst
Every file in coalesce-labs/catalyst