agentsclimarketplace

Plan & spec

10,741 rows, by stacks then stars

2,010 of these skill files have been read, by 1,360 distinct authors, and what they tell an agent counted. What Plan & spec authors agree on, and what they forbid

  • Generating prd md from userstory md

    qte77/claude-code-plugins/plugins/ralph/skills/generating-prd-md-from-userstory-md Skill

    2★ repo

    Converts UserStory.md into a structured PRD.md document. Use after generating UserStory.md and before initializing the Ralph loop.

  • Lab notes

    eins78/agent-skills/skills/lab-notes Skill

    2★ repo

    Use when starting experiments, planning features with hypothesis-first approach, checking experiment status, logging observations, or wrapping up trials. Triggers: start an experiment, new trial, begin experiment, what experiments are running, check experiment status, wrap up the experiment, log observation, experiment verdict, plan a feature, explore an idea, /lab-notes.

  • Planning and task breakdown

    LLl0k0laD/agent-skills/skills/planning-and-task-breakdown Skill

    2★ repo

    Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

  • Spec driven development

    LLl0k0laD/agent-skills/skills/spec-driven-development Skill

    2★ repo

    Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

  • Ios native review

    Paretofilm/superpowers-gstack/skills/ios-native-review Skill

    no license2★ repo

    After a PRD/spec/plan for an iOS app, before implementation: validate the artifact against Apple HIG (iOS) via WebFetch citations. Asks "is this iOS-native?" — complements pitfall-verification and quality-review.

  • Macos native review

    Paretofilm/superpowers-gstack/skills/macos-native-review Skill

    no license2★ repo

    After a PRD/spec/plan for a macOS app, before implementation: validate the artifact against Apple HIG via WebFetch citations. Asks "is this Apple-native?" — complements pitfall-verification and quality-review.

  • Pitfall verification

    Paretofilm/superpowers-gstack/skills/pitfall-verification Skill

    no license2★ repo

    After any PRD, spec, plan, or code change: verify artifact-specific pitfalls don't apply before declaring done. For ship-worthy changes, auto-chains Codex + a third model house + adversarial synthesis.

  • Quality review

    Paretofilm/superpowers-gstack/skills/quality-review Skill

    no license2★ repo

    After a PRD, spec, or plan, before implementation: hunt perceived-quality pitfalls (silent failures, missing loading/empty states, error recovery, state drift) that make a product feel cheap. Complements pitfall-verification.

  • Plan

    launch52-ai/flutter-template/.claude/skills/plan Skill

    2★ repo

    Comprehensive feature planning before implementation. Gathers requirements, designs all layers (domain, data, presentation), identifies data sources, and creates an implementation roadmap with skill references. Use BEFORE creating any new feature to ensure complete understanding and proper architecture.

  • Forge prd

    ForgeyClap/claude-forge/.claude/skills/forge-prd Skill

    2★ repo

    Generate a structured PRD (markdown + meta) for a non-trivial build and auto-create a ticket per acceptance criterion (Forge Mission Control Phase 2, WP3 "PRD generator"). Use before starting a non-trivial feature/build, typically right after Deep Learn Mode. Trigger on "write a PRD", "generate a PRD", "scope this feature", "spec this out before we build".

  • Forge deeplearn

    ForgeyClap/claude-forge/plugins/forge/skills/forge-deeplearn Skill

    2★ repo

    On-demand, READ-ONLY full-codebase priming scanner (Forge Mission Control Phase 2, WP2 "Deep Learn Mode"). Use before generating a PRD, before a big refactor, or whenever the Lead is dropped into a new/unfamiliar project and needs an honest project-summary + risk-list before planning. Trigger on "deep learn", "prime the codebase", "scan the project", "learn this codebase before we plan".

  • Forge prd

    ForgeyClap/claude-forge/plugins/forge/skills/forge-prd Skill

    2★ repo

    Generate a structured PRD (markdown + meta) for a non-trivial build and auto-create a ticket per acceptance criterion (Forge Mission Control Phase 2, WP3 "PRD generator"). Use before starting a non-trivial feature/build, typically right after Deep Learn Mode. Trigger on "write a PRD", "generate a PRD", "scope this feature", "spec this out before we build".

  • Plan with teeth

    Fergius-Engineering/instincts/skills/plan-with-teeth Skill

    2★ repo

    Use when about to write an implementation plan, scope a multi-step change, or enter plan mode - before any plan text exists. Also fires when reviewing a plan that states what code does without evidence behind it.

  • War gar decomposition

    PuckAPI/claude-sports-analytics/skills/war-gar-decomposition Skill

    2★ repo

    Builds WAR (Wins Above Replacement) and GAR (Goals Above Replacement) from scratch using RAPM ridge regression on shift-level data. Use when user asks about WAR, GAR, RAPM, player value metrics, wins above replacement, contract surplus value, JFresh-style player cards, or all-in-one player evaluation. Do not use for simple player stats lookup -- see player-scouting. Do not use for goalie evaluation -- goalies use GSAA not WAR, see goalie-analysis. Do not use for team-level performance -- see team-analysis.

    The same file is in 1 other repository

  • The sun tzu lens

    karagos/ai-skills-by-caio/skills/the-sun-tzu-lens Skill

    no license2★ repo

    The Sun Tzu Lens: strategic intelligence for executive decisions. Applies Sun Tzu's 13 chapters to business situations: mergers, market entries, competitor moves, pricing, restructuring, negotiations, failures. Seven modes: War Council, Strategic Analysis, Enemy's Eyes, Five Factors Audit, General's Debrief, Terrain Map, and Negotiation Table. Web search before every response. Trigger when the user says "war council", "strategic lens", "enemy's eyes", "audit", "debrief", "terrain", "negotiate", "sun tzu", "sun tzu help", "show me the commands", "what can the sun tzu lens do", "how do I use sun tzu". Also trigger on strategic analysis through a Sun Tzu or military strategy framework, analyzing a decision like a general, competitor analysis from the opponent's perspective, or pre-decision readiness assessment. By Stefanos Karagos, CAIO (wearecaio.com).

  • Blueprint

    multiplex-ai/muggle-ai-teams/skills/blueprint Skill

    2★ repo

    Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".

    The same file is in 4 other repositories

  • Content strategy

    multiplex-ai/muggle-ai-teams/skills/content-strategy Skill

    2★ repo

    When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.

    The same file is in 2 other repositories

  • Free tool strategy

    multiplex-ai/muggle-ai-teams/skills/free-tool-strategy Skill

    2★ repo

    When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.

    The same file is in 2 other repositories

  • Geo proposal

    multiplex-ai/muggle-ai-teams/skills/geo-proposal Skill

    2★ repo

    Auto-generate a professional, client-ready GEO service proposal from audit data. Creates a full proposal in markdown and PDF including executive summary, findings, recommended service packages (Basic/Standard/Premium), pricing, timeline, and terms. Use when user says "proposal", "proposta", "offerta", "preventivo", "generate proposal", or after completing a GEO audit for a prospect.

    The same file is in 16 other repositories

  • Inventory demand planning

    multiplex-ai/muggle-ai-teams/skills/inventory-demand-planning Skill

    2★ repo

    Codified expertise for demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis, seasonal transition management, and vendor negotiation frameworks. Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimizing inventory levels.

  • Launch strategy

    multiplex-ai/muggle-ai-teams/skills/launch-strategy Skill

    2★ repo

    When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas.

    The same file is in 3 other repositories

  • Lead magnets

    multiplex-ai/muggle-ai-teams/skills/lead-magnets Skill

    2★ repo

    When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tool-strategy. For writing the actual content, see copywriting. For the email sequence after capture, see email-sequence.

    The same file is in 2 other repositories

  • Pricing strategy

    multiplex-ai/muggle-ai-teams/skills/pricing-strategy Skill

    2★ repo

    When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.

    The same file is in 5 other repositories

  • Ralphinho rfc pipeline

    multiplex-ai/muggle-ai-teams/skills/ralphinho-rfc-pipeline Skill

    2★ repo

    RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.

    The same file is in 7 other repositories

  • Seo plan

    multiplex-ai/muggle-ai-teams/skills/seo-plan Skill

    2★ repo

    Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "content strategy", "site architecture", or "SEO roadmap".

    The same file is in 10 other repositories

  • Site architecture

    multiplex-ai/muggle-ai-teams/skills/site-architecture Skill

    2★ repo

    When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.

    The same file is in 4 other repositories

  • Strategic compact

    multiplex-ai/muggle-ai-teams/skills/strategic-compact Skill

    2★ repo

    Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

    The same file is in 4 other repositories

  • Ss coding workflow

    lbk-open/super-spec/skills/ss-coding-workflow Skill

    2★ repo

    Executes a ready-made plan or a plain-language change instruction end to end — branch, multi-agent coding with built-in review, and PR/commit delivery. Use for running an existing execution plan or a simple, well-scoped code change; use ss-feature-workflow instead when a proposal and plan still need to be drafted.

  • Ss feature workflow

    lbk-open/super-spec/skills/ss-feature-workflow Skill

    2★ repo

    End-to-end feature delivery — takes a PRD, requirement description, or requirement doc link and orchestrates branch creation, a complexity-gated technical proposal (complex requirements only), execution plan, multi-agent coding with built-in review, and PR/commit delivery. Use only when the user explicitly asks for the full feature pipeline, not for a single edit or question.

  • Ss plan

    lbk-open/super-spec/skills/ss-plan Skill

    2★ repo

    Use before writing any code, once you have a requirement, technical proposal, or spec that needs to become an executable, task-level plan. Decomposes the input into self-contained, TDD-ordered tasks with explicit dependencies, exact file paths, and acceptance criteria traced to OpenSpec scenarios; splits multi-subsystem requirements into separate plans and produces a master plan when the split spans multiple repositories.

  • Ss proposal

    lbk-open/super-spec/skills/ss-proposal Skill

    2★ repo

    Use when you have a PRD or requirement description and need a complete technical proposal before writing any code. Filters the requirement down to this repository's boundary, analyzes the existing architecture and conventions, and produces a Markdown proposal covering architecture, data flow, key interfaces, alternatives, risks, and milestones — gated by a self-review and, when available, an independent reviewer pass.

  • Ss references

    lbk-open/super-spec/skills/ss-references Skill

    2★ repo

    A library of shared templates that other ss-* skills read at runtime — subagent dispatch prompts, the technical-proposal template and its quality checklist, the OpenSpec directory skeleton, and the multi-repo detection rules. Not invoked directly by users; skills like ss-coding, ss-proposal, ss-write-spec, and the workflows read the file they need before producing an artifact.

  • Ss reverse spec

    lbk-open/super-spec/skills/ss-reverse-spec Skill

    2★ repo

    Reverse-engineers OpenSpec source-of-truth capability specs from an existing (brownfield) codebase, either as a full baseline sweep or for a single capability. Bootstraps the openspec/ skeleton first if the project doesn't have one yet. Use this to give a legacy repository a meaningful starting spec instead of an empty openspec/specs/ directory.

  • Ss show spec

    lbk-open/super-spec/skills/ss-show-spec Skill

    2★ repo

    Displays the current source-of-truth OpenSpec for a capability, or lists all capabilities when called without one, and summarizes recent archived changes that touched it. Use this as the entry point before reading or editing anything under openspec/ — do not grep or browse the directory manually first.

  • Ss trace spec

    lbk-open/super-spec/skills/ss-trace-spec Skill

    2★ repo

    Traces when an OpenSpec Requirement or Scenario was added, modified, removed, or renamed by searching current specs, archived deltas, and git history. Use this to answer "when and why did this behavior change" questions about a capability.

  • Ss write spec

    lbk-open/super-spec/skills/ss-write-spec Skill

    2★ repo

    Generates or updates OpenSpec delta specs under openspec/changes/<change-id>/ from a proposal, PRD, or plain-language requirement, bootstrapping the openspec/ skeleton first if the project doesn't have one yet. Use this to align capability specs with reviewers before writing a full execution plan, or to adjust deltas without regenerating the plan.

  • Devrites ux shape

    ViktorsBaikers/DevRites/pack/.claude/skills/devrites-ux-shape Skill

    no license2★ repo

    Plan UX/UI before code: design direction, design brief, visual direction, key states, interaction model for screens/forms/dashboards/settings pages. Use when shaping UI. Not for building/polish.

  • Rite define

    ViktorsBaikers/DevRites/pack/.claude/skills/rite-define Skill

    no license2★ repo

    Define the first build plan from an approved spec: architecture, task slices, traceability, and state. Use when turning approved intent into its initial plan.

  • Rite plan

    ViktorsBaikers/DevRites/pack/.claude/skills/rite-plan Skill

    no license2★ repo

    Re-plan existing work when reality invalidates the plan: reslice a slice that is too big, repair drift, reorder dependencies, split boundaries, or unblock work. Not first-pass decomposition.

  • Rite spec

    ViktorsBaikers/DevRites/pack/.claude/skills/rite-spec Skill

    no license2★ repo

    Spec new or high-risk behavior before code and write its `.devrites/work/<slug>/` workspace. Use for a feature/app, vague product idea, auth or migration work, or a public-API change. Not for approved-spec planning.

  • Rite temper

    ViktorsBaikers/DevRites/pack/.claude/skills/rite-temper Skill

    no license2★ repo

    Temper a readied spec before planning. Use when the user says "temper this", "strategy review", "pre-mortem the spec", or asks if we are over/under-building. Not for code review or final seal.

  • Devrites ux shape

    ViktorsBaikers/DevRites/pack/generated/claude/skills/devrites-ux-shape Skill

    no license2★ repo

    Plan UX/UI before code: design direction, design brief, visual direction, key states, interaction model for screens/forms/dashboards/settings pages. Use when shaping UI. Not for building/polish.

  • Rite define

    ViktorsBaikers/DevRites/pack/generated/claude/skills/rite-define Skill

    no license2★ repo

    Define the first build plan from an approved spec: architecture, task slices, traceability, and state. Use when turning approved intent into its initial plan.

  • Rite plan

    ViktorsBaikers/DevRites/pack/generated/claude/skills/rite-plan Skill

    no license2★ repo

    Re-plan existing work when reality invalidates the plan: reslice a slice that is too big, repair drift, reorder dependencies, split boundaries, or unblock work. Not first-pass decomposition.

  • Rite spec

    ViktorsBaikers/DevRites/pack/generated/claude/skills/rite-spec Skill

    no license2★ repo

    Spec new or high-risk behavior before code and write its `.devrites/work/<slug>/` workspace. Use for a feature/app, vague product idea, auth or migration work, or a public-API change. Not for approved-spec planning.

  • Rite temper

    ViktorsBaikers/DevRites/pack/generated/claude/skills/rite-temper Skill

    no license2★ repo

    Temper a readied spec before planning. Use when the user says "temper this", "strategy review", "pre-mortem the spec", or asks if we are over/under-building. Not for code review or final seal.

  • Rite define

    ViktorsBaikers/DevRites/pack/generated/codex/skills/rite-define Skill

    no license2★ repo

    Define the first build plan from an approved spec: architecture, task slices, traceability, and state. Use when turning approved intent into its initial plan.

  • Rite plan

    ViktorsBaikers/DevRites/pack/generated/codex/skills/rite-plan Skill

    no license2★ repo

    Re-plan existing work when reality invalidates the plan: reslice a slice that is too big, repair drift, reorder dependencies, split boundaries, or unblock work. Not first-pass decomposition.

  • Rite spec

    ViktorsBaikers/DevRites/pack/generated/codex/skills/rite-spec Skill

    no license2★ repo

    Spec new or high-risk behavior before code and write its `.devrites/work/<slug>/` workspace. Use for a feature/app, vague product idea, auth or migration work, or a public-API change. Not for approved-spec planning.

  • Rite temper

    ViktorsBaikers/DevRites/pack/generated/codex/skills/rite-temper Skill

    no license2★ repo

    Temper a readied spec before planning. Use when the user says "temper this", "strategy review", "pre-mortem the spec", or asks if we are over/under-building. Not for code review or final seal.

  • Spawning plan

    citedy/skills/skills/spawning-plan Skill

    2★ repo

    Spawning Plan. Use when user wants to spawn agents, create a team, or coordinate multiple agents. Automatically gathers context, asks team topology questions, outputs clean TEAM PLAN markdown, and gets user approval. 3 steps: context gathering -> questions -> present plan. Requires Claude Code with Agent Teams support.

    The same file is in 2 other repositories

  • Benders decomposition

    hajibabaie/combinatorial-optimization-skills/skills/benders-decomposition Skill

    2★ repo

    When the user wants to solve a structured MILP or two-stage stochastic program by Benders decomposition — splitting it into an integer master and LP subproblems, deriving optimality and feasibility cuts from subproblem duals, and implementing either the classic iterative loop or branch-and-Benders-cut with lazy-constraint callbacks in Gurobi. Also use when the user mentions "Benders decomposition," "Benders cuts," "L-shaped method," "feasibility cut," "optimality cut," "master problem," or when fixing a few complicating variables leaves an easy or separable subproblem. For scenario generation and SAA, see stochastic-optimization; for callback mechanics and parameters, see gurobi-advanced-features.

  • Dantzig wolfe decomposition

    hajibabaie/combinatorial-optimization-skills/skills/dantzig-wolfe-decomposition Skill

    2★ repo

    When the user wants to reformulate a structured LP or MIP via Dantzig-Wolfe decomposition — detect block-angular structure, build the master with convexity constraints, price columns from independent subproblems, and relate the DW bound to LP and Lagrangian bounds. Also use when the user mentions "Dantzig-Wolfe," "block-angular," "decomposable structure," "convexification," "master problem reformulation," or when a model splits into blocks tied by a few linking constraints. For the pricing loop and branch-and-price, see column-generation; for subgradient dual bounds, see lagrangian-relaxation.

  • Estimation of distribution algorithms

    hajibabaie/combinatorial-optimization-skills/skills/estimation-of-distribution-algorithms Skill

    2★ repo

    When the user wants to design or implement an estimation of distribution algorithm — UMDA, PBIL, compact GA, tree models, BOA, or permutation EDAs with position-frequency, edge-histogram, or Mallows models — building and sampling probabilistic models over good solutions instead of using crossover. Also use when the user mentions "estimation of distribution," "EDA," "UMDA," "PBIL," "probabilistic model-building," or when variable interactions must be learned rather than hand-coded. For recombination-based search, see genetic-algorithms; for representation and decoder choices, see solution-encodings.

  • Trade show budget planner

    rubyt5673/trade-show-skills/trade-show-budget-planner Skill

    2★ repo

    Build realistic trade show budgets and ROI projections with industry cost benchmarks.

  • Spec writer

    jaydenluckertjes-ai/Carmack-Council/skills/spec-writer Skill

    2★ repo

    Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this out", "create a spec", "I need a spec for...", or describes a feature they want to build. Produces adaptive-complexity specs with Job Stories, Gherkin acceptance criteria, and three-tier boundaries. Output is a markdown file ready for agent execution or human review.

    The same file is in 1 other repository

  • Corpus chain

    matejformanek/postgres-claude/.claude/skills/corpus-chain Skill

    2★ repo

    Traverse the pg-claude knowledge graph to answer "what does this feature/file/pattern touch across the corpus?" — pulls scenarios, idioms, call-site file examples, sibling patterns, subsystem ownership, and analogous past features from planning/ + sessions/ into a single chain map. Uses the graph edges built by `scripts/populate-idiom-callsites.py` (idiom → files) and `scripts/build-scenario-idiom-matrix.py` (scenario ↔ idiom bidirectional). Use proactively when brainstorming a new PG feature, planning §3 file table, investigating an unfamiliar subsystem, or trying to find "have we touched something like this before?". Also use inside `pg-feature-brainstorm` step 1 (subsystem framing) and `pg-feature-plan` before §3 to seed the file list from existing evidence rather than pure grep. Skip when you already have the anchor's downstream chain memorized, when the task is a one-file bug fix, or when the ask is about non-PG code.

  • Executor and planner

    matejformanek/postgres-claude/.claude/skills/executor-and-planner Skill

    2★ repo

    Edit the PostgreSQL executor or planner — covers src/backend/executor/ (nodeXxx.c, ExecInitNode/ExecProcNode/ExecEndNode/ExecReScan dispatch, PlanState lifecycle, EXPLAIN wiring) and src/backend/optimizer/ (Path → Plan via createplan.c, RelOptInfo lifecycle, add_path cost-dominance pruning, cost_* units in cost.h). Use whenever a PG patch adds or modifies a plan-node executor, introduces a new Path or Plan type, changes cost-model fields in cost.h, adds EXPLAIN output for a node, plumbs a node into execParallel.c, or tweaks join-path enumeration. Skip for end-user query tuning, EXPLAIN ANALYZE of a production query, work_mem / shared_buffers tuning, MySQL / MongoDB / BigQuery / Snowflake / DuckDB / Spark / Trino query engines, ORM query-builder optimization, and pandas / polars dataframe operations.

  • Fmgr and spi

    matejformanek/postgres-claude/.claude/skills/fmgr-and-spi Skill

    2★ repo

    Write a SQL-callable C function or call PostgreSQL fmgr / SPI from C — covers PG_FUNCTION_INFO_V1, PG_GETARG_* / PG_RETURN_*, PG_ARGISNULL, SRF_* set-returning function ValuePerCall and Materialize modes, composite / polymorphic returns, DirectFunctionCall* / OidFunctionCall* / FunctionCallInvoke fmgr entry points, plus SPI_connect / SPI_execute / SPI_prepare / SPI_finish, plan caching, SPI cursors, subxact rollback, and SPI return codes. Use whenever a PG patch or extension adds a `Datum foo(PG_FUNCTION_ARGS)` entry point, exposes a set-returning function, calls fmgr from backend C, or embeds SQL via SPI in a backend / trigger / PL handler. Skip for plpgsql / PL/Python / PL/Perl user-side function authoring, libpq / psycopg / JDBC / node-postgres client-side query execution, generic executor questions (use executor-and-planner), and non-PG embedded SQL (Oracle OCI, SQLite C API).

  • Meta commit style

    matejformanek/postgres-claude/.claude/skills/meta-commit-style Skill

    2★ repo

    Write a commit message inside the postgres-claude META repo (knowledge corpus, skill / agent / command edits, planning artifacts, session logs, infra changes) — covers the meta style: `ft(scope):` / `hf(scope):` / `docs(scope):` prefix, a wrapped body, an optional `Plan:` trailer, and the global `Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>` footer (lowercase trailer per real log — 45 lowercase vs 11 uppercase in last 50 commits). Distinct from the upstream PG commit-message-style (which forbids Co-authored-by and uses bare-imperative titles). Use whenever drafting a commit inside `postgres-claude/` (the meta repo) — corpus PR, skill rewrite, session log, planning doc, cloud-routine recipe, etc. Skip for upstream PG patches in `dev/` (use commit-message-style), Conventional Commits style (feat: / fix: / chore: across most non-PG projects), Linux-kernel Signed-off-by commits, Angular / Vue / React commit style, and the generic git-commit message question on any other project.