Dry Walkthrough
Plan validation executor. ALWAYS invoke this skill when instructed to validate or dry-walkthrough a plan. Do not read the plan or trace changes directly — use this skill first to load the validation workflow.
Install
npx skills add TalonT-Org/AutoSkillit --skill dry-walkthroughgit clone --depth 1 https://github.com/TalonT-Org/AutoSkillit.git /tmp/AutoSkillit
mkdir -p ~/.claude/skills
cp -r /tmp/AutoSkillit/src/autoskillit/skills_extended/dry-walkthrough ~/.claude/skills/dry-walkthroughPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Dry Walkthrough Skill
Validate a proposed implementation plan by performing a dry walkthrough of each change without implementing. Fix issues directly in the plan and report what changed to the terminal.
## Key Principle
The plan file must remain a **clean, self-contained implementation instruction set**. No gap analysis, no commentary, no "issues found" sections in the plan itself. All reporting goes to terminal output.
**Your role is technical validation, not strategic decision-making.** Fix factual inaccuracies (wrong file paths, nonexistent functions, incorrect line numbers). Preserve all goals and scope.
## When to Use
- User says "dry walkthrough", "drywalkthrough", "dry walk", "dry run"
- User wants to "validate plan" or "check plan"
- User says "before implementing" and wants verification
- After creating a plan, before implementation
## Arguments
`{plan_path}` — Absolute path to the plan file to validate (optional: falls back to most recent {{AUTOSKILLIT_TEMP}}/ artifact if omitted)
## Critical Constraints
**NEVER:**
- Modify any source code files
- Implement any part of the plan
- Add backward compatibility to the plan
- Add fallback mechanisms
- Write gap analysis or commentary INTO the plan file
- Add a rollback plan
- Add deprecation notes, stubs, code, warnings
- Include alternative approaches that will not be part of implementation in plan
- Remove or defer goals or phases from the planDetails
- Skill name
dry-walkthrough- Repository
- TalonT-Org/AutoSkillit
- Path
src/autoskillit/skills_extended/dry-walkthrough/SKILL.md- License
- MIT
- Repo updated
- 8 November 2026
FAQ
What does the Dry Walkthrough skill do?
Plan validation executor. ALWAYS invoke this skill when instructed to validate or dry-walkthrough a plan. Do not read the plan or trace changes directly — use this skill first to load the validation workflow.
How do I install the Dry Walkthrough skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add TalonT-Org/AutoSkillit --skill dry-walkthrough. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Dry Walkthrough popular?
It lives in TalonT-Org/AutoSkillit, which has 5 GitHub stars and 1 forks.
Related skills
Analyze Prs
5TalonT-Org/AutoSkillit
Analyze all open PRs targeting a base branch — determine merge order, identify file overlaps, and tag each PR as simple or needs_check for complexity. Use at the start of a PR consolidation workflow.
Arch Lens C4 Container
5TalonT-Org/AutoSkillit
Create C4 Container architecture diagram showing static structure, building blocks, and technology choices. Anatomical lens answering "How is it built?
Arch Lens Concurrency
5TalonT-Org/AutoSkillit
Create Concurrency architecture diagram showing parallel execution patterns, thread pools, synchronization, and barriers. Physiological lens answering "How does parallelism work?
Make Plan
5TalonT-Org/AutoSkillit
Planning executor. ALWAYS invoke this skill when instructed to create, devise, or write an implementation plan. Do not explore the codebase or draft a plan directly — use this skill first to load the planning workflow.
Diagnose CI
5TalonT-Org/AutoSkillit
Diagnostic executor for CI failures. ALWAYS invoke this skill when instructed to diagnose CI failures. Do not fetch CI logs directly — use this skill first to load the diagnosis workflow.
Make Req
5TalonT-Org/AutoSkillit
Decompose a task, plan, roadmap, or feature description into a structured set of requirements grouped for independent planning. Use when user says "make req", "make requirements", "decompose requirements", "extract requirements", or wants to break down a task into what needs to be true.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.