Receber por email
← Voltar para o catálogo

proceed

Execute um plano de implementação com precisão cirúrgica, geralmente após uma fase de planejamento ter produzido uma estratégia passo a passo e identificado arquivos críticos. Esta skill foca em mudanças de código precisas com verificação a cada passo.

27estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add OutlineDriven/odin-claude-plugin

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/proceed/svg)](https://www.skillteca.com.br/skills/proceed)

Skills relacionadas

Ver todas de DevOps e Infra →

Alerta por categoria

Receba novas skills de DevOps e Infra toda segunda

1 email curto, só com as skills novas de DevOps e Infra. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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:
  2. Implement changes step-by-step as outlined in the plan.
  3. Use ast-grep (preferred) or the Edit tool for code transformations.
  4. Follow the Find -> Transform -> Verify workflow.
  5. Complete each task in the plan sequentially. Batch independent operations where possible, but never batch dependent ones.
  1. Verify After Each Step:
  2. After each file modification, use difft to inspect changes and ensure no unintended modifications.
  3. If the project has build/lint/test commands available, run them to catch regressions early.
  4. If verification fails, debug and fix before proceeding to the next step.
  1. Finalize:
  2. Run available build/lint/test commands for final verification.
  3. 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.

Compartilhar X LinkedIn