Remediate Plan

Paths. This skill reads a file inside its own directory as ${CLAUDE_SKILL_DIR}/…. Claude Code fills that in. On any other harness, set CLAUDE_SKILL_DIR to the absolute directory that contains this SKILL.md before reading it. If you cannot, stop and report skill_dir_unresolved.

What it consumes

Load the validate-plan skill (/catalyst-dev:validate-plan; in a skills-CLI install, its SKILL.md sits in the sibling validate-plan skill directory) for the schema this skill reads — its allowed-tools, and the exact headings its "Validation Report" renders into the conversation. That report is this skill's entire input; do not re-derive or copy its contract here, since validate-plan is the owning skill and the only source that stays current when its report shape changes. See references/single-session-fix.md for a worked example of turning that report into fixes.

When to run it

Two modes, same report, same steps:

• Same-session (laptop): right after a /catalyst-dev:validate-plan run in this session reported FAIL or PARTIAL — its Validation Report is sitting in the conversation.
• Fresh session (cloud dispatch): the session was dispatched to remediate a validate failure and the persisted Validation Report is a real file on disk — primarily a materialized prior-artifact file (the runner fetches the failed validate phase's validation.md from the R2 artifact store and your dispatch prompt names its local path); failing that, a thoughts doc or Linear attachment the prompt points at.

If no Validation Report is in context and no report file is named in your prompt, run /catalyst-dev:validate-plan first, in this session, before invoking this skill.

Steps