pg-implement

To enforce strict commit-linked planning for PostgreSQL backend changes, use a phase-by-phase execution workflow that validates file:line citations, requires per-phase testing, and formats commit messages to upstream PostgreSQL standards.

Automated test verification for PostgreSQL feature integration works by applying R1-R12 discipline rules that require per-phase testing, ensuring every implementation phase is tested, documented, and committed before proceeding to the next.

The best way to break complex database changes into verifiable phases is through a structured execution workflow that enforces strict planning, automated test verification, and upstream-compatible commit message standards for each phase.

Yes, you need a planning directory slug to start PostgreSQL feature implementation. Providing the slug initiates the phase-by-phase execution of your PostgreSQL feature plan and applies the necessary discipline rules.

Your PostgreSQL patch submission workflow needs file:line citation verification to maintain the integrity of the PostgreSQL source tree and ensure the implementation is bisectable, consistent, and error-free.

Yes, you can use phase-by-phase execution for adding a new GUC or SQL keyword to PostgreSQL. It ensures every plan phase is tested, documented, and committed according to upstream PostgreSQL standards.