What problem does it solve? Turning a rough feature idea into a scoped, backlog-ready product artifact is slow and error-prone, especially when drafts mix shipped behavior with proposals, use stale terminology, or lack measurable success criteria. ## Core Features & Use Cases - Structured PRD Drafting: Produces proposals with problem statement, target users, goals and non-goals, user stories, acceptance criteria, risks, and success metrics aligned to the active JoyJoin product canon. - Backlog-Ready Artifacts: Converts scoped ideas into issue-ready items with Given/When/Then acceptance criteria and explicit dependencies. - Canon Alignment: Grounds terminology in PRODUCT_REQUIREMENTS.md, DEVELOPER_QUICK_REFERENCE.md, and docs/README.md, separating current state from proposed changes. - Use Case: Before engineering kickoff for a new credits feature, generate a proposal that defines scope boundaries, measurable conversion targets, and engineering impact hypotheses so implementation does not start from ambiguous goals. ## Quick Start Ask the assistant to draft a PRD for your feature idea, including user stories, acceptance criteria, non-goals, and measurable success metrics.
