What problem does it solve? After a long design discussion, decisions, assumptions, and open questions are scattered across the conversation. This Skill synthesizes what was already agreed into a concise specification with observable acceptance criteria, so implementation can start from a shared, verifiable document instead of chat history. ## Core Features & Use Cases - Decision synthesis: Distinguishes agreed decisions, reasonable assumptions, and unresolved choices, checking the relevant code and existing domain terms before writing. - Structured specification: Covers the user's problem, desired behavior, contracts, acceptance criteria, verification methods, scope exclusions, and open decisions, using the project's own spec format when one exists. - Publication handling: Uses the requested destination and existing tracker conventions, publishing directly when authorized or saving to the project's established documentation location. - Use Case: After discussing a new API endpoint with your AI assistant, ask it to turn the conversation into a spec with acceptance criteria, then publish it to your issue tracker for the team to implement. ## Quick Start Turn our conversation about the export feature into a specification with acceptance criteria and save it to the project docs.
