plugin
Senior dev
senior-dev
The core of the kit: an orchestrator that triages each task by risk and delegates to product, design, architecture, implementation, QA and review agents.
When to use it
You want an agent team that plans first, tests and proves its work.
Includes: 10 subagents
- Architect engineerDesigns module boundaries and API and database contracts, and records each structural decision as a short ADR.
- ChallengerAttacks the implementation with fuzzing, extreme inputs, failure paths and timeouts to find what breaks.
- Code implementerWrites the production code with TDD inside the files it was assigned, and returns the test command and its exit code.
- Compliance verifierRuns static analysis, security checks and architecture rules, and approves or rejects the change.
- CriticReviews the code without changing it: complexity, duplication, SOLID and maintainability.
- E2E black-box testerStarts the app, runs the user journeys in a real browser and saves screenshots. Reports blocked when it cannot run, never a fake pass.
- Product analystClarifies the business rules and writes the product section of the spec with user stories and acceptance criteria.
- QA testerRuns the affected tests and the full suite once per change, extends the test matrix and closes with done or not done.
- Senior dev orchestratorUnderstands the request, asks what is unclear, plans and delegates to the specialists. It never edits application code itself.
- UI/UX designerMaintains DESIGN.md and writes the design notes for a feature: layouts, states and accessibility.
Includes: 15 skills
- Adversarial challengerStress tests, fuzzing, worst-case inputs, timeouts and concurrency probes that look for the place where the code breaks.
- Black-box testerRuns real user journeys in a browser with Playwright, checks console and network errors, and saves screenshots at four screen widths.
- Code criticAn independent review of complexity, duplication, SOLID, anti-patterns and how easy the code is to change.
- Code implementerWrites production code with test-driven development: a failing test first, then the smallest clean change that passes.
- Code smells expertFinds and classifies code smells and technical debt with the Fowler and Beck catalog, with the reason each one hurts.
- Compliance verifierThe final check before release: non-functional requirements, static analysis, coverage and security, ending in an approved or rejected verdict.
- Context captureSaves what was done, why and how into context/memory/ so another agent or session can pick up the work.
- Context restoreReads the shared memory at the start of a session and summarizes earlier decisions before any work begins.
- Loop engineeringThe three-tier process: sizes each task, runs only the specialists it needs, isolates parallel workers and caps review loops at three.
- Product analystTurns a vague request into clear scope, user stories and testable acceptance criteria in a 50-line spec.
- QA testerDesigns and runs unit, integration and E2E tests and writes a test matrix backed by a real exit code 0.
- Refactoring expertImproves structure, readability and extensibility without changing behavior, with design patterns where they help.
- Senior architecturePragmatic system design with short decision records (ADRs) and an architecture section based on KISS, YAGNI and SOLID.
- Senior dev orchestratorThe playbook the orchestrator follows: restore memory, triage, dispatch agents, verify honestly and save the milestone.
- UI/UX designerDesign systems in a DESIGN.md with tokens, responsive states and WCAG AA accessibility, plus small per-feature design notes.
Includes: 3 hooks
- E2E evidence gateRejects a browser test report that has no real screenshots on disk, so no one can claim a test they never ran.
- Orchestrator role gateRequires a plan before code changes and stops the orchestrator from editing application code itself.
- Universal quality gateDetects the stack and runs its tests and checks before the turn ends, for any language.
Technical description
Senior Developer Orchestrator and specialized subagents for SDLC execution using TDD, clean code, and automated verification.