New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Enrich Release Roadmap

by trickle-labs in trickle-labs/pg-trickle

Enrich a pgtrickle release roadmap with prioritised items across six quality pillars: correctness, stability, performance, scalability, ease-of-use, and test coverage.

Apache-2.0Auto-check passedProduct & Project Management

Install Enrich Release Roadmap

skills CLI
$ npx skills add trickle-labs/pg-trickle --skill enrich-release-roadmap -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install trickle-labs/pg-trickle enrich-release-roadmap --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/trickle-labs/pg-trickle.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/enrich-release-roadmap .claude/skills/enrich-release-roadmap && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
enrich-release-roadmap
GitHub stars
148
Token cost
~1.9k tokens
SKILL.md length
897 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
Apache-2.0

At a glance

Enrich a pgtrickle release roadmap with prioritised items across six quality pillars: correctness, stability, performance, scalability, ease-of-use, and test coverage.

  • Works in 4 steps: Collect Context → Propose Items per Pillar → Write the Release Theme → …
  • Planning a new release
  • SKILL.md covers When to Use, Inputs to Gather First, Procedure and Output & Application, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Enrich Release Roadmap is an agent skill from trickle-labs/pg-trickle. Enrich a pgtrickle release roadmap with prioritised items across six quality pillars: correctness, stability, performance, scalability, ease-of-use, and test coverage. Use when planning a new release, fleshing out a milestone, or reviewing what gaps exist before tagging a version.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering Test coverage and Project management. The repository describes itself as: A PostgreSQL 18+ extension for streaming tables with incremental view maintenance, powered by differential dataflow in Rust. The licence is Apache-2.0.

When your agent uses it

  • Planning a new release
  • Fleshing out a milestone
  • Reviewing what gaps exist before tagging a version

Example prompts

  • “/enrich-release-roadmap”

Requirements

  • Docker

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Collect Context
  2. Propose Items per Pillar
  3. Write the Release Theme
  4. Flag Conflicts & Risks

What it can do on your machine

Read from SKILL.md and the folder at commit 101c5d3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Enrich Release Roadmap loads about 1.9k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 897 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from trickle-labs/pg-trickle at commit 101c5d3, republished under its Apache-2.0 licence (© trickle-labs). 897 words, ~1,930 tokens.

