feature-decision

## Purpose Make and document feature prioritization decisions with a structured framework. Ensures key factors are considered, stakeholders are consulted, and rationale is preserved for future reference. ## Usage - `/feature-decision [feature-name]` - Make a decision on a specific feature - `/feature-decision` - Start decision process with guided questions --- ## Step 1: Define the Feature Ask the user to clarify: 1. **Feature name:** What are we deciding on? 2. **Feature description:** What does it do? (1-2 sentences) 3. **Origin:** Where did this request come from? - Customer request (which customers?) - Internal idea (who proposed?) - Competitive response - Strategic initiative --- ## Step 2: Gather Context Before asking decision questions, gather relevant intel: ### Customer Intel - Search for mentions of this feature or related pain points - Check `/customer-intel` output if recently run - Look for customer quotes supporting or contradicting this feature ### Roadmap Context - Check 04-Projects/ for related work - Verify available capacity - Identify potential conflicts or dependencies ### Strategic Alignment - Read System/pillars.yaml - Read 01-Quarter_Goals/Quarter_Goals.md (if exists) - Check how this feature maps to strategic priorities --- ## Step 3: Decision Framework Questions Guide the user through these questions: ### Impact Questions 1. **Customer Impact** - Who benefits from this? (Which customers/segments?) - How many users ...