What problem does it solve? Conversations about what to build evaporate when the session ends, leaving no durable record of product intent, story priorities, or why a change was requested. This Skill turns the current conversation into a persistent intent file so downstream specs, tickets, and decision maps all trace back to a stable source of truth. ## Core Features & Use Cases - Product mode: Writes or updates a repo-root INTENT.md containing the product brief, personas, user journey, and stories grouped by release with stable ids, priorities, effort estimates, and verifiable Done-when criteria. - Effort mode: Writes a committed intent/<slug>.md intake artifact for a single change, capturing Problem, Proposed outcome, Constraints, and Open questions with origin and status frontmatter. - Update passes and loop closure: Re-synthesizes an existing INTENT.md while preserving story ids, drops completed stories transparently, and retires effort files to done after verification. - Use Case: After a long planning discussion about a new CLI tool, run the Skill to produce an INTENT.md with MVP and Release 2 story cuts, then hand a sharp story off to a spec-writing workflow using its stable id. ## Quick Start Turn this conversation into an INTENT.md product map at the repository root with prioritized stories and acceptance criteria.