--- title: "engineering" description: "Engineering workflow skills for decision mapping, adversarial design review, dependency maintenance, durable terminology, prototyping, TDD, diagnosis, architecture, code review, and handoffs." canonical: https://agentpluginsdirectory.com/plugins/engineering--0xa3b last-updated: 2026-09-18 --- # engineering Engineering workflow skills for decision mapping, adversarial design review, dependency maintenance, durable terminology, prototyping, TDD, diagnosis, architecture, code review, and handoffs. - Slug: engineering--0xa3b - Publisher: Alex Baker - Repository: https://github.com/0xA3B/skills - Manifest: plugins/engineering/plugin.json - Version: 2.5.1 - License: MIT - Category (editorial): other - Skills: 13 (codebase-design, dependency-maintenance, diagnose, grill-me, handoff, improve-codebase-architecture, improve-codebase-tests, prototype, receiving-feedback, review-changes, tdd, terminology, wayfinder) - MCP servers: 0 - Stars: 0 - Repository created: 2026-05-02 - Repository last pushed: 2026-09-17 - Publisher type: User - Listing: https://agentpluginsdirectory.com/plugins/engineering--0xa3b - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What engineering does, in the publisher's words These skills cover the engineering loop from decision mapping and design review through implementation, diagnosis, code review, and session handoff. The skills list below names each workflow. The typical implementation flow starts with wayfinder, which maps a loose or oversized idea into decision-sized chunks. grill-me resolves a selected direction through adversarial questioning, and prototype answers questions that need disposable executable evidence, and loads on its own for prototype and spike requests. tdd implements observable behavior through a red-green-refactor loop over a frontier of behaviors, and loads on its own for implementation requests. review-changes reviews changes the session authored through focused lanes, fixes accepted findings, verifies the fixes with the lanes that reviewed them, and reruns the lanes those fixes invalidated; tdd applies it at completion. Use handoff when another agent session should continue the work from an ignored local context document. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/0xA3B/skills/HEAD/plugins/engineering/README.md ## Skills - codebase-design: Design deeper module interfaces and better seams in concrete repository code. Use when asked to design or improve a specific module interface, deepen shallow wrappers, compare interface designs, choose a seam, reduce caller knowledge, improve testability through an interface, or when another workfl… - dependency-maintenance: Review dependency update PRs across package managers and forges, decide whether they are safe to merge, merge only ready updates, sync local dependency state, refresh repo-pinned tooling through small maintenance PRs, and create linked follow-up issues for breaking changes, validation failures, or… - diagnose: Run a disciplined diagnosis loop for bugs, failures, flaky behavior, and performance regressions: build a red-capable loop, reproduce and minimize, rank falsifiable hypotheses, instrument, fix, and regression-test. Use when the user explicitly asks to diagnose or debug a problem. - grill-me: Interview the user through an adversarial decision tree until the important decisions, dependencies, and edge cases are clear. Use when the user asks to stress-test a plan, decision, idea, or design, get grilled on an approach, challenge a brainstormed direction, or resolve ambiguity before impleme… - handoff: Compact the current session into a local handoff document so another agent session can continue without reconstructing decisions, state, and next actions. - improve-codebase-architecture: Find evidence-backed architectural deepening opportunities in a codebase. Use when the user wants refactoring candidates, better module design, simpler interfaces, stronger testability, or a focused codebase architecture review. - improve-codebase-tests: Find evidence-backed test-suite improvement opportunities in a codebase. Use when the user wants the test suite treated as a codebase: flaky or slow suites, scaffold and fixture design, mock strategy drift, subsumed or low-value tests, or a focused test-suite health review. Do not use for reviewing… - prototype: Build a disposable prototype that answers one design question before real implementation. Use when the user asks to prototype, spike, or try a throwaway version of something, sanity-check a state model or data shape, compare design approaches with switchable variants, or prove that an existing syst… - receiving-feedback: Use when handling existing feedback that evaluates completed work: reviewer comments, PR or MR comments, sub-agent findings, findings from a review agent or bot, or a user's correction of a prior response. Verifies and triages each item before responding or applying fixes. Do not use for a message… - review-changes: Use when asked to review changes made in the current session before committing, opening a PR, or merging: the worktree, staged or work-in-progress edits, or the session's commits up to a whole branch, including changes to agent-instruction files and documentation. Also use when asked to run one rev… - tdd: Use when implementing or changing behavior that callers or users can observe: a new feature, a behavior change, a bug fix whose cause is known, a port from a reference implementation, or a new or changed public interface or seam. Drives the work through a red-green-refactor loop over a frontier of… - terminology: Create, update, prune, or review durable project terminology in AGENTS.md. Use when the user wants to define domain terms, harden naming, resolve ambiguous language, record aliases to avoid, align code or docs with a terminology section, capture a term that stabilized during review or implementatio… - wayfinder Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.