otaviobarros/agent-engineering
A playbook for coding agents: plan changes, implement with checks, review independently, and publish within your limits.
Implement a software change through planning, implementation, verification, independent review, remediation, and authorized delivery. Use for full implementation requests or implementation mode. Standalone phase requests stay within their own boundaries.
Implement an accepted software change plan with scoped code, tests, and documentation. Use for the implementation phase or to resume an authorized slice. Standalone implementation stops before independent review and publication.
Plan a software change or revise an existing plan. Define acceptance criteria, authorized scope, coherent slices, and verification needs. Use for planning requests; planning alone does not start implementation.
Publish a verified, reviewed change through authorized commits, push, and a draft pull request. Use for the publication phase or to resume interrupted publication. Preserve operation-specific permissions and explicit limits.
Validate review findings, fix authorized defects, and obtain correction evidence and fresh re-review. Use after a review or to resume a remediation round. Preserve existing scope and round limits; standalone remediation stops before publication.
Review a software change against requirements and project standards. Use for change, branch, or PR reviews. Return validated findings about bugs, security, and maintainability. Stop before remediation.
Review a GitHub pull request through review-change and publish validated findings as inline threads with a summary and an authorized review decision. Use for requested PR feedback or interrupted review publication; preserve report-only limits.
Set up or refresh a project's engineering workflow through codebase discovery, a guided interview, documentation proposals, and explicit workflow adoption. Preserve existing project authorities. Use for project onboarding or setup, not application implementation.
Verify a software change against acceptance criteria. Run relevant checks and report evidence, failures, and gaps. Use for verification requests or the verification phase of delivery; verification alone does not authorize fixes or publication.