pg-feature-planlisted

Drop a heavy, citation-rich implementation plan for a scoped PostgreSQL backend feature — Phase 2 of the two-phase PG planner, the bridge from a brainstorm-with-picked-approach to /pg-implement. Names every src/backend or src/include file that must change with file:line cites at a pinned anchor, enumerates catalog / CATALOG_VERSION_NO / WAL / on-disk / lock-order / extension-ABI risks, proposes the test surface (regress / iso / TAP), structures the patch into independently-reviewable phases, picks a CommitFest landing strategy, and emits the plan-mode plan that /pg-implement executes phase-by-phase with plan-linked commits. **Use proactively whenever the user invokes /pg-plan, says "plan this PG feature", "make a plan for X in PG", "drop a heavy plan", "plan-mode plan for [PG feature]", "i picked option [A/B/C] in the brainstorm, now plan it", "we settled on the [approach] for the [PG topic], write me the phase plan with file:line cites", "spec-to-plan this pgsql-hackers thread", "shadow-implementation plan a
matejformanek/postgres-claude · ★ 0 · AI & Automation · score 73

Install: claude install-skill matejformanek/postgres-claude

# pg-feature-plan — Phase 2 of the PG planner The heavy stage. Phase 1 (`pg-feature-brainstorm`) narrowed the design space; Phase 2 makes it implementable. Output is a plan-mode plan with file:line cites that `/pg-implement` (NOT the generic `/implement`) executes phase-by-phase with plan-linked commits. ## Inputs - **Slug** (required): the planning directory under `planning/<slug>/`. If `brainstorm.md` exists, read it first — the picked approach + the DECISION: answers are your constraints. - **No brainstorm?** Fine — accept a direct natural-language description of the picked approach + any constraints the user has already locked down. But note in the plan's intro that Phase 1 was skipped (and therefore some design-space exploration may be missing). - **Thread spec?** A `planning/<slug>/spec.md` extracted from a pgsql-hackers thread (shadow-implementation runs). Run the spec through the engagement-classification step below before treating any of its content as locked. ## Context awareness — mandatory pre-step (M2) **Before drafting any plan content**, run a context probe. Surfaced by the money-fx-exchange shadow run (April-1 2026 joke proposal that the planner initially treated earnestly). 1. **Posting date.** Check the thread's first-message date: - April 1 → flag for joke-check (look for `[PoC]` / `[RFC]` wording, absence of patch attachment, deadpan replies). - Within 2 weeks of a release-branch cut → flag for late-cycle context; the