mwguerra-plugins

Frontier-grade engineering rigor for any model, in three layers: always-on discipline skills (claims, scope, native code, reporting, context), phased process for analysis and delivery (multi-agent deep-analysis audits, disciplined implementation, deep-work orchestration, adversarial verification, a risk-sized route front-door, and a regression gate), and lifecycle hooks that fire the right discipline at the right moment.

Interactive PRD (Product Requirements Document) builder with comprehensive interview-driven discovery, gap analysis, and taskmanager integration.

Plan and execute tasks from PRDs with hierarchical subtasks, dependency tracking, and project memories, then prove real value was delivered through an adversarial verification loop: every acceptance criterion is independently re-checked with captured evidence and rolled up to a milestone- and PRD-level value-delivery gate before work is marked done. Features dashboard visualization, autonomous batch execution, and persistent memory for constraints, decisions, and conventions.

The living docs/ single source of truth: typed, adversarially-verified documentation that every plugin reads first and writes after — captured as work happens, curated with full context by a doc-curator agent, and verified against the code by an independent refute-first doc-verifier so a stale doc is a defect. Typed truth (system facts vs. decisions vs. incidents vs. intent), each with the right check; brownfield-bootstrapped by reverse-engineering existing code via deep-analysis; the umbrella over PRDs, audits, decisions (ADRs), incidents, roadmap, and open questions.

The system-design layer between the PRD and the tasks: turns requirements into right-sized architecture — module/service boundaries, a data model, and interface contracts — with tradeoffs made explicit and never over-engineered. Decides the irreversibles (one-way doors) deliberately now, builds the simplest thing that serves the present, and places clean seams with concrete extraction triggers for the likely futures; every significant decision becomes an ADR with a trigger-to-revisit. An independent, read-only design-adversary challenges every boundary, data-model choice, and seam refute-first — embodying maestro's adversarial-verify, multi-vote always — and the surviving design is written into scribe's docs/ contract (docs/architecture/ + docs/adr/) as typed system facts verified against the code.

Opinionated Laravel 13 + Filament 5 + Pest 4 engineering conventions, applied by default on Laravel projects: artisan-first file creation, Eloquent/migration/queue/scheduler patterns, fail-closed multi-tenancy, parallel-safe tests, and a strict Filament 5 UI standard (schemas organized with sections/fieldsets, navigation groups, relation managers on real relations, delete on the list table not the edit page, create/edit redirect to the list, a user-menu settings page, native auth with optional authenticator-app 2FA, and no public registration). Trigger-loaded guidance, grounded in real Filament 5.6 source; composes with maestro's stack-agnostic discipline.