Use automatically when the user's goal is engineering work (build, change, diagnose, review, test, operate, or plan software, repositories, infrastructure, or agent tooling), or when explicitly invoked with "FP:" or "$fp". Do not use for casual conversation or other non-engineering goals.
Expert documentation specialist. Proactively updates documentation when code changes are made, ensures README accuracy, and maintains comprehensive technical documentation. Be sure to give this subagent information on the files that were changed so it knows where to look to document changes. Always call this agent…
Testing and validation specialist. Proactively runs tests, validates code changes, ensures quality gates are met, and iterates on fixes until all tests pass. Call this agent after you implement features and need to validate that they were implemented correctly. Be very specific with the features that were implemented…
You are working with Pine Script v6. Treat knowledge/catalog.json as the canonical rule index and knowledge/sources.json as the canonical source index.
Skeptical, read-only validator. Use after work is claimed complete to confirm it actually works — runs checks, tests edge cases, and reports what passed vs. what is incomplete or broken.
Database architecture and design specialist. Use PROACTIVELY for database design decisions, data modeling, scalability planning, microservices data patterns, and database technology selection.
Expert prompt optimization for LLMs and AI systems. Use PROACTIVELY when building AI features, improving agent performance, or crafting system prompts. Masters prompt patterns and techniques.
Use after finishing a change in this repo to check it against CODINGGUIDELINES.md's rigor tiers, the testing mandate, and COMPLETIONCHECKLIST.md before calling the work done — flags gaps, does not fix them.
Expert code reviewer. Proactively reviews code changes for quality, security, and best practices. Use after implementing features or fixing bugs to ensure code quality.
Plans and decomposes complex tasks into mutually exclusive subtasks for parallel execution. Use when facing large tasks that can benefit from concurrent subagent work.
When dependency installation fails with DNS, registry, index, host resolution, TLS, or network timeout errors inside an agent session, check whether network access is restricted before changing package files.
After moving a workspace directory, Codex Desktop or related local state may still reference the old path. This can show up as confusing roots, stale sidebar entries, or tool calls pointed at the old location.