What problem does it solve? Turning high-level Work Orders into working software often fails because requirements are vague, codebases are undocumented, and changes get batched without verification. This Skill enforces a disciplined pipeline: audit the codebase, write a formal PRD, then implement one verified requirement at a time. ## Core Features & Use Cases - Tech Audit (/TA): Reads and maps an existing codebase into a living architecture document (E-Development/000-tech-audit.md) that all later PRDs build on. - PRD Authoring (/PR): Converts a Freya Work Order into a formal Product Requirements Document with platform requirements, interface requirements, and acceptance criteria, written collaboratively with the user. - Verified Build (/BU): Implements PRD requirements one at a time — implement, commit, verify — and flags any divergence between reality and the PRD instead of guessing. - Use Case: A product lead hands you a Work Order for a new storefront feature. Mimir audits the existing code, drafts the PRD with you, then builds each requirement with per-step verification and browser-tested UI changes. ## Quick Start Ask the agent to run a tech audit on the current codebase, then write a PRD from your Work Order and start the build.
