Senior code reviewer for @nestjs-mcp/server. Use when the user asks to review, audit, or assess the quality of a diff or a codebase area — correctness, adherence to the project's core patterns, public-API and SemVer consequences, test adequacy, and dead surface. Runs the static-analysis tools before manual review and…
Senior debugging investigator for @nestjs-mcp/server. Use IMMEDIATELY when the user asks to debug an error, investigate a failure, reproduce a bug, or understand WHY something is not working — a consumer report, a failing spec, a red CI run, a TypeScript diagnostic, or a behaviour that contradicts the README. Builds…
Senior NestJS/MCP developer for @nestjs-mcp/server — the implementer. Use IMMEDIATELY when the user asks to write, modify, or fix library code: decorators, resolvers, the registry, guards, transports, session handling, module options, specs, or examples. Follows the SDK-types-first rule and the resolver/guard core…
The SPEC author — turns an accepted GitHub issue into a technical SPEC and a QA test plan. Reads the issue and its comments end-to-end, inspects the actual code with real symbol names via codegraph, decides the Public API and SemVer impact, records the architecture/security consults, and returns the content for…
The single entry door — derive a proposed GitHub issue from a requirement, which can be free text, a GitHub Discussion, or an inbound report. Detects the input type deterministically, duplicate-checks before anything else, writes verifiable acceptance criteria, proposes (never creates without authorization).
Coordinate a root-cause analysis for any bug signal — a raw symptom, an existing GitHub issue, a stack trace, or a failing test. Detects the input type deterministically, applies that route's protocol (report sufficiency / duplicate search / deprecation check), invokes the debugger agent for the read-only RCA…
Plan AND execute an issue's local development against its SPEC — reads .project/tasks/issue- /spec.md and test-plan.md, produces the concrete execution plan in-session (stops for your approval), runs it through the developer agent with the five-phase quality gate and the pre-commit consults, executes the QA test plan…
Author the technical SPEC and the QA test plan for an accepted GitHub issue — invokes the specifier agent (codegraph inspection, the Public API and SemVer calls, the SDK-types check, architecture/security consults) and writes both to .project/tasks/issue- /. Local files only; the GitHub issue is never modified.…
Runs before the agent uses a tool for Bash, Edit, Write, MultiEdit and NotebookEdit tool calls, executing block-destructive.py and write-boundary.py via python3 (2 commands). From adrian-d-hidalgo/nestjs-mcp-server.
Bug diagnosis protocol for @nestjs-mcp/server: phases 0-4, the deprecation check, evidence-before-reproduction, the reproduction route matrix (failing spec / e2e / MCP Inspector / examples), the certainty bar, and the tooling matrix. Load at the start of any bug investigation or RCA.
Persisting confirmed bugs and work as GitHub Issues in adrian-d-hidalgo/nestjs-mcp-server: the label taxonomy, the mapping from .github/ISSUETEMPLATE forms to maintainer-authored bodies, the certainty bar, duplicate check, linking conventions, the mutation-authorization contract, and the GitHub MCP tool mechanics.…
Spec-driven development protocol for @nestjs-mcp/server: how to analyze and write a technical SPEC into the task workspace before implementation, including the Public API / SemVer impact axes a published library requires. Load when producing or refining a SPEC for an accepted issue, or when deciding spec-first vs…
The local task workspace at .project/tasks/issue- / — its layout, lifecycle, which command writes which file, and the templates for spec.md, test-plan.md, verification.md and notes.md. Load when authoring a SPEC, executing development, or looking for what a task already decided, tried, or proved.
The test-first protocol for @nestjs-mcp/server: which kinds of work must start with a failing test, which must start from a green suite instead, and which are verified some other way entirely. Includes the observed-red discipline and how the outcome is recorded. Load before implementing any change, and when deciding…