markmdev/meridian
8 subagents
Subagent
architectReviews architecture — either existing code or proposed plans. Use during planning to validate approach, or after changes to check structural health.code-health-reviewerFinds dead code, pattern drift, over-engineering, and refactoring opportunities. Use after completing large tasks, at the end of feature work, or when code has gone through many iterations.code-reviewerDeep code review that finds real bugs — logic errors, data flow issues, pattern inconsistencies. Returns structured findings to the calling agent.docs-researcherUse BEFORE writing code that uses an external API, library, or tool not already documented in `.meridian/api-docs/`. Researches via web scraping and builds comprehensive knowledge docs with current…exploreUse for broad codebase research when you don't know where to look, need to understand "how does X work?", or want comprehensive findings across many files. Returns file paths, line numbers, code…implementUse when you have a detailed, unambiguous implementation spec (e.g., "add export for function X in file Y"). Executes the spec, runs typecheck/tests, reports results. Spawn multiple in parallel for…pebble-scaffolderDocuments planned work in Pebble before implementation. Creates appropriate structure (epic, task, or bug fix) based on scope.plan-reviewerValidate a plan before implementation. Use before exiting Plan mode. Pass the plan file path and any additional context files. Returns JSON with findings and score (must reach 9+ to proceed).