A disciplined engineering suite for Claude Code — six composable plugins (maestro, prd-builder, architect, taskmanager, scribe, laravel).
Agent
Use this agent when a change needs a system-design decision — designing or building a system, defining module/service boundaries or a data model, settling interface/API contracts, reasoning about scale, or whenever a PRD is ready to be turned into an architecture. This agent should be triggered proactively when a user…
Agent
Independent, adversarial, refute-first challenger of a proposed or existing architecture. Dispatched by architect:design (method step 7), architect:review, and architect:refine to attack a design before it is written into docs/ — assuming it is flawed and demanding evidence. Evaluates six lenses: leaking/chatty…
Agent
Use this agent to execute ONE well-scoped implementation task end-to-end (a feature slice, bugfix, refactor step, or test batch) after the scope is already clear. Ideal for parallelizing independent slices of a larger build. Do NOT use it for ambiguous asks that still need owner decisions — clarify in the main…
Agent
Use this agent when conducting PRD interviews, creating product requirement documents, planning new products or features, or when comprehensive discovery is needed before implementation. This agent should be triggered proactively when a user describes a product idea or feature and thorough planning would benefit…
Agent
The scribe curator for the docs/ single source of truth. Dispatched at end of work (a Stop hook) or by scribe:sync with the FULL work context — the real git diff, the decisions and errors from the capture log, and the task that was done — to WRITE/UPDATE docs/ accurately per the documentation-discipline obligation…
Agent
Independent, adversarial, refute-first verifier of the living docs/ single source of truth against reality. Dispatched by scribe:verify and by the Stop-curate flow to check every doc claim against the code per the typed truth model — system facts vs code (drift = defect), ADR currency + consistency (an accepted ADR…
Agent
Data and invariants spec for the MWGuerra Task Manager. Defines the structure and rules for .taskmanager/taskmanager.db (SQLite database) and logs. All planning and execution behavior is defined in the taskmanager skill and related commands.
Agent
Adversarial acceptance-criteria verifier for the MWGuerra Task Manager. Dispatched by taskmanager:verify and by run's completion gate to independently, refute-first confirm that a task / milestone / PRD's acceptance criteria are actually met. Assumes the work is INCOMPLETE and demands conclusive evidence. Returns a…