thegoodparty

Use when manually triggering a bulk run of meeting briefings — dispatching a cohort of meeting_briefing agent jobs against prod via the imminence-gated endpoint, monitoring them to completion, and producing the outcome/cost/runtime analysis and CSV export. Irreversible prod spend (~$6 per dispatched briefing); requires gp-admin AWS access and this repo's packages/gp-api.

Open a PR following GoodParty conventions and drive the delegate-reviewer bot to approval autonomously. Use when the user says "open a PR", "ship this", "create a PR", "create a PR and address delegate", or otherwise wants changes turned into an approved PR in omni.

Write a GoodParty Technical Design Doc (TDD) for a big-rock feature: a human-reviewable design of the system changes, posted to the ClickUp TDD folder, with deeper detail split into an Implementation Notes subpage. Use when the user wants to design a feature, write a tech design / design doc / TDD, or turn a scoped problem into a reviewable technical design. Not for small features or bugs.

Use when you want to visually review a cohort of meeting_briefing artifacts rendered in the real webapp UI — "pop the gallery", "view the briefings", "let me page through these briefings". Pulls artifact JSON from S3 into a local dev-only gallery at http://localhost:4000/dev/briefings that renders each briefing through the production briefing components with prev/next paging. Dev-only, read-only, no prod spend.

Use when you want to spot-check a cohort of community-issue artifacts (top_community_issues + trending_issues) locally — "pop the issue gallery", "view the issues", "let me eyeball these issue artifacts". Pulls artifact JSON from S3 into a local dev-only viewer at http://localhost:4000/dev/issues that renders ranked issues with category/priority chips, overview text, and sources. Dev-only, read-only, no prod spend.

Use when you need to analyze the cost of CAP agent experiment runs or cohorts (meeting_briefing, community_issues, etc.) — what a job costs, where in a run the spend happens, which runs drive the bulk of spend, and how cost scales with district size. Resolves a scope from plain English, extracts per-turn cost-weighted data to a cached parquet, and produces cost-distribution tables and plots. Population-not-sample, distributions-not-point-estimates, and dollars always traced to the invoice-validated DB costUsd.

Write an analytics event's governance metadata (purpose, status, supersession lineage, product tag) into Amplitude — when adding a new client event, retiring or superseding one, or enriching/backfilling an existing event that is missing metadata. Called by instrument-analytics-event after it registers a new event, and runnable standalone for governance updates after an audit. Client (Amplitude) events only.

Enter prototype mode to build, extend, or explore a UI prototype in packages/prototypes. Use when the user says "prototype", "prototype mode", "build a mockup", "build a prototype UI", "work on a prototype", "design mode", or wants to iterate on a visual concept without production constraints.

Use when a Serve-product data concept — EO activation, Serve engagement/MAU, People Served, the onboarding funnel, Serve Amplitude events, hygiene filters — needs to resolve to its governed metric, table, column, or definition before a query is written. Not for running analyses (that is the analytics-process skill).

Use when a Win-product data concept — engagement, activation, outcomes/win rate, viability, segmentation, Amplitude events, joins, PMF/satisfaction — needs to resolve to its governed metric, table, column, or definition before a query is written. Not for running analyses (that is the analytics-process skill).

Use when planning, executing, reviewing, or calibrating a product analysis, or when asked a product data question that should become one (the entry runbook routes by product — Win and Serve today). For the data facts themselves, use the product's knowledge skill (win-analytics-knowledge or serve-analytics-knowledge).

Use when investigating a Databricks or dbt Cloud cost/usage increase, attributing spend across warehouses, clusters, jobs, models, and tests, or answering "what is driving our compute cost". Produces an interactive HTML cost dashboard from system tables.

Audit and quantify gp_api product campaigns that have no matching DDHQ election result, for a given election-date window. Classifies every unmatched candidacy into a definitive reason (never ran / race not present in DDHQ data / never made the ballot / product wrong-office or wrong-date / DDHQ omission / genuine matcher false-negative) using a deterministic SQL pre-pass against DDHQ staging plus a web-verification subagent fan-out, then writes an external aggregate summary CSV, an internal per-record detail CSV, and a confirmed-winners list. Use when asked to understand or quantify why product users tied to a 2026 (or later) campaign are not matched to election results, or to refresh the prior DDHQ miss audit.

Match an external or ad-hoc table (HubSpot export, lead list, P2V sample) to ICP flags or other reference data in Databricks. Use when you have a table of people or races and need to attach int__icp_offices flags (icp_office_win / icp_office_serve, voter_count, etc.) but the table only has emails, BallotReady race IDs, or position IDs, not the ICP join. Routes by which ID you have: email (two-hop via campaigns), race ID (two-hop via race staging), or position ID (direct join). General Databricks matching reference; not Win-pipeline specific.

Audit entity resolution match results for quality — analyze coverage, false positives, and false negatives

Triage and remediate L2 uniform schema drift using `l2_uniform_schema_preflight` output. Use when dbt runs touching `int__l2_nationwide_uniform` or `int__l2_nationwide_uniform_w_haystaq` fail, or when `L2_PREFLIGHT|` lines report drift (`stg_minus_src`, `src_minus_stg`, `target_minus_src`, `relation_missing`). Parse preflight logs, generate deterministic safe commands and manual instructions, and produce operator-ready next steps.

Add a new HTTP endpoint to a feature module following the controller/services/schemas convention, PrismaBase pattern, and Zod response validation. Use when adding any new route to gp-api.

Run vitest tests in gp-api efficiently — single file, by name, integration with useTestService, or the full verify gate. Use whenever you need to check your work.

Create a new Prisma migration safely against the modular schema. Use when adding/changing a column, table, index, or enum in gp-api. Never edit applied migration SQL.

Add or change a Zod schema in the @goodparty_org/contracts package and rebuild it so gp-webapp and other consumers see the new types. Use when a shape crosses a service boundary.

Add a new Sanity page-builder block (a reusable section the marketing team can drag onto pages). Use when the user wants a new component, block, or section type on the marketing site that does not already exist. Runs the scaffolding generator so no wiring is missed, then customizes and verifies it.

Open a PR on gp-marketing following GoodParty conventions and drive it to all-green — the delegate-reviewer bot approves and every CI check passes. Use when the user says "open a PR", "ship this", "ship it", "create a PR", or otherwise wants their change turned into an approved PR.