pg-feature-plan

Generate phased PostgreSQL backend implementation plans with citations and file-level edits.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/matejformanek/postgres-claude --skill pg-feature-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pg-feature-plan
Source: https://github.com/matejformanek/postgres-claude/tree/main/.claude/skills/pg-feature-plan
Command: npx skills add https://github.com/matejformanek/postgres-claude --skill pg-feature-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the guesswork and hallucination risks associated with planning complex PostgreSQL backend changes by providing a structured, citation-heavy implementation roadmap.

Core Features & Use Cases

  • Implementation Roadmapping: Breaks down backend features into phased, reviewable steps with specific file-level edits.
  • Context-Aware Validation: Probes thread history, author posture, and community engagement to determine if a feature is ready for implementation or requires a rejection.
  • Use Case: When you need to add a new GUC or system catalog column, this skill generates a comprehensive plan that includes catalog impact, WAL requirements, and locking strategies, ensuring your patch is ready for CommitFest.

Quick Start

Invoke the pg-feature-plan skill to generate a detailed implementation plan for the proposed PostgreSQL feature after you have picked an approach.

Frequently Asked Questions about pg-feature-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a PostgreSQL backend feature for CommitFest submission?

Plan a PostgreSQL backend feature by generating a citation-rich implementation roadmap that breaks down catalog changes, WAL requirements, and locking strategies into phased, reviewable steps. This ensures your patch adheres to community coding idioms.

What is the best way to structure a PostgreSQL patch submission for system catalog changes?

The best way to structure a PostgreSQL patch submission is using a phased implementation plan with specific file-level edits. This approach validates community thread context and outlines exact catalog impacts before submission.

Does my PostgreSQL feature proposal need context-aware validation before adding WAL records?

Yes, your PostgreSQL feature proposal needs context-aware validation to probe thread history and author posture. This determines if your WAL record additions are ready for implementation or require rejection.

Can I generate an implementation plan for PostgreSQL executor modifications without guessing file impacts?

Yes, you can generate an implementation plan for PostgreSQL executor modifications without guessing. The plan analyzes source tree invariants and provides specific file-level edits to eliminate hallucination risks.

When do I need a phased implementation roadmap for PostgreSQL database internals?

You need a phased implementation roadmap for PostgreSQL database internals when adding new GUCs or system catalog columns. It provides rigorous adherence to locking conventions and prepares your patch for CommitFest review.

Why does my PostgreSQL backend development plan lack reviewable patch steps?

Your PostgreSQL backend development plan lacks reviewable steps because it misses citation-heavy roadmapping. Applying a structured breakdown of source tree invariants ensures your patch meets community coding idioms.