outlinedriven/odin-codex-plugin

proceed

Execute an implementation plan with surgical precision. Use after a planning phase (plan-now or similar) has produced a step-by-step strategy and identified critical files. Focuses on precise code changes with verification at each step.

First seen Jun 4, 2026

Installation

$ npx skills add outlinedriven/odin-codex-plugin --skill proceed

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from outlinedriven/odin-codex-plugin · top by installs.

npx skills add outlinedriven/odin-codex-plugin

Browse all from outlinedriven/odin-codex-plugin

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 15
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,902 B
  • docs SUMMARY.md 251 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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

  1. Review the Plan: Analyze the provided implementation plan and critical files. Understand the architectural decisions and sequence of operations before writing any code.
  1. 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.

  1. Verify After Each Step:

- After each file modification, use difft to 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.

  1. Finalize:

- Run available build/lint/test commands for final verification. - VCS operations (commits, branch management) only if the user explicitly requests them or the plan specifies them.

Required Output

End your response with:

Implementation Summary

  • [File path] - [Status: e.g., "Implemented & Verified"]
  • [File path] - [Status: e.g., "Updated & Tested"]

Verification Results

  • Build: [pass/fail/not available]
  • Lint: [pass/fail/not available]
  • Tests: [pass/fail/not available]

Remember: Execute the plan precisely. Follow existing patterns. Verify every change.