Skip to main content

/questions

Investigate a question about Clear Rates (CLD), Spines, or Consumer Engineering by searching the codebase, documentation, and querying Trino data.

Usage​

/questions [cld|spines|consumer] <paste the question here>

Prefix your question with the domain (cld, spines, or consumer). If you don't specify one, you'll be asked to clarify.

What It Does​

  1. Classifies the question — identifies what's being asked, any entities (payer, provider, billing code, NPI, network), and any version/time context.

  2. Loads reference material — for CLD questions, reads a curated index of sub-categories (missing codes, missing rates, hospital data issues, rate scores, rate values) and follows it to the relevant reference doc with investigation paths and worked examples. For Spines and Consumer Engineering, searches the codebase and docs directly.

  3. Searches the codebase and docs — reads the relevant entry-point files, SQL templates, and config for the domain. CLD has structured entry points (__init__.py, params.py, network_mappings.py); Spines has per-module directories; Consumer has pricingservice/, eli_lilly_pricing/, etc.

  4. Queries Trino (if needed) — uses /trino-query with helper SQL templates for common patterns: finding a provider, tracing a code through the pipeline, checking plan bridge matches, checking hospital data, and checking rate scores.

  5. Answers the question — leads with the answer (not the investigation), cites sources, and suggests next steps.

  6. Applies code changes (if needed) — if the investigation reveals a code change is required, asks you to confirm and then invokes /edit-dags with the appropriate arguments. The edit skill handles branch creation, makes the change, commits, pushes, and creates a PR. Supported edit types:

    • Adding billing codes → /edit-dags cld add codes
    • Adding payer networks → /edit-dags cld add network
    • Adding a new provider type → /edit-dags cld add provider type
    • Parallelizing a task → /edit-dags cld chunkify
    • Creating a new spine → /edit-dags spines create spine
    • Other DAG edits → /edit-dags <domain> <description>

  7. Posts to Jira (if applicable) — if the investigation was triggered via /jira, posts the answer as a comment on the Jira issue using the Atlassian Document Format. Includes the answer summary, cited sources, any PR links from code changes, and suggested next steps.

  8. Saves the output — writes the investigation to .claude/skills/questions/answers/{date}_{short_description}.md including Trino queries run and any PR links from code changes. If triggered from Jira, posts a link to the answer doc on the ticket.

  9. Optionally improves references — after answering, may suggest updating reference docs, adding worked examples, or creating new helper queries based on what the investigation revealed.

Key Files Read​

  • .claude/skills/questions/references/cld/index.md — CLD question classification and sub-category index
  • .claude/skills/questions/references/cld/*.md — detailed reference docs per sub-category
  • .claude/skills/questions/helpers/schemas.md — Trino table schemas for writing correct queries
  • .claude/skills/questions/helpers/*.sql — reusable query templates (find_provider, trace_code_pipeline, check_plan_bridge, check_hospital_data, check_rate_score)
  • airflow_dags/dags/data_science/cld/ — CLD source code
  • airflow_dags/dags/data_science/spines/ — Spines source code
  • airflow_dags/dags/consumer_engineering/ — Consumer Engineering source code
  • tq-api-docs/*/docs/ — domain documentation
On this page: