oats-autonomous-agents

Translate git history and orchestrator logs into authentic social content. Use when turning recent technical work into tweets, Dev.to posts, or changelog entries without manual summarisation.

Red team the staging environment with injection attacks, rate limit probes, and auth bypass attempts. Use before major releases or when adding new user-input surfaces.

Deploy Your Project to production safely. Use before any deployment, after code changes, or when asked to push to prod.

Facilitate a structured CONVERSATIONAL meeting between department agents via claude-peers — named phases (Diverge, Clarify, Challenge, Build, Stress Test, Converge, Decide) with state machine navigation. Agents push back on each other and build on each other's ideas. Minimum path: Diverge → Challenge → Build → Stress Test. Early exit only after Stress Test. NOT for simple task dispatch (use orchestra-management). NOT for solo research (use rd-architect).

Manage the 6-department orchestra via claude-peers. Use when dispatching tasks, coordinating departments, reviewing results, or shaping department behavior.

Write emails, social posts, and newsletter submissions for Your Project. Use when creating maker outreach, blog content, social media posts, or press pitches.

Research & Development Architect — researches improvements, writes proposals, manages autoresearch loops. Use when hitting a bottleneck, exploring new tech, or running improvement experiments.

Audit LLM token usage across departments, identify waste, and recommend model/caching optimisations. Use when costs are rising or before scaling the orchestra.

Navigate the staging site as a specific developer persona and report UX confusion points. Use when auditing flows for a specific user type before a release.

Audit the MCP server experience from an agent's perspective. Use when checking search quality, response richness, or first-impression for new MCP installs.

Strategy for getting Your Project's first paying customer. Use when discussing revenue, pricing, monetization, or what to sell. Based on Minimalist Entrepreneur principles adapted for our stage.

XSS prevention and HTML safety patterns for Your Project's f-string templates. Use when writing or reviewing any route file that renders HTML.

Run a maker outreach campaign through the orchestra. Use when sending claim emails, finding maker contacts, or expanding distribution to tool makers.

Safely update data on the production Your Project database via Fly SSH. Use when fixing tool metadata, pushing autopsy data, or running DB queries on prod.

Structured S&QA review framework for every task. Use before approving, challenging, or vetoing any work dispatched by Master.