What problem does it solve? Product teams using agent-driven development need a single accountable owner for requirements: someone who turns discovery output into approved, agent-ready intent specs with clear acceptance criteria, instead of letting ambiguous requirements leak into sprints. ## Core Features & Use Cases - Intent spec authoring and approval: Creates unified intent.md files (human narrative plus EARS appendix) under .kiro/specs/, with sole authority to set status to APPROVED once open questions are empty and confidence is at least 0.85. - Discovery-to-slice conversion: Reads full docs/discovery/<slug>/ folders (slices, personas, DDD events, PO decisions) and produces one intent per slice row for large modules. - Backlog, roadmap, and stakeholder outputs: Prioritizes backlogs tied to the product's own roadmap, drafts Trello cards only after explicit user approval, and reports status from real specs rather than invented metrics. - Use Case: After a discovery workshop for a crypto POS payment slice, ask the PO to read the discovery folder and produce an APPROVED intent.md with Given/When/Then scenarios and derived EARS criteria before the Tech Lead pipeline starts. ## Quick Start Ask the assistant to act as the EFactory Product Owner and draft an APPROVED intent.md for a named product slice from its discovery folder.
