proceed
Proceed Command
Execute the provided implementation plan with surgical precision.
CRITICAL: This is an EXECUTION task. Implement changes exactly as specified in the plan.
Process
-
Review the Plan: Analyze the provided implementation plan and critical files. Understand the architectural decisions and sequence of operations before writing any code.
-
Execute Surgically:
- Implement changes step-by-step as outlined in the plan.
- Use
ast-grep(preferred) or the Edit tool for code transformations. - Follow the Find -> Transform -> Verify workflow.
- Complete each task in the plan sequentially. Batch independent operations where possible, but never batch dependent ones.
-
Verify After Each Step:
- After each file modification, use
difftto inspect changes and ensure no unintended modifications. - If the project has build/lint/test commands available, run them to catch regressions early.
- If verification fails, debug and fix before proceeding to the next step.
- After each file modification, use
More from outlinedriven/odin-claude-plugin
ast-grep
Effective code search, analysis, and refactoring using ast-grep (sg). Use this skill for precise AST-based code modifications, structural search, and linting.
2askme
Verbalized Sampling (VS) protocol for deep intent exploration before planning. Use when starting ambiguous or complex tasks, when multiple interpretations exist, or when you need to explore diverse intent hypotheses and ask maximum clarifying questions before committing to an approach.
1inits
Analyze a codebase and create or improve an AGENTS.md file for future agent instances. Use when onboarding to a repository and capturing hard-to-rediscover conventions, constraints, and rationale.
1plans
Software architect and planning specialist - conduct thorough read-only planning before any action. Use when exploring a codebase to design implementation plans, defining objectives, gathering relevant files, and summarizing available tools before coding begins.
1reviews
Review the code changes on the current branch. Use when the user asks to review their current work, analyze recent commits, or get a code quality assessment of the active branch against the main branch.
1resolve
Resolve code review comments by verifying their validity and proposing multiple solutions for confirmed issues. Use when addressing review feedback, analyzing whether review comments are valid, and generating architectural solutions (not naive fixes) for confirmed issues.
1