Forge
muhammad-saadd/forge
Desenvolvimento assistido por IA com rigor de engenharia sênior
Ver no GitHubAgent que automatiza desenvolvimento com disciplina de engenheiro sênior, aplicando spec-first, test-driven development e commits atômicos. Organiza requisitos em planos executáveis, executa tarefas em paralelo, verifica cobertura de testes e bloqueia deploy até passing tests.
Instalação
npx convez-ai muhammad-saadd/forge1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Planejar e executar features complexas com especificação estruturada
- Implementar TDD automatizado com análise de dependências entre tasks
- Garantir qualidade antes de merge com verificação obrigatória
Veredito

Forge resolve um problema real: transformar requisitos vagos em planos executáveis e verificados. A abordagem spec-first + TDD obrigatória + parallelização inteligente é madura e bem documentada. Ideal para times que querem disciplina de engenharia sem perder velocidade.
README
A tradução para o português deste README ainda está na fila.
Forge
AI-assisted development with the discipline of a senior engineer — spec first, test-driven, atomic commits, verified before done.
For engineers who write specs, not prompts.
Install
/plugin install forge@your-marketplace
The Five Commands
/forge:plan-requirement "add OAuth login"
Analyzes codebase + asks ≤3 questions → .forge/SPEC.md
/forge:review-plan
Reviews spec, generates task dependency graph → .forge/PLAN.md
/forge:execute-plan
Git worktree + parallel execution + TDD + deviation rules → commits per task
/forge:verify-plan
Runs test suite, checks success criteria → .forge/VERIFICATION.md
/forge:ship-plan
Merges main, bumps version, updates CHANGELOG, creates PR
Blocked until verification passes
How It Works
/forge:plan-requirement → forge-analyst + forge-planner → .forge/SPEC.md
/forge:review-plan → forge-reviewer → .forge/PLAN.md
/forge:execute-plan → forge-executor (parallel) → commits per task
→ forge-debugger (on failure) → .forge/tasks/
/forge:verify-plan → forge-verifier → .forge/VERIFICATION.md
/forge:ship-plan → forge-shipper → PR URL
Context rot prevention: STATE.md is written before every agent exits. New session = 2-second orientation.
Parallel execution: Independent tasks run concurrently via dependency graph in PLAN.md.
Deviation rules (auto-enforced during execution):
- Auto-fix bugs
- Auto-add missing critical functionality (error handling, auth, rate limiting)
- Auto-fix blockers
- Checkpoint for architectural changes — requires human decision
Ship gate: /forge:ship-plan will not run until verification passes.
Project State
.forge/
├── STATE.md — current stage, progress, next action
├── CODEBASE.md — tech stack and patterns
├── SPEC.md — structured spec
├── PLAN.md — task dependency graph
├── VERIFICATION.md — test results
└── tasks/ — per-task summaries and commit hashes
Philosophy
- Spec before code — analyst reads your codebase before writing a line
- Tests before implementation — TDD enforced on tasks with testable behavior
- Atomic commits — each task gets its own commit
- Verified before shipped — ship is gated on passing verification
- Resumable always — STATE.md + session hook = instant orientation
License
MIT