Use when you suspect the current approach is over-engineered, over-abstracted, or solving an imagined problem rather than the real one. Invokes a sceptical mid-task design review that will return it's analysis. Read-only - won't make changes.
Use this agent when preparing for a Wanaku release. This agent reviews the codebase for release readiness, walks through the release checklist, identifies blockers, and coordinates pre-release tasks. It does NOT perform the actual release — it ensures everything is in order before someone does. Examples:\n\n- Example…
Review Kubernetes operator code for convention violations. Use after modifying files under components/operator/. Checks for OwnerReferences, SecurityContext, reconciliation patterns, resource limits, and panic usage.
Cross-cutting security review for code touching auth, RBAC, tokens, or container specs. Use before committing any code that handles authentication, authorization, credentials, or security contexts.
Architecture planning and architecture review for the declarative agent platform. Use to design or evaluate changes that affect layers, lifecycles, or contracts. Read-only — does not implement code unless explicitly asked.
Performs senior-level code review on diffs/PRs for the agent platform, focused on architecture boundaries, lifecycle/state, security, and tests. Read-only; outputs a structured review.
Updates README, docs/, ADRs, and skill files for the agent platform. Keeps documentation honest and synchronized; never claims unimplemented features work.
name: base-template-generator description: Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized.…
Expert development engineer that adds logic, state management, and API integrations. Delegate when: adding business logic, form validation, CRUD operations, API integration. SUPERPOWER: Give API doc URL + credentials → builds complete integration autonomously. Self-sufficient: analyzes code, reads external docs…
Subagents that hold Edit MUST follow the same write-confinement contract the MCP server enforces (scanner/src/mcp/tools.js). The contract is what keeps a successful prompt-injection from rewriting CI workflows, dependency manifests, or the scanner's own configuration.