data-request

Plugin data-request from marketplace rdl-agent-extensions in nq-rdl/agent-extensions. Commands read from the repo's manifest — 27 days ago.

Skills (15)

• amend

  Classify analyst amendments to an operator-run or released RDL extract. Renames, reorders, dropped already-surfaced columns and presentation changes go through query-builder's projection extension points; anything that changes rows or meaning becomes a paste-ready engineer hand-off. Use when an extr

• analyse

  Review a finished SQL file for handoff: read it against its scope, record purpose, inputs, outputs, logic steps, assumptions and limitations in .sqlreview/reviews/<slug>/review.json, with every assumption and limitation confirmed by the human, and render the standardised review.md. Re-running on rev

• bootstrap

  Scope a piece of SQL work with the Data Engineer before the SQL is written: an interview that produces .sqlreview/reviews/<slug>/scope.json and the rendered scope.md (intent, inputs, outputs, assumptions, open questions), preserving recorded upstream confirmations. Re-running on an existing scope wa

• draft

  Draft or revise RDL cohort SQL from a defined request and verified source mappings, working autonomously on settled requirements or co-developing unresolved decisions. RDL cohort SQL; verify target engine/version, dataops schema and query-builder column-spec metadata at use time. record_assumption/r

• explain

  Walk a Data Analyst through reviewed SQL, step by step, against its review document, JSON and scope: each logic step with its lines, the assumptions and limitations that govern it (by id), outputs and open questions — pausing for the analyst at every step, then accept for release preparation, send b

• fix

  Fix a defect or make a decided pre-release logic change in RDL request SQL and Python: query results, transformations, identifier types, export formatting, keys, joins and filters. Use for a defect with a concrete expected result, released or not, and for a logic change confirmed to come before an e

• guardrails

  Apply advisory RDL cohort-SQL guardrails when drafting, changing, mapping, validating or reviewing request pipelines, SQL and query-builder resolvers. Covers spec composition, indexed filters, source timezones, join evidence and researcher modelling choices, with pointers to authoritative sources. R

• intake

  Interview the Data Analyst on the research decisions of a data request — cohort and age limits, code-set edges, outcomes and windows, identifiers and presentation, governance and the grain — then fill answers.yaml, write answers.intake.json (schema 1) and, on approval, render the data-analysis-scaff

• lift

  Close out request pipelines: inspect the pinned library, classify lift candidates with the human, file reusable work on the owning library, and record delivered hand-SQL limitations. Revisit released lifts for recurring extracts and candidates in builds not yet delivered, without automatic adoption.

• lookup

  Help a Data Analyst discover source codes for an order field, clinical event or event set, medication, diagnosis or procedure, or pathology task assay. Choose the lookup family and direction, generate a count-only probe for a human to run, then write a private lookup record for mapping. Never runs a

• map

  Propose evidence-backed RDL cohort source-table and query-builder resolver mappings from a request, scope, legacy answers.yaml or existing hand SQL; resolve grain, keys, timezone and units before SQL drafting. Supports a partial map. repo: https://github.com/nq-rdl/agent-extensions

• release

  Draft the researcher-facing Extraction Summary and Extraction Assumptions / Important limitations for a release from the release tag's own pipeline, outputs and validation, checked against the confirmed scope and .sqlreview reviews. A stale review or conflicting source holds its claim; the analyst a

• setup

  Initialise project scope and review records for the Data Request workflow: create the .sqlreview/ directory with config.json (settings + the shared assumption/limitation definitions) and the scope/review report templates, from the bundled default or from answers to a few questions. Safe to re-run —

• triage

  Triage the RDL service-desk data-request queue: resolve enquiry and issue numbers to approval-ID repositories, check scope, scaffold, branch and library-gap state, classify blockers, and return paste-ready comments with an ordered queue (read-only). Co-development mode works one selected request wit

• validate

  Validate RDL request or cohort SQL against its requirements, column specs and shared guardrails; report technical findings and evidence without creating a confirmed review. repo: https://github.com/nq-rdl/agent-extensions

Hooks (2)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/data-request-preflight.sh"

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/data-request-guard.sh"

Similar plugins