Create feature spec

Use this workflow when the user requests a new feature, a substantial refactor, or asks to "formalize" a design.

1. Analyze Request: Understand the core problem, proposed solution, and domain impact.
2. Generate Artifact: Create a new file in the brain artifacts directory named feature_spec_[feature_name].md.

3. Template Structure: Use the following markdown structure:

   # Feature Specification: [Feature Name]
   
   **Feature**: [Name]
   **Status**: Draft
   **Last Updated**: [Date]
   
   ## 1. Executive Summary
   
   Brief overview of what this feature is and why we are building it.
   
   ## 2. Problem Statement
   
   - **Current State**: What is broken or missing?
   - **Impact**: Why does this matter?
   
   ## 3. Solution Architecture
   
   High-level design. Diagrams (Mermaid) encouraged.
   
   - **Core Concepts**: New entities, logic flows.
   - **Integration**: How it fits into existing modules.
   
   ## 4. Domain Specifics
   
   Breakdown by domain (Access, Maintenance, Finance, etc.) if applicable.
   
   ## 5. Data Models
   
   TypeScript interfaces or Database Schemas.
   
   \`\`\`typescript
   interface Example {
   id: string;
   // ...
   }
   \`\`\`
   
   ## 6. Migration Strategy
   
   How do we get from A to B?
   
   1.  Phase 1: [Step]
   2.  Phase 2: [Step]
   
   ## 7. Verification Blueprint (Standard 102)
   
   - **Primary Persona**: (e.g., PrimaryOwner - from Persona Book)
   - **Forensic Success State**: (What constitutes a pass in the data?)
   - **Boundary Hazards**: (At least 2 edge cases, e.g., zero value, concurrency)
   - **Telemetry Signal**: (Audit ID to be recorded)
   - **Tooling**: (@tool playwright, etc.)
   - **Environment**: (@env sprint, etc.)
   

4. Review: Present the spec to the User via notify_user for approval before writing code.