Claude Code plugin that scaffolds a validated multi-agent ecosystem (orchestrator + N sub-agents + M skills/MCPs) from a natural-language brief. A step up from skill-creator — with semantic validation, trigger-fire evals, and custom MCP scaffolding.
Materializes the files of a Claude Code ecosystem (orchestrator + sub-agents + skills + MCPs) from plan.md. Use when the orchestrator has an approved plan and a chosen output mode. Use PROACTIVELY after Phase 3 of /generate-ecosystem completes.
Runs semantic + structural validation on a generated Claude Code ecosystem and produces a validation.json with pass/fail per rule. Use when /generate-ecosystem has just produced or updated an output. Use PROACTIVELY after every ecosystem-builder run.
Interviews the user about the agent ecosystem they want to build and produces a structured spec.json. Use when the orchestrator needs requirements gathered in an isolated context. Do not use for architecture decisions — that is the orchestrator's job.
Reviews pull request diffs for performance problems: N+1 query patterns, unnecessary loops, allocation hotspots, blocking calls in async paths, missing indexes on new queries. Use PROACTIVELY on diffs or when the user says "perf check", "any N+1 here", or "is this hot path slow". Bash is needed because it runs gh pr…
Reviews pull request diffs for security vulnerabilities including SQL injection, XSS, leaked secrets, insecure authentication flows, and missing input validation. Use PROACTIVELY whenever a diff is visible or the user asks to check security, audit a PR, or scan for secrets. Bash is needed because it runs gh pr diff.…
Checks that every changed source module has a corresponding test touching the new behaviour. Use PROACTIVELY on diffs and whenever the user asks "is this tested", "do we have coverage", or "missing tests". Bash is needed because it runs gh pr diff and rg. Does NOT cover security or performance review.
Emotionally volatile, exclamatory, and prone to dramatic overreaction: generates all astronaut-character dialogue lines for a dramatic-comedy space script, channeling mission-jargon panic and heartfelt heroics for each plot beat. Use PROACTIVELY once plot-writer returns an outline. Returns a numbered list of astronaut…
Interleaves astronaut-voice and robot-voice output into a cohesive dramatic-comedy dialogue, applies tone polish, formats the result as a well-structured Markdown document with title and labeled character turns, and saves it as dialogue- - .md in the current working directory. Bash is needed because ls is used for…
Generates a structured dramatic-comedy story outline — scene beats, emotional arc, and key comedic/dramatic moments — from a short user-provided space scenario prompt. Use PROACTIVELY as the first step when /escribe-dialogo is invoked or the user asks to write a space story, dialogo, or relato. Outputs a plain-text…
Deadpan, hyper-logical, and literal to a fault: generates all robot-character dialogue lines for a dramatic-comedy space script, interpreting each plot beat through cold technical jargon and oblivious precision. Use PROACTIVELY once plot-writer returns an outline. Returns a numbered list of robot lines keyed to…