specpulse 1.0.6__py3-none-any.whl → 1.1.0__py3-none-any.whl

{specpulse-1.0.6.dist-info → specpulse-1.1.0.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: specpulse
-Version: 1.0.6
+Version: 1.1.0
 Summary: Specification-Driven Development Framework
 Home-page: https://github.com/specpulse
 Author: SpecPulse
@@ -66,11 +66,12 @@ Dynamic: requires-python
 
 SpecPulse revolutionizes AI-assisted development by enforcing a **specification-first approach**. Instead of jumping straight into code, SpecPulse ensures every feature starts with clear specifications, validated plans, and tracked tasks - guaranteeing quality from day one.
 
-> **Latest Update (v1.0.6)**: 
-> - 🐛 **Critical Bug Fix**: Fixed cross-platform template initialization bug
-> - ✅ **Proper Resource Management**: All cross-platform scripts now correctly copied from @specpulse/resources
-> - ✅ **Complete Script Availability**: All 12 scripts (4 types × 3 platforms) properly installed
-> - ✅ **Enhanced Package Configuration**: Fixed package data inclusion for Python and PowerShell scripts
+> **Latest Update (v1.1.0)**: 
+> - 🔧 **Command Prefix System**: All commands now use `sp-` prefix to avoid conflicts
+> - 📋 **Multi-Spec Workflow**: Support for multiple specs/plans/tasks per feature
+> - 🗂️ **Versioned File System**: Automatic spec-001.md, plan-001.md, task-001.md naming
+> - 🎯 **Context Detection**: Automatic feature detection using git branches
+> - 🤖 **Enhanced AI Integration**: Improved manual workflow control
 > - ✅ **Improved Error Handling**: Better resource path resolution and script copying operations
 
 ### Why SpecPulse?
@@ -126,21 +127,21 @@ specpulse init --ai gemini
 
 ```bash
 # Initialize a new feature
-/pulse user-authentication
+/sp-pulse user-authentication
 # Creates structure for 001-user-authentication feature
 
 # Create the specification  
-/spec create user login with OAuth2 and email/password
-# Or just: /spec (for interactive mode)
+/sp-spec create user login with OAuth2 and email/password
+# Or just: /sp-spec (for interactive mode)
 
 # Generate implementation plan
-/plan generate
-# Or: /plan validate (to check existing plan)
+/sp-plan generate
+# Or: /sp-plan validate (to check existing plan)
 
 # Break down into tasks
-/task breakdown
-# Or: /task update (to update task status)
-# Or: /task status (to see progress)
+/sp-task breakdown
+# Or: /sp-task update (to update task status)
+# Or: /sp-task status (to see progress)
 ```
 
 ### Step 4: Validate & Ship
@@ -264,23 +265,22 @@ Claude and Gemini use slash commands that accept arguments via `$ARGUMENTS`:
 - **Unicode Support**: Full international character support (≤, ≥, →, ←)
 
 ```bash
-/pulse user-authentication     # Start new feature with name
-/spec create OAuth2 login      # Create specification with description
-/spec update                   # Update existing specification
-/spec validate                 # Validate specification completeness
-/plan generate                 # Generate plan from specification
-/plan validate                 # Validate plan against constitution
-/task breakdown                # Create task list from plan
-/task update                   # Update task statuses
-/task status                   # Show current progress
+/sp-pulse user-authentication     # Start new feature with name
+/sp-spec create OAuth2 login      # Create specification with description
+/sp-spec update                   # Update existing specification
+/sp-spec validate                 # Validate specification completeness
+/sp-plan generate                 # Generate plan from specification
+/sp-plan validate                 # Validate plan against constitution
+/sp-task breakdown                # Create task list from plan
+/sp-task update                   # Update task statuses
+/sp-task status                   # Show current progress
 ```
 
 **Behind the Scenes:**
 - Commands capture arguments using `$ARGUMENTS` variable
 - **Multi-platform scripts** in `resources/scripts/` folder process the arguments:
-  - `pulse-*.py` - Python scripts (universal)
-  - `pulse-*.ps1` - PowerShell scripts (Windows)
-  - `pulse-*.sh` - Bash scripts (Linux/macOS)
+  - `sp-pulse-*.py` - Python scripts (universal)
+  - `sp-pulse-*.sh` - Bash scripts (Linux/macOS)
 - AI reads templates from `resources/templates/` folder
 - Results are saved in `specs/`, `plans/`, `tasks/` folders
 - Memory system tracks progress in `memory/` folder
@@ -325,19 +325,19 @@ my-project/
 │   └── decisions.md    # Architecture Decision Records
 ├── specs/               # Feature specifications
 │   └── 001-feature/
-│       └── spec.md
+│       └── spec-001.md
 ├── plans/               # Implementation plans
 │   └── 001-feature/
-│       └── plan.md
+│       └── plan-001.md
 ├── tasks/               # Task breakdowns
 │   └── 001-feature/
-│       └── tasks.md
+│       └── task-001.md
 ├── templates/           # Customizable templates
 ├── scripts/             # Shell scripts for AI execution
-│   ├── pulse-init.sh    # Feature initialization
-│   ├── pulse-spec.sh    # Specification creation
-│   ├── pulse-plan.sh    # Plan generation
-│   └── pulse-task.sh    # Task breakdown
+│   ├── sp-pulse-init.sh    # Feature initialization
+│   ├── sp-pulse-spec.sh    # Specification creation
+│   ├── sp-pulse-plan.sh    # Plan generation
+│   └── sp-pulse-task.sh    # Task breakdown
 └── PULSE.md            # Project manifest
 ```
 
@@ -349,7 +349,7 @@ Create project-specific templates:
 
 ```bash
 # Copy and modify templates
-cp templates/spec.md templates/custom-spec.md
+cp templates/spec-001.md templates/custom-spec.md
 # Edit to match your needs
 ```
 
@@ -413,7 +413,7 @@ specpulse validate --component constitution
 **Solution**: Check template path in config.yaml
 
 ### AI Commands Not Working
-**Problem**: `/pulse` commands not recognized
+**Problem**: `/sp-pulse` commands not recognized
 **Solution**: Ensure you ran `specpulse init --ai claude` or `--ai gemini`
 
 </details>

specpulse-1.1.0.dist-info/RECORD

@@ -0,0 +1,41 @@
+specpulse/__init__.py,sha256=S9i2N7RizTFgCe7PsAehlM3Ba_FtbAQPxCDSKcO_tbQ,270
+specpulse/cli/__init__.py,sha256=DpX6FoRJtSNjudsmZ3mTih_RIaWyiIgxew4-f8mOmFY,70
+specpulse/cli/main.py,sha256=U8BzBSrnVbkudKdd0ADfeQmmmjbT5OpR819I6gVp3OE,23478
+specpulse/core/__init__.py,sha256=VKHGdPDM38QM9yDIq05jxol4q8WFlFAeltOzYLsPuto,132
+specpulse/core/specpulse.py,sha256=dGOuDVaeTrUHa3u-tGs2yN3A-ao1TnI6Cu5uTUjFTWA,31753
+specpulse/core/validator.py,sha256=dnaNUx7tj8V2K1TE6WPwrNWEiCpqC_b_DKryq6-A7Hk,12057
+specpulse/resources/commands/claude/sp-continue.md,sha256=3_vikDSNRN0slNtKQGWl9dWEgkT-Q7nFpUxHKnzBCKs,5175
+specpulse/resources/commands/claude/sp-plan.md,sha256=eOVioaBpsOhEoFcFRRaxqBULIWbGx85A1L-ZwQyiUiQ,7009
+specpulse/resources/commands/claude/sp-pulse.md,sha256=IjoB2NeoTIjJEATcxG0mCfagRuzlRb7CwHawiotAIjk,5023
+specpulse/resources/commands/claude/sp-spec.md,sha256=i3NmQbzbWlFSlu9jJpg6j3TyfW2TCAoMH9qVtJvIWW0,6242
+specpulse/resources/commands/claude/sp-status.md,sha256=pUcFsYdmvAPTA1BdRjiN-AWi9I8IN4GiEErjfK4wNOU,4633
+specpulse/resources/commands/claude/sp-task.md,sha256=El9iwPTlLPJdbJKYKYkDwBzRy_JvWoqu_AjPgLQ0WVs,9168
+specpulse/resources/commands/gemini/sp-continue.toml,sha256=_iyo_g9IV0-FtIpiVknKNaegmhyc3DHb41lvfpf7anU,1784
+specpulse/resources/commands/gemini/sp-plan.toml,sha256=ROG9G3V9VGahHmQqdxs2znQgnrYx_8Hg4Wu3Yzp0Fpo,2271
+specpulse/resources/commands/gemini/sp-pulse.toml,sha256=YFpp1V_jCnP1mODU-9jpXyoGW61oSX-Y1YXewDCYYac,1307
+specpulse/resources/commands/gemini/sp-spec.toml,sha256=0U5BIiCMGaXDvp4KoXEKu08VpL54iCiMMuoVoxRG1BE,2284
+specpulse/resources/commands/gemini/sp-status.toml,sha256=PNZvCwwbzTYyA5Bm2M4SYw1ndz0vRqCkqT-_3pYJ_Qs,1979
+specpulse/resources/commands/gemini/sp-task.toml,sha256=fuQkdK8wI279wy_qAOKGqxJQqIQc5C9xCDf7oNoCah8,2663
+specpulse/resources/memory/constitution.md,sha256=34M0dMDzeE9JfAaNjK1S9uxVSD1I8KIaEtb8C3_7Ru8,8341
+specpulse/resources/memory/context.md,sha256=rMQGXeJ9TaKmx2BVfQd8X6_ekwrKDdBsvWObCTiOTC0,812
+specpulse/resources/memory/decisions.md,sha256=ZwzVyOPB2mIzwveWpGmedej7ncI81GALg8WVy6AeZA4,686
+specpulse/resources/scripts/sp-pulse-init.py,sha256=-_L9TOr1zKCSJOS8dBUbeKOkWBlR5I6kB5ZUuEF3GBQ,6688
+specpulse/resources/scripts/sp-pulse-init.sh,sha256=Be3ogbKQCy2WMONC22Ht-15gxgQS0sB7U74EoSrDnMU,3164
+specpulse/resources/scripts/sp-pulse-plan.py,sha256=PYyvVPP0Wo-6VAAnRAeesfv6gV2qegs6nEWwLeqBTj4,8614
+specpulse/resources/scripts/sp-pulse-plan.sh,sha256=0G6WMDV2ChO4kkulgEL49qZFg7adwf3-lqeH3Rvs7T4,4199
+specpulse/resources/scripts/sp-pulse-spec.py,sha256=IzThoWPcfgApJ_FeTGoA54_LEoWahQkgLeEHpHx0bKs,7485
+specpulse/resources/scripts/sp-pulse-spec.sh,sha256=TVA1ktylZZy_9yj-4inncP1_FoVp8vteP5kaWelLeks,4194
+specpulse/resources/scripts/sp-pulse-task.py,sha256=hVi7E81azLWqRuzEYtzz_uIJKahfh-mGu8zxOvwjsVY,10826
+specpulse/resources/scripts/sp-pulse-task.sh,sha256=RmV6fIVIssK9QR4jAKzHhghrl4voG7PpXXC0yPi6_Rk,5039
+specpulse/resources/templates/plan.md,sha256=KSCB5HvYRjqrM-VTe7nwJgR1MjGI748YE2BJtn41g4Q,6689
+specpulse/resources/templates/spec.md,sha256=yVWn2LhZn0IMLJ9XuBjPWSWNS4GYJFowRrqRMT2wJf4,3748
+specpulse/resources/templates/task.md,sha256=mGRlE4WD2E1Lh5gGr7kyOEmoXDbjLhUVMG9D7ZGCpmw,5357
+specpulse/utils/__init__.py,sha256=VTGRDsVLl2JIXYyHB9Sidxj5acY_W-LJI2MMtY1pwb0,122
+specpulse/utils/console.py,sha256=xn4Koc1_ph61bvBTlvPOwAbqZ5ac7TZ51xTWJbwG0sc,12973
+specpulse/utils/git_utils.py,sha256=RzJBZoyWp5on1_wq2lY1bs__UJsGKSDpAUeDKFdRYlQ,6095
+specpulse-1.1.0.dist-info/licenses/LICENSE,sha256=ImSFezK-Phy0oTBqZipcajsJfPZT8mmg8m3jkgNdNhA,1066
+specpulse-1.1.0.dist-info/METADATA,sha256=57zA7ltiXaOvCGhydaZRtaLVbIX6MocMHbx9g0ZFlRI,16610
+specpulse-1.1.0.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
+specpulse-1.1.0.dist-info/entry_points.txt,sha256=GwMaCKWSCFZlJMrTNavEYrnREynIS6dM3B0ILxnaouA,83
+specpulse-1.1.0.dist-info/top_level.txt,sha256=pEfkFil5xe38J00OHrBrJ07xpbm6bRnGhI8B07O9KeI,10
+specpulse-1.1.0.dist-info/RECORD,,

specpulse/resources/commands/claude/pulse.md

@@ -1,91 +0,0 @@
----
-name: pulse
-description: Initialize a new feature with SpecPulse framework
-allowed_tools:
-  - Bash
-  - Read
-  - Write
-  - Edit
-  - TodoWrite
----
-
-# /pulse Command
-
-Initialize a new feature following SpecPulse methodology with constitutional compliance.
-
-## Usage
-```
-/pulse <feature-name> [feature-id]
-```
-
-## Implementation
-
-When called with `/pulse $ARGUMENTS`, I will:
-
-1. **Validate arguments** and extract feature name + optional ID
-2. **Run initialization script** with cross-platform detection:
-   - **Windows**: `powershell scripts/pulse-init.ps1 "$FEATURE_NAME" "$OPTIONAL_ID"`
-   - **Linux/macOS**: `bash scripts/pulse-init.sh "$FEATURE_NAME" "$OPTIONAL_ID"`
-   - **Python Fallback**: `python scripts/pulse-init.py "$FEATURE_NAME" "$OPTIONAL_ID"`
-3. **Create complete feature structure**:
-   - Generate feature ID (001, 002, etc.) or use provided ID
-   - Create sanitized branch name: `ID-feature-name`
-   - Create directories: `specs/ID-feature-name/`, `plans/ID-feature-name/`, `tasks/ID-feature-name/`
-   - Copy AI-optimized templates to feature directories
-   - Update `memory/context.md` with current feature metadata
-   - Create and switch to git branch if in git repository
-
-4. **Validate structure** and report comprehensive status
-5. **Create todo list** for tracking feature development progress
-
-## Constitutional Compliance
-
-**Article I: Simplicity**
-- [ ] Feature name is clear and specific
-- [ ] No unnecessary abstractions in initial structure
-- [ ] Single responsibility per feature
-
-**Article II: Anti-Abstraction**  
-- [ ] Direct template usage (no wrapper layers)
-- [ ] Minimal initial structure
-- [ ] Framework-ready files
-
-## Example
-```
-User: /pulse user-authentication-oauth2
-```
-
-I will:
-- Run: `bash scripts/pulse-init.sh "user-authentication-oauth2"`
-- Create: `specs/001-user-authentication-oauth2/spec.md`
-- Create: `plans/001-user-authentication-oauth2/plan.md`  
-- Create: `tasks/001-user-authentication-oauth2/tasks.md`
-- Branch: `001-user-authentication-oauth2`
-- Status: `STATUS=initialized, BRANCH_NAME=001-user-authentication-oauth2`
-
-## Error Handling
-
-Enhanced validation includes:
-- Feature name sanitization (alphanumeric, hyphens only)
-- Directory creation validation
-- Template existence verification
-- Git repository validation
-- Context file management
-
-## Next Steps (Constitutional Order)
-
-1. **Phase -1**: Use `/spec` to create specification with constitutional gates
-2. **Phase 0**: Use `/plan` to generate implementation plan with complexity tracking
-3. **Phase 1**: Use `/task` to break down into executable tasks
-4. **Implementation**: Begin development following constitutional principles
-
-## Integration Features
-
-- **Automatic context tracking** in `memory/context.md`
-- **Enhanced error reporting** with specific failure reasons
-- **Git integration** with branch management
-- **Template validation** before copying
-- **Todo list creation** for progress tracking
-- **Cross-platform script execution** with automatic detection
-- **Multiple language support**: Bash, PowerShell, Python
-- **Platform-agnostic operation** for any development environment

specpulse/resources/commands/gemini/plan.toml

@@ -1,59 +0,0 @@
-description = "Generate or validate implementation plans"
-prompt = """
-Handle the /plan command with arguments: {{args}}
-
-Parse arguments to determine action:
-- If "validate": Check plan against constitution
-- Otherwise: Generate new plan
-
-## For /plan generate or /plan:
-1. Read current specification from @{specs/*/spec.md}
-
-2. Run Phase Gates checks:
-   - Constitutional compliance
-   - Simplicity check (≤3 modules)
-   - Test-first strategy defined
-   - Framework selection complete
-   - Research completed
-
-3. Generate plan sections:
-   - Technology stack
-   - Architecture overview
-   - Implementation phases
-   - API contracts
-   - Data models
-   - Testing strategy
-
-4. Track complexity:
-   - If >3 modules, document justification
-   - Create simplification roadmap
-
-5. Write plan to plans/XXX-feature/plan.md
-6. Run cross-platform validation:
-   - Windows: !{powershell scripts/pulse-plan.ps1 "XXX-feature"}
-   - Linux/macOS: !{bash scripts/pulse-plan.sh "XXX-feature"}
-   - Fallback: !{python scripts/pulse-plan.py "XXX-feature"}
-
-## For /plan validate:
-1. Read existing plan from @{plans/*/plan.md}
-2. Run cross-platform validation:
-   - Windows: !{powershell scripts/pulse-plan.ps1 "XXX-feature"}
-   - Linux/macOS: !{bash scripts/pulse-plan.sh "XXX-feature"}
-   - Fallback: !{python scripts/pulse-plan.py "XXX-feature"}
-3. Verify Phase Gates compliance
-4. Check complexity tracking
-5. Ensure test-first approach
-6. Validate framework choices
-7. Report validation results
-
-Phase Gates (Phase -1) must pass before implementation:
-- ✅ Using ≤3 projects/modules
-- ✅ Tests defined before code
-- ✅ Using framework features directly
-- ✅ No premature abstractions
-- ✅ Research completed
-
-Examples:
-- /plan generate
-- /plan validate
-"""

specpulse/resources/commands/gemini/spec.toml

@@ -1,45 +0,0 @@
-description = "Create or manage feature specifications"
-prompt = """
-Handle the /spec command with arguments: {{args}}
-
-Parse the arguments to determine the action:
-- If starts with "create": Generate new specification
-- If starts with "update": Modify existing specification  
-- If starts with "validate": Check specification completeness
-- If no action specified: Default to "create" with full arguments as description
-
-## For /spec create [description] or /spec [description]:
-1. Read template from @{templates/spec.md}
-2. Parse the description to identify:
-   - Functional requirements (Must/Should/Could have)
-   - User stories and acceptance criteria
-   - Technical requirements
-3. Mark any uncertainties with [NEEDS CLARIFICATION: detail]
-4. Find current feature directory (latest in specs/)
-5. Write specification to specs/XXX-feature/spec.md
-6. Run cross-platform validation:
-   - Windows: !{powershell scripts/pulse-spec.ps1 "XXX-feature"}
-   - Linux/macOS: !{bash scripts/pulse-spec.sh "XXX-feature"}
-   - Fallback: !{python scripts/pulse-spec.py "XXX-feature"}
-
-## For /spec update:
-1. Read existing specification from @{specs/*/spec.md}
-2. Ask user for clarifications or changes
-3. Update content while preserving structure
-4. Remove resolved [NEEDS CLARIFICATION] markers
-
-## For /spec validate:
-1. Run cross-platform validation:
-   - Windows: !{powershell scripts/pulse-spec.ps1 "XXX-feature"}
-   - Linux/macOS: !{bash scripts/pulse-spec.sh "XXX-feature"}
-   - Fallback: !{python scripts/pulse-spec.py "XXX-feature"}
-2. Check all required sections are filled
-3. Count [NEEDS CLARIFICATION] markers
-4. Verify acceptance criteria are testable
-5. Report validation results
-
-Examples:
-- /spec user authentication with OAuth2 and email/password
-- /spec update
-- /spec validate
-"""

specpulse/resources/commands/gemini/task.toml

@@ -1,69 +0,0 @@
-description = "Generate and manage task breakdowns"
-prompt = """
-Handle the /task command with arguments: {{args}}
-
-Parse arguments to determine action:
-- If "update": Update task status
-- If "status": Show progress
-- Otherwise: Generate task breakdown
-
-## For /task breakdown or /task:
-1. Read implementation plan from @{plans/*/plan.md}
-
-2. Generate tasks from plan:
-   - Create task categories:
-     • Critical Path (Phase 0)
-     • Phase 1: Foundation
-     • Phase 2: Core Features
-     • Phase 3: Polish
-     • Phase 4: Testing
-
-   - For each task:
-     • Use T[XXX] format (T001, T002)
-     • Include clear description
-     • Mark dependencies
-     • Estimate complexity (S/M/L/XL)
-     • Assign priority
-
-3. Write tasks to tasks/XXX-feature/tasks.md
-4. Run cross-platform validation:
-   - Windows: !{powershell scripts/pulse-task.ps1 "XXX-feature"}
-   - Linux/macOS: !{bash scripts/pulse-task.sh "XXX-feature"}
-   - Fallback: !{python scripts/pulse-task.py "XXX-feature"}
-
-## For /task update:
-1. Read current tasks from @{tasks/*/tasks.md}
-2. Ask which tasks to update
-3. Mark tasks as completed/in-progress
-4. Add newly discovered tasks
-5. Update dependencies and blockers
-6. Save updated task list
-7. Run cross-platform validation:
-   - Windows: !{powershell scripts/pulse-task.ps1 "XXX-feature"}
-   - Linux/macOS: !{bash scripts/pulse-task.sh "XXX-feature"}
-   - Fallback: !{python scripts/pulse-task.py "XXX-feature"}
-
-## For /task status:
-1. Read current tasks
-2. Run cross-platform analysis:
-   - Windows: !{powershell scripts/pulse-task.ps1 "XXX-feature"}
-   - Linux/macOS: !{bash scripts/pulse-task.sh "XXX-feature"}
-   - Fallback: !{python scripts/pulse-task.py "XXX-feature"}
-3. Count completed vs total
-4. Show current phase progress
-5. List any blockers
-6. Estimate remaining work
-7. Display progress summary
-
-Task Format:
-```markdown
-- [ ] T001: [S] Set up project structure
-- [ ] T002: [M] Create database schema
-- [x] T003: [L] Implement authentication
-```
-
-Examples:
-- /task breakdown
-- /task update
-- /task status
-"""

specpulse/resources/scripts/pulse-init.ps1

@@ -1,186 +0,0 @@
-# SpecPulse Feature Initialization Script
-# Cross-platform PowerShell equivalent of pulse-init.sh
-
-param(
-    [Parameter(Mandatory=$true)]
-    [string]$FeatureName,
-    
-    [string]$CustomId = ""
-)
-
-$ErrorActionPreference = "Stop"
-$ProgressPreference = "SilentlyContinue"
-
-# Configuration
-$ScriptName = $MyInvocation.MyCommand.Name
-$ProjectRoot = $PSScriptRoot | Split-Path -Parent | Split-Path -Parent
-$MemoryDir = Join-Path $ProjectRoot "memory"
-$ContextFile = Join-Path $MemoryDir "context.md"
-$TemplatesDir = Join-Path $ProjectRoot "resources" "templates"
-
-function Write-Log {
-    param([string]$Message)
-    $Timestamp = Get-Date -Format "yyyy-MM-dd HH:mm:ss"
-    Write-Host "[$Timestamp] $ScriptName : $Message" -ForegroundColor Yellow
-}
-
-function Exit-WithError {
-    param([string]$Message)
-    Write-Log "ERROR: $Message"
-    exit 1
-}
-
-function Sanitize-FeatureName {
-    param([string]$Name)
-    
-    if ([string]::IsNullOrWhiteSpace($Name)) {
-        Exit-WithError "Feature name cannot be empty"
-    }
-    
-    # Convert to lowercase, replace spaces and special chars with hyphens
-    $Sanitized = $Name.ToLower() -replace '[^a-z0-9-]', '-'
-    $Sanitized = $Sanitized -replace '-+', '-'  # Remove consecutive hyphens
-    $Sanitized = $Sanitized.Trim('-')  # Remove leading/trailing hyphens
-    
-    if ([string]::IsNullOrWhiteSpace($Sanitized)) {
-        Exit-WithError "Invalid feature name: '$Name'"
-    }
-    
-    return $Sanitized
-}
-
-function Get-FeatureId {
-    param([string]$CustomId)
-    
-    if ($CustomId) {
-        return "{0:D3}" -f [int]$CustomId
-    }
-    
-    # Find existing feature directories
-    $SpecsDir = Join-Path $ProjectRoot "specs"
-    if (Test-Path $SpecsDir) {
-        $Existing = Get-ChildItem -Path $SpecsDir -Directory | 
-                  Where-Object { $_.Name -match '^\d+$' } |
-                  Sort-Object Name
-        $NextId = $Existing.Count + 1
-    } else {
-        $NextId = 1
-    }
-    
-    return "{0:D3}" -f $NextId
-}
-
-function Create-Directories {
-    param([string]$BranchName)
-    
-    $Directories = @(
-        (Join-Path $ProjectRoot "specs" $BranchName),
-        (Join-Path $ProjectRoot "plans" $BranchName),
-        (Join-Path $ProjectRoot "tasks" $BranchName)
-    )
-    
-    foreach ($Directory in $Directories) {
-        try {
-            New-Item -ItemType Directory -Path $Directory -Force | Out-Null
-            Write-Log "Created directory: $Directory"
-        } catch {
-            Exit-WithError "Failed to create directory $Directory : $_"
-        }
-    }
-}
-
-function Copy-Templates {
-    param([string]$BranchName)
-    
-    $Templates = @{
-        "spec.md" = (Join-Path $ProjectRoot "specs" $BranchName "spec.md")
-        "plan.md" = (Join-Path $ProjectRoot "plans" $BranchName "plan.md")
-        "task.md" = (Join-Path $ProjectRoot "tasks" $BranchName "tasks.md")
-    }
-    
-    foreach ($Template in $Templates.GetEnumerator()) {
-        $TemplatePath = Join-Path $TemplatesDir $Template.Key
-        $TargetPath = $Template.Value
-        
-        if (-not (Test-Path $TemplatePath)) {
-            Exit-WithError "Template not found: $TemplatePath"
-        }
-        
-        try {
-            Copy-Item $TemplatePath $TargetPath -Force
-            Write-Log "Copied template to: $TargetPath"
-        } catch {
-            Exit-WithError "Failed to copy template $TemplatePath : $_"
-        }
-    }
-}
-
-function Update-Context {
-    param(
-        [string]$FeatureName,
-        [string]$FeatureId,
-        [string]$BranchName
-    )
-    
-    try {
-        New-Item -ItemType Directory -Path $MemoryDir -Force | Out-Null
-        
-        $ContextEntry = @"
-
-## Active Feature: $FeatureName
-- Feature ID: $FeatureId
-- Branch: $BranchName
-- Started: $(Get-Date -Format "o")
-"@
-        
-        Add-Content -Path $ContextFile -Value $ContextEntry -Encoding UTF8
-        Write-Log "Updated context file: $ContextFile"
-    } catch {
-        Exit-WithError "Failed to update context file: $_"
-    }
-}
-
-function New-GitBranch {
-    param([string]$BranchName)
-    
-    $GitDir = Join-Path $ProjectRoot ".git"
-    if (-not (Test-Path $GitDir)) {
-        return
-    }
-    
-    try {
-        # Check if branch already exists
-        $ExistingBranch = git branch --list $BranchName
-        if ($ExistingBranch) {
-            Write-Log "Git branch '$BranchName' already exists, checking out"
-            git checkout $BranchName
-        } else {
-            Write-Log "Creating new git branch '$BranchName'"
-            git checkout -b $BranchName
-        }
-    } catch {
-        Exit-WithError "Git operation failed: $_"
-    }
-}
-
-# Main execution
-Write-Log "Initializing feature: $FeatureName"
-
-# Sanitize and generate identifiers
-$SanitizedName = Sanitize-FeatureName -Name $FeatureName
-$FeatureId = Get-FeatureId -CustomId $CustomId
-$BranchName = "$FeatureId-$SanitizedName"
-
-# Create structure
-Create-Directories -BranchName $BranchName
-Copy-Templates -BranchName $BranchName
-Update-Context -FeatureName $FeatureName -FeatureId $FeatureId -BranchName $BranchName
-New-GitBranch -BranchName $BranchName
-
-# Output results
-Write-Host "BRANCH_NAME=$BranchName"
-Write-Host "SPEC_DIR=specs/$BranchName"
-Write-Host "FEATURE_ID=$FeatureId"
-Write-Host "STATUS=initialized"
-
-Write-Log "Successfully initialized feature '$FeatureName' with ID $FeatureId"