A disciplined engineering suite for Claude Code — six composable plugins (maestro, prd-builder, architect, taskmanager, scribe, laravel).
Command
Design the system between the PRD and tasks — right-size the present, place clean seams with explicit extraction triggers, decide the irreversibles, adversarially challenge the design, and write a verifiable architecture + ADRs into docs/architecture/ and docs/adr/ per scribe's contract.
Command
Evolve an existing design — update docs/architecture/ and supersede/add ADRs for new requirements, a fired extraction trigger, or review findings, then re-run the design-adversary on the change.
Command
Adversarially challenge an existing design (docs/architecture/ + docs/adr/) — multi-vote, structured findings, read-only and advisory.
Command
Independently re-check a conclusion, fix, or design by spawning an agent prompted to refute it — not affirm it.
Command
Multi-agent deep audit of the current project — adversarially verified findings + prioritized roadmap, published to docs/deep-analysis/.
Command
Run a large, multi-place, uncertain task to completion — plan, adversarial review, serial execute, synthesize & verify.
Command
Implement a feature, fix, or whole app with the full disciplined process — clarify, investigate, plan, build, verify, deliver.
Command
Show one feature's whole journey across the suite — idea → PRD → design → tasks → verified → regression-clean → shipped — by composing the existing per-plugin views (read-only; no new store).
Command
Prove a change didn't break existing work — run the suite + a bounded refute-first blast-radius probe vs docs/architecture/ contracts + honest coverage — and emit a structured regression verdict that taskmanager's done-gate enforces.
Command
Route a request to the right top-level pipeline by scope and risk — name the ordered sequence of existing entry points (analysis / trivial change / bug fix / feature-high-risk / health), advisory, then hand control back.
Command
Document a bug fix with problem analysis, root cause investigation, and regression testing strategy.
Command
Create a feature-focused PRD with lighter interview process optimized for new features within existing products.
Command
Start a comprehensive PRD interview to transform an idea into a complete Product Requirements Document.
Command
Bootstrap the living docs/ single source of truth — scaffold the canonical skeleton (greenfield) or reverse-engineer it from real code via a maestro deep-analysis pass (brownfield). Idempotent; never clobbers existing docs.
Command
Consolidate recent work into docs/ then adversarially verify it — curate the capture log + git diff into ADRs/incidents/STATUS/roadmap/open-questions, then check every claim against the code.
Command
Adversarially verify docs/ against the typed truth model + cross-doc staleness — multi-vote, advisory drift report.
Command
Export SQLite database to JSON or individual task markdown files.
Command
Manage project memories (constraints, decisions, conventions) - add, list, search, update, deprecate with FTS5 full-text search.
Command
Parse a PRD into tasks, or expand existing tasks into subtasks.
Command
Research a topic using web search and codebase analysis, storing findings as memories.
Command
Execute a single task or batch of tasks with memory support and status propagation.
Command
View dashboard, task details, next tasks, or statistics.
Command
Update task fields, status, scope, tags, dependencies, or position.