Pace
All teams / Engineering

Engineering

Reviews, standups, incident response, architecture decisions, tech debt.

Engineering teams spend half their week on non-coding work: PR review, standup updates, on-call, architecture conversations, docs. Pace tightens each one. The engineering plugin works standalone (no required connectors), and pairs with /data:* for the 'why is this slow' questions that show up in reviews.

Plugins to install

Pick from this set for the role. Primary plugins are essential; companions multiply value.

  • engineering primary

    Code review, architecture decisions, incident response, tech debt audits, deploy checklists, testing strategy, docs.

    claude plugin install engineering@pace
  • data companion

    When reviews touch performance, SQL, or analytics; pair with /data:* to ground in real numbers.

    claude plugin install data@pace
  • productivity companion

    Standups, daily focus blocks, memory of past architecture decisions.

    claude plugin install productivity@pace

Connectors to set up

Claude prompts to authorize each one the first time a relevant skill fires. You only do this once per project.

  • (none required for engineering itself)
  • Snowflake / Databricks / BigQuery (via /data:*)
  • Linear / Jira / Slack (via /productivity:*)

Workflows

Common ways teams use these plugins day to day. Each one is a starting point; adapt the prompt to your context.

  • Pre-review code review

    Runs a structural review before requesting human review. Catches the obvious stuff: dead code paths, missing tests, naming inconsistencies, broken contracts.

    /engineering:code-review this PR

  • Standup summary

    Generates your async standup by reading Linear tickets touched, git commits pushed, and what's blocking.

    /engineering:standup what's blocking me today

  • Architecture decision

    Pros/cons + recommendation on a system choice. Writes the ADR (architecture decision record) in your repo format.

    /engineering:architecture should we use NATS or Kafka for the event bus

  • Incident response

    Triage playbook: diagnostic questions, likely causes, mitigation order, comms template. Useful at 3am.

    /engineering:incident-response p1 ingestion lag

  • Tech debt audit

    Scans a directory or service and ranks debt by effort vs payoff. Surfaces stuff you keep meaning to fix.

    /engineering:tech-debt audit this directory

  • Documentation gap fix

    Reads a module and writes the missing docs: contracts, edge cases, gotchas.

    /engineering:documentation for the rate-limiter middleware

Tips & tricks

Field-tested patterns from teams that have already shipped a quarter or two on these plugins.

  • Self-review before requesting review

    /engineering:code-review before you tag a human. Catches naming and silly mistakes; the human gets to focus on intent.

  • Pin the deploy-checklist

    Use /engineering:deploy-checklist before any prod push. Pin it (via the Pace router pin.mjs) once your team standardizes.

  • Testing strategy upfront

    /engineering:testing-strategy when scoping a feature, not when writing tests. Saves rewrite cycles.

  • Pair with /data for perf reviews

    When the PR touches anything that hits the DB, run /data:write-query against staging to verify the query plan before merging.

  • Incident response > heroics

    /engineering:incident-response has saved hours at 3am. Beats inventing a playbook under pressure.

  • ADR convention sticks

    /engineering:architecture writes ADRs in a stable format. Adopt the format and don't fight it; consistency is the point of ADRs.

See also