proceed

Execute predefined implementation plans with per-step verification and optional VCS steps.

5|2|Updated Nov 17, 2025
One-click install
npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill proceed-outlinedriven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proceed
Source: https://github.com/OutlineDriven/odin-gemini-cli-extension/tree/main/skills/proceed
Command: npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill proceed-outlinedriven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates the execution of a predefined implementation plan on a codebase with strict adherence to steps, and ensures verification after each operation to prevent drift.

Core Features & Use Cases

  • Review Plan: Analyze the provided plan and confirm the sequence of changes.
  • Execute Surgically: Implement changes step-by-step exactly as specified, using available tooling for guided transformations.
  • Verify After Each Step: Use difft and other checks to validate modifications before proceeding.
  • Finalize: Run final verification (build/lint/tests) and prepare for optional VCS tasks if requested.

Quick Start

Apply the provided implementation plan to modify the project exactly as specified, then verify changes after each step.

Frequently Asked Questions about proceed

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute a predefined implementation plan on a codebase step-by-step?

To execute a predefined implementation plan on a codebase, apply the specified changes sequentially, use guided tooling for surgical code transformations, and run difft after each modification to prevent drift.

What is the best way to verify code changes after each step of an implementation plan?

The best way to verify code changes after each step is to run difft and other validation checks immediately after applying modifications, ensuring strict adherence to the plan before moving to the next operation.

Can I finalize code modifications and prepare for VCS tasks after completing a plan execution?

Yes, you can finalize code modifications by running final verification steps like build, lint, and tests, and then prepare for optional version control system (VCS) tasks to commit the verified changes.

How do I review an implementation plan to confirm the sequence of code changes?

Review an implementation plan by analyzing the provided artifacts to confirm the exact sequence of code changes required, ensuring disciplined steps and strict adherence before executing any modifications on the codebase.

Why does surgical code execution require verification tooling like difft and lint?

Surgical code execution requires verification tooling like difft and lint to validate modifications after each step, preventing drift and ensuring that the applied changes match the plan exactly before finalization.

Do I need a plan artifact to apply surgical code changes to my project?

Yes, you need a plan artifact to apply surgical code changes, as the execution requires a predefined implementation plan to guide step-by-step transformations and ensure strict adherence to the specified modifications.