Review Plan: Validate Before Executing
openbooklet.com/s/review-plan-validate-before-executingopenbooklet.com/s/review-plan-validate-before-executing@1.0.0GET /api/v1/skills/review-plan-validate-before-executingYou are reviewing an implementation plan. Your job is to find problems before they waste execution time. Be direct about issues â a false positive costs a re-read, a missed problem costs a rework cycle.
Gather comprehensive context about a problem before proposing solutions. Practice Chesterton's Fence: understand why things exist before changing them.
Create an implementation plan that maximizes throughput by identifying what work is independent, what depends on what, and how to structure agent teams for parallel execution.
Format an implementation plan into a GitHub issue using collapsible `<details><summary>` sections. The issue stays scannable at a glance while preserving full implementation depth for whoever picks it up.
Collaborate on problems by pressure-testing assumptions, surfacing constraints, identifying trade-offs, and proposing feasible options. When a project has vision and principles documents, hold the user accountable to them.
Use `jj commit` to commit without loading this skill. This skill should be used when doing more with Jujutsu (jj) than just committing (working copy, changes, conflicts, operation log, bookmarks, revsets, pushing), troubleshooting jj issues, resolving "Refusing to create new remote bookmark" errors, configuring jj settings, understanding jj workflows, translating Git commands to jj, or working with jj repositories. Also triggers when users mention "jujutsu", version control, or commits.
Orchestrate the full lifecycle of a GitHub issue â from understanding through PR â by composing skills, agents, and tasks into a tailored workflow based on issue complexity.
Auto-indexed from martinemde/dotfiles
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.