laravel

mwguerra-plugins — a disciplined engineering suite for Claude Code

Six plugins for Claude Code. Five compose into one end-to-end workflow — turn an idea into a verified, shipped change with frontier-grade rigor (requirements → design → tasks → execution → living docs), with verification that actually enforces before work is called done — and a sixth (laravel) supplies stack-specific conventions that compose with the rest.

Plugin	Role
maestro	Engineering discipline: always-on behavior skills, phased process (deep-analysis, implementation, deep-work, adversarial-verify, regression), a risk-sized route front door, and lifecycle hooks — six advisory + two enforcing verification gates (hard-block a commit / turn-end until verified).
prd-builder	Interview-driven PRDs → docs/prd/.
architect	The system-design layer between PRD and tasks → docs/architecture/ + ADRs, adversarially challenged.
taskmanager	Decompose a PRD into tasks (SQLite), execute, and prove value via an adversarial done-gate (criteria + regression).
scribe	The living docs/ single source of truth: capture → curate → verify, so a stale doc is a defect.
laravel	Opinionated Laravel 13 + Filament 5 + Pest 4 conventions — artisan-first, the Filament UI standard, fail-closed multi-tenancy, parallel-safe Pest — applied by default on Laravel projects. The stack idiom that composes with maestro's stack-agnostic discipline.

Start here

Install (from this marketplace):

/plugin marketplace add mwguerra/plugins
/plugin install maestro@mwguerra-plugins prd-builder@mwguerra-plugins architect@mwguerra-plugins taskmanager@mwguerra-plugins scribe@mwguerra-plugins laravel@mwguerra-plugins

Requires jq, sqlite3 (taskmanager's store), and a sha256 tool (sha256sum/shasum/openssl) for maestro's verification gates.

Not sure where to begin? Ask maestro:route — it sizes a request by scope/risk and names the pipeline to run. See a feature whole: maestro:journey <slug> renders one feature's full path across the suite (idea → PRD → design → tasks → verified → regression-clean → shipped).

Greenfield (new project):

1. scribe:init — scaffold the docs/ single source of truth.
2. prd-builder:prd — interview an idea into docs/prd/.
3. architect:design — turn the PRD into docs/architecture/ + ADRs.
4. taskmanager:init → taskmanager:plan docs/prd/prd-<slug>.md → taskmanager:run.
5. scribe:sync — fold the work into living docs; scribe:verify checks docs against the code.

Brownfield (existing code): start with scribe:init (it reverse-engineers docs/ via a maestro deep-analysis pass), then use maestro:route per task. For a quick change, just maestro:implement; for an audit, maestro:deep-analysis.

The two things that make it "verified, not vibes"

• Verification is enforced, not nudged. maestro's verify_commit_gate hard-blocks git commit until the change is recorded as tests-green and adversarially checked in .maestro/ledger.log (or a logged waiver is filed); verify_stop_gate blocks ending a turn with unverified work. One command satisfies it: bash <maestro>/hooks/lib/ledger.sh pass all "<what you ran + what survived>". See the verify-gates smoke test. To disable, remove the gate entries from maestro/hooks/hooks.json.
• docs/ is the contract. Every plugin reads docs/ first and writes it after; the doc-verifier checks each claim against the code. The canonical layout lives in scribe/skills/documentation-discipline/references/docs-layout.md.

Docs

Per-plugin READMEs: maestro · prd-builder · architect · taskmanager · scribe · laravel. Suite architecture & conventions: CLAUDE.md.

Tests

bash taskmanager/tests/test_sql_queries.sh     # SQL layer (queries, views, done-gate)
bash taskmanager/tests/test_lifecycle_e2e.sh   # full init→plan→run→verify lifecycle
bash maestro/tests/test_verify_gates.sh        # the enforcing gates + ledger

MIT