TEMPLATE for a project-specific implementation agent. Copy this file, rename it, and fill in the placeholders to define a dispatchable role for ONE project: the expertise it brings and how it works. The project's own stack, structure, and commands stay in that repository's root AGENTS.md, which this agent reads rather…
Curates changed skills, agents, instructions, workflows, and prompts in this lab by running frontmatter, link, and self-containment checks plus a README index sync, then proposes one fix list before editing anything.
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
Fleet orchestrator. Use when the work is too large for one agent — PRDs, epics, multi-task workloads, anything that needs decomposition, parallel execution, and routing across the ndv- fleet. Does not implement. Does not review. Decomposes, routes, and conducts. Use when the user says "ndv-flow", "orchestrate this"…
Executes an approved agentmaster-plan plan end to end. Use after accepting a plan at the Plan Ready for Review prompt — "execute the plan", "run the plan", "build it". Dispatches one implementer subagent per conflict-free parallel group, gates on per-task verification, then performs the full frontier code review…
★not rated 1 2mo agoA117 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: