skill-intent-contract

# Intent Contract System ## Purpose The intent contract creates a **persistent record of user intent** that: - Captures what the user is trying to accomplish - Defines success criteria upfront - Establishes boundaries and constraints - Travels through the entire workflow - Validates final outputs against original intent This closes the loop between intention and delivery. --- ## Intent Contract Structure The intent contract is stored in `.claude/session-intent.md` and follows this format: ```markdown # Intent Contract **Created**: [ISO timestamp] **Workflow**: [discover/embrace/review/etc.] **Status**: [active/validating/completed] ## Job Statement What the user is trying to accomplish (JTBD framework). [User's goal in plain language] ## Success Criteria ### Good Enough - [Minimum viable success criterion 1] - [Minimum viable success criterion 2] ### Exceptional - [Excellence criterion 1] - [Excellence criterion 2] ## Boundaries What this should NOT be: - [Boundary 1: What to avoid] - [Boundary 2: What's out of scope] ## Context & Constraints **Stakeholders**: [Who needs this to work for them] **Existing Assets**: [What to build on] **Timeline**: [Time constraints if any] **Technical Constraints**: [Platform, language, dependencies] ## Clarifying Context [Any answers from the 3-question pattern] ## Validation Checklist - [ ] Meets "good enough" criteria - [ ] Respects all boundaries - [ ] Works for all stakeholders - [ ] Builds on existing assets appropriate...