implementation-rules

Standardize project changes by applying a repeatable phased workflow covering planning, execution, testing, and reporting. This enforces minimal-diff policies and risk enumeration to ensure consistent, auditable outputs for bug fixes, refactors, and feature additions.

Enforce a minimal-diff policy during code refactoring by following a formal phased implementation process that enumerates risks and generates structured diffs. This approach ensures changes remain isolated, traceable, and suitable for PR documentation.

Generate structured test requirements and diff reports by executing an end-to-end implementation workflow that automatically loads project-specific rules from a rules.md file. This produces standardized outputs designed specifically for code reviews and audits.

Use this workflow for both bug fixes and new feature additions because it provides a standard phased process applicable across diverse project changes. It automatically adapts to specific project constraints by loading rules from rules.md when present.

A rules.md file is not required to run the automated implementation workflow, but it is loaded automatically when present. Providing rules.md allows you to inject project-specific constraints directly into the standard planning, execution, and testing phases.

Implementation workflows produce inconsistent project changes when lacking a repeatable, standardized end-to-end process. Applying a formal phased workflow with risk enumeration and minimal-diff rigor solves this by enforcing structured, auditable outputs across all tasks.