godoctor

Pre-release checklist and quality gate to verify codebase health, docs, and security before interacting with Git. Activate when preparing to tag/publish a release, concluding milestones, or running final verification on a pull request.

Guidelines, best practices, and templates for authoring Architecture Decision Records (ADRs). Activate when proposing major architectural changes, resolving design/technical debates, or documenting codebase refactorings.

Core engineering workflow standards detailing the 2x2 prioritization matrix, RFC/ADR planning, and the 7-tier Evidence Hierarchy for research. Activate at the start of any task, when designing features, refactoring, dealing with technical ambiguity, performing research, or setting quality gates.

Guidelines and conventions for bootstrapping Go modules, project structures, and reliable production patterns (HTTP servers, database connections). Activate on module initialization, new service creation, layout scoping, or setup requests.

Guidelines and procedures for querying, verifying, and upgrading Go module dependencies and toolchains. Activate when adding or upgrading Go packages, auditing go.mod, addressing dependency vulnerabilities, or verifying toolchain versions.

Highly actionable step-by-step checklist for diagnosing and resolving Go compilation errors, type errors, build/test failures, and runtime issues. Activate on any build or execution failure.

Guidelines and templates for authoring Request for Comments (RFCs). Activate when proposing significant features/refactorings, exploring design alternatives under high ambiguity, or gathering technical consensus.

Guidelines and templates for structuring software development goals and ideas into actionable, bounded tasks using Context/Todo/AC, enforced by the DoR gate. Activate when scoping user requests, decomposing RFCs into tasks, or creating a new task file.