Download SKILL.mdSave it as .claude/skills/enrich-release-roadmap/SKILL.md (or your agent's skills folder).
name
enrich-release-roadmap
description
Enrich a pg_trickle release roadmap with prioritised items across six quality pillars: correctness, stability, performance, scalability, ease-of-use, and test coverage. Use when planning a new release, fleshing out a milestone, or reviewing what gaps exist before tagging a version.
argument-hint
Target release version (e.g. 0.18.0)

Enrich Release Roadmap

Proposes a rich, prioritised set of roadmap items for a target pg_trickle release, grouped under six quality pillars, ready to paste into ROADMAP.md.

When to Use

  • Planning a new milestone / release
  • Fleshing out a skeletal roadmap section
  • Pre-release gap review (correctness, stability, performance, scalability, ease-of-use, coverage)

Inputs to Gather First

Before generating proposals, read the following files so you have current context:

  1. ROADMAP.md — existing entry for the target release (theme, listed items)
  2. plans/PLAN_0_<version>.md — implementation order and open items (if it exists)
  3. CHANGELOG.md — last 2-3 releases to avoid duplicating shipped work
  4. AGENTS.md — coding conventions and constraints that all items must respect

Procedure

Step 1 — Collect Context

Read the four files above in parallel. Identify:

  • Items already listed for the target release
  • Items recently shipped (do not re-propose)
  • Known deferred items (explicitly call these out if proposing them again)
Step 2 — Propose Items per Pillar

For each of the six pillars below, propose 3-6 items. For every item provide:

FieldFormat
IDPillar prefix + number, e.g. CORR-1, STAB-2, PERF-3, SCAL-4, UX-5, TEST-6
Title≤ 10-word action phrase
EffortXS / S / M / L / XL
PriorityP0 (must-have) · P1 (high) · P2 (nice-to-have)
Description2-4 sentences covering what, why, and how to verify
DependenciesOther item IDs or prior-release features it builds on
Schema change?Yes / No (SQL migration required)
Pillar 1 — CORRECTNESS

Guiding question: "Could a user silently get the wrong answer from their stream table?"

Focus areas:

  • Differential refresh producing wrong results
  • Delta weight / __pgt_count accounting errors
  • NULL edge cases in PK joins and aggregate algebraic invariants (SUM/COUNT sign, Welford aux columns)
  • PK collision under concurrent DML
  • GROUP BY / DISTINCT / HAVING correctness under deletes
  • CDC ordering guarantees (TRUNCATE + INSERT, UPDATE old/new)
  • Recursive CTEs and LATERAL subquery scoping
  • Any issues surfaced by SQLancer fuzzing
Pillar 2 — STABILITY

Guiding question: "Could this crash, corrupt, or leave the system in a broken state?"

Focus areas:

  • unwrap() / panic!() elimination in SQL-reachable paths
  • Parallel worker crash recovery (orphaned transactions, leftover change buffer rows, advisory locks)
  • Background worker SIGTERM handling
  • WAL decoder slot lag and slot invalidation
  • SPI error propagation and SQLSTATE classification
  • Extension upgrade migration safety (catalog drift, column additions)
  • Error message quality and actionability
Pillar 3 — PERFORMANCE

Guiding question: "Are we leaving measurable performance on the table?"

Focus areas:

  • Differential refresh throughput and latency (P50/P99)
  • Cost-model accuracy for FULL vs. DIFFERENTIAL strategy selection
  • Delta branch pruning for zero-change sources
  • Index-aware MERGE planning (covering index, seqscan disable)
  • changed_cols bitmask short-circuiting for unchanged projections
  • Change buffer compaction efficiency
  • Scheduling overhead under high table counts
  • Benchmark regression prevention (Criterion baseline gate)
Pillar 4 — SCALABILITY

Guiding question: "Does this hold up at 10× the current scale?"

Focus areas:

  • High-table-count DAG rebuild time
  • Parallel refresh worker utilisation
  • Partitioned stream table throughput
  • Multi-tenant scheduling fairness
  • Change buffer growth under write-heavy workloads
  • Memory usage under large delta sets
  • CNPG / cloud-native operational patterns
Pillar 5 — EASE OF USE

Guiding question: "Can a new user be productive in under 30 minutes?"

Focus areas:

  • SQL API ergonomics (function naming, defaults, return types)
  • Error message actionability (include table name, query fragment, remediation hint)
  • Documentation gaps (GETTING_STARTED, TROUBLESHOOTING, CONFIGURATION)
  • Migration guides (pg_ivm, native materialized views)
  • Runbook coverage for each known failure mode
  • Playground / quickstart Docker experience
  • TUI quality and completeness
  • dbt macro coverage and documentation
  • Observability (Prometheus metrics, Grafana dashboards)
  • pgxn / GHCR packaging and install verification
Show full SKILL.md (344 more words)Show less
Pillar 6 — TEST COVERAGE

Guiding question: "What scenario could regress silently because no test covers it?"

Focus areas:

  • Logic currently tested only via E2E that could be unit-tested
  • Property-based / SQLancer fuzzing gaps
  • TPC-H query coverage (22 queries, all SF levels)
  • Upgrade migration tests (column drift, constraint additions)
  • Benchmark regression gates (Criterion baseline on every PR)
  • CDC edge cases: NULL PKs, composite PKs, generated columns, domain types, arrays
  • dbt integration test breadth
  • Light E2E eligibility (move tests off full E2E image where possible)
Step 3 — Write the Release Theme

Write a single paragraph (≤ 5 sentences) summarising the spirit of the release: what user-visible problem it solves, what internal foundations it lays, and what the headline capability is.

Step 4 — Flag Conflicts & Risks

In a "Conflicts & Risks" subsection, call out:

  • Items that contradict each other
  • Items that depend on features not yet shipped
  • Items that require a SQL migration (schema freeze risk)
  • Items that touch the DVM engine core (high regression risk — require property tests)

Output & Application

Do NOT present the enrichment for review or ask for confirmation. Apply the changes directly:

  1. Replace the target release section in ROADMAP.md with the enriched version (preserve existing items, add pillar sections after them). Follow the same style as existing enriched release sections in the file.
  2. Update the effort summary table row for the target release to reflect the new effort estimate.
  3. Commit and push with message: roadmap: enrich v<X.Y.Z> with six-pillar quality items

The enriched section must follow this structure:

markdown
## v<X.Y.Z> — <Theme Title>

> **Release Theme**
> <one-paragraph theme>

### <Existing subsections with original items preserved>

### Correctness
| ID | Title | Effort | Priority |
|----|-------|--------|----------|
| CORR-1 | ... | S | P0 |
...

<brief description per item>

### Stability
...

### Performance
...

### Scalability
...

### Ease of Use
...

### Test Coverage
...

### Conflicts & Risks
...

Constraints (Always Respect)

These come from AGENTS.md and must not be violated by any proposed item:

  • Differential refresh is the primary mode; full refresh is a last resort
  • No data loss under any failure scenario — correctness and durability over performance
  • No unwrap() / panic!() in SQL-reachable Rust code
  • All unsafe blocks require // SAFETY: comments
  • New SQL-facing functions use #[pg_extern(schema = "pgtrickle")]
  • name-typed SPI columns must be cast to text
  • Tests use Testcontainers — never a local PG instance
  • Background workers must handle SIGTERM and respect pg_trickle.enabled GUC
  • Keep SPI connections short-lived — no long operations while holding a connection

© trickle-labs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/enrich-release-roadmap of trickle-labs/pg-trickle.

Open the folder on GitHubat commit 101c5d3

Compare with similar skills

Enrich Release Roadmap next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Enrich Release Roadmap compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Enrich Release Roadmap this skilltrickle-labs/pg-trickle148—~1.9kAutomated safety check: PassApache-2.0
Vibe Scenario Matrixash1794/vibe-engineering163—~695Automated safety check: PassMIT
Verification Gatesrohitg00/skillkit1.5k—~1.7kAutomated safety check: PassApache-2.0
Benchmark Sandboxvercel/vercel-plugin301—~5.4kAutomated safety check: NotesCustom licence
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Uvastral-sh/claude-code-plugins3132 repos~980Automated safety check: PassApache-2.0

Similar skills

  • Vibe Scenario Matrix

    ash1794/vibe-engineering

    Generates a behavioral scenario acceptance matrix for comprehensive test coverage planning.

    163 GitHub stars~695 tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

  • Verification Gates

    rohitg00/skillkit

    Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding.

    1.5k GitHub stars~1.7k tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed

  • Benchmark Sandbox

    vercel/vercel-plugin

    Official

    Run vercel-plugin eval scenarios in Vercel Sandboxes instead of local WezTerm panels.

    301 GitHub stars~5.4k tokensUpdated yesterday
    Product & Project ManagementAuto-check: notes

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Uv

    astral-sh/claude-code-plugins

    Official

    Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.

    313 GitHub starsUsed in 2 repos~980 tokens
    Product & Project ManagementAuto-check passed

  • Project Management

    kunchenguid/firstmate

    Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.

    7.8k GitHub stars~2.1k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from trickle-labs/pg-trickle

  • Create Pull Request

    trickle-labs/pg-trickle

    Create or update a pull request for pgtrickle. An agent skill from trickle-labs/pg-trickle.

    148 GitHub stars~1.1k tokensUpdated 4 days ago
    Auto-check passed

  • Implement Roadmap Version

    trickle-labs/pg-trickle

    Implement all items for a specific version in the pgtrickle roadmap.

    148 GitHub stars~2.9k tokensUpdated 4 days ago
    Auto-check passed

  • Improve Documentation

    trickle-labs/pg-trickle

    Reviews and improves the pgtrickle documentation in docs/. An agent skill from trickle-labs/pg-trickle.

    148 GitHub stars~2.3k tokensUpdated 4 days ago
    Auto-check passed

Categories

Questions about Enrich Release Roadmap

What does Enrich Release Roadmap do?

Enrich a pgtrickle release roadmap with prioritised items across six quality pillars: correctness, stability, performance, scalability, ease-of-use, and test coverage. Enrich Release Roadmap is an agent skill from trickle-labs/pg-trickle. Enrich a pgtrickle release roadmap with prioritised items across six quality pillars: correctness, stability, performance, scalability, ease-of-use, and test coverage.

When should I use Enrich Release Roadmap?

Enrich Release Roadmap fits situations like: planning a new release; fleshing out a milestone; reviewing what gaps exist before tagging a version.

How do I install Enrich Release Roadmap in Claude Code?

Run `npx skills add trickle-labs/pg-trickle --skill enrich-release-roadmap -a claude-code`. Or copy the skill folder (.github/skills/enrich-release-roadmap in trickle-labs/pg-trickle) into .claude/skills/enrich-release-roadmap in your project. Claude Code loads it when a task matches its description.

How do I install Enrich Release Roadmap in Codex?

Run `npx skills add trickle-labs/pg-trickle --skill enrich-release-roadmap -a codex`. Or copy the skill folder (.github/skills/enrich-release-roadmap in trickle-labs/pg-trickle) into .agents/skills/enrich-release-roadmap in your project. Codex loads it when a task matches its description.

Can I use Enrich Release Roadmap in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add trickle-labs/pg-trickle --skill enrich-release-roadmap -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/enrich-release-roadmap, .gemini/skills/enrich-release-roadmap, .github/skills/enrich-release-roadmap and .opencode/skills/enrich-release-roadmap in your project.

What does Enrich Release Roadmap need to run?

SKILL.md names no scripts, command-line tools or credentials: Enrich Release Roadmap is instructions for the agent only. Our summary lists: Docker.

Does Enrich Release Roadmap access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Enrich Release Roadmap safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Enrich Release Roadmap use?

Enrich Release Roadmap is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Enrich Release Roadmap use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Enrich Release Roadmap?

Skills that share tags, products or a category with Enrich Release Roadmap: Vibe Scenario Matrix (ash1794/vibe-engineering, 163 stars), Verification Gates (rohitg00/skillkit, 1.5k stars), Benchmark Sandbox (vercel/vercel-plugin, 301 stars) and CCPM Project Management (automazeio/ccpm, 8.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Enrich Release Roadmap?

trickle-labs (a GitHub organization) maintains it in trickle-labs/pg-trickle, which has 148 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.

Source: trickle-labs/pg-trickle on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.