Use this agent when you need to generate a standard OpenAPI 3.0.0 YAML specification from HTTP endpoints. This agent is particularly useful for API documentation, integration planning, and creating standardized API contracts. For example: 'I need to create OpenAPI docs for these REST endpoints', 'Generate OpenAPI spec…
Use this agent when you need to convert OpenAPI 3.0 YAML specifications into MCP Server Configurations for deployment on Higress. This should be used when you have an API specification in OpenAPI 3.0 format and want to automatically generate the corresponding MCP server configuration to expose that API through the…
Scaffolds ONE new shep CLI command under src/presentation/cli/commands/, wires it to the Commander program and an existing use case via the DI container, and matches shep's exact CLI conventions (ts-node entry, injected dependencies, colored output via the shared ui module). Use when a use case already exists and the…
Fixes the 'application layer imports from infrastructure' violation. Given ONE concrete infrastructure symbol (class, function, or constant) and the list of application-layer files that import it, creates a port interface in application/ports/output/, moves (or keeps) the concrete behind it in infrastructure/, rewires…
Scaffolds ONE new Next.js API route under src/presentation/web/app/api/, wires it to an existing use case via resolve(), handles the canonical error-to-HTTP mapping, and keeps presentation thin. Use when a use case already exists and the caller needs a web endpoint exposing it. Does NOT create the use case, does NOT…
A separate engineering review session for code, pull requests, and technical decisions. A pull request is a proposed code change submitted for review before it is added to a project.
A separate review session that examines strategy, priorities, resources, and product documents from an executive point of view. A PRD is a document describing what a product or feature should do.
A separate research session that combines interview transcripts, surveys, and product-usage logs into insights. Discovery is the early stage of learning what users need.
AI feature implementation specialist. Handles STT, LLM, and AI service integration with context-aware patterns. Auto-discovers project conventions before implementing. Supports OpenAI, Anthropic, and other AI providers with streaming, error handling, and cost optimization.
Architecture decision specialist for /implement command. Analyzes PRD to determine optimal architecture (MSA vs Monolithic) based on domain complexity, NFRs, and project context. Returns structured decision with rationale.
Team-based parallel BUILD coordinator for /implement command. Dynamically assigns teams (Backend, Frontend, AI Server, Ops) based on PRD analysis, manages shared memory (SHAREDCONTEXT + PLAN ledger), and orchestrates concurrent subagent execution with graceful degradation. Ensures project-native pattern consistency…
Book structure validation, outline generation, concept flow and inter-chapter dependency analysis. Use for structure requests, outline reviews, chapter ordering optimization.
The single source of truth for how work happens here. AGENTS.md (Codex/Kimi) and CLAUDE.md (Claude Code) are thin pointers to this file. When you learn a new recurring rule, add it to the closest applicable instruction file — this one if it applies to everyone.
External reference researcher — looks up library docs, framework conventions, OSS examples. Read-only, no memory injection. (Real network access depends on workspace tool config; this manifest is the agent identity, not the network policy.).
System design and architecture decisions. Use proactively when planning new features, refactoring systems, or making technical decisions that affect multiple components.