Plugin·v1.3.0·16 skills
engineering-kit
Engineering skills for AI coding agents, vetted and pinned: bug diagnosis, test-first work, architecture scans, plan interviews, retros, primary-source research, setup wizards and read-only PostgreSQL investigations. Every command runs only when you call it.
Claude Code
claude plugin marketplace add AtlasScope/agent-kit claude plugin install engineering-kit@agent-kit
Codex
codex plugin marketplace add AtlasScope/agent-kit codex plugin add engineering-kit@agent-kit
Skills
codebase-designDeep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality). Called by tdd and improve-codebase-architecture; otherwise only when the user explicitly asks for it by name.engineering-kit·Matt PocockdatabaseUse only when the user explicitly invokes /database or $database. Turns a plain description of a PostgreSQL problem (wrong numbers, heavy writes, a crowded schema, cost, a risky migration, agents escalating decisions) into one starting investigation from the prompt library, says why in a sentence, and runs it read-only when the session can reach the code and database. Ordinary database talk must not activate it.engineering-kit·Agent Kitdiagnosing-bugsDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.engineering-kit·Matt Pocockdomain-modelingKeeps GLOSSARY.md and ADRs current while a design is discussed. Called by grill-with-docs and improve-codebase-architecture; otherwise only when the user explicitly asks to update the glossary or record an ADR.engineering-kit·Matt PocockengineerUse only when the user explicitly invokes /engineer or $engineer. Turns a description of what is going on in a codebase (a symptom, a worry, a plan) into one starting move from the Agent Engineering Field Guide - an investigation prompt to paste, an installed skill to run, or a thinking prompt - and says why in a line. Ordinary engineering talk must not activate it.engineering-kit·Agent Kitgrill-meA relentless interview to sharpen a plan or design.engineering-kit·Matt Pocockgrill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.engineering-kit·Matt PocockgrillingInterview rounds that stress-test a plan or decision. Called by grill-me, grill-with-docs and improve-codebase-architecture; otherwise only when the user explicitly asks to be grilled.engineering-kit·Matt Pocockimprove-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.engineering-kit·Matt PocockresearchInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.engineering-kit·Matt PocockretroConduct a retrospective on a coding session.engineering-kit·Matt PococktddTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.engineering-kit·Matt Pocockto-questionnaireTurn a decision you can't fully answer into a questionnaire for someone else to fill in.engineering-kit·Matt Pocockwait-whatStop. That last message did not land: re-pitch it.engineering-kit·Matt PocockwizardGenerate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.engineering-kit·Matt Pocockwriting-for-agentsStyle reference for documents agents read (skills, AGENTS.md, CLAUDE.md). Called by retro; otherwise only when the user explicitly asks for it by name.engineering-kit·Matt Pocock
Read the kit’s README for setup notes and companion plugins.