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

specpulse/resources/commands/claude/sp-pulse.md

@@ -0,0 +1,142 @@
+---
+name: sp-pulse
+description: Initialize a new feature with SpecPulse framework
+allowed_tools:
+  - Bash
+  - Read
+  - Write
+  - Edit
+  - TodoWrite
+---
+
+# /sp-pulse Command
+
+Initialize a new feature following SpecPulse methodology with constitutional compliance.
+
+## Usage
+```
+/sp-pulse <feature-name> [feature-id]
+```
+
+## Implementation
+
+When called with `/sp-pulse $ARGUMENTS`, I will:
+
+1. **Validate arguments** and extract feature name + optional ID
+2. **Run initialization script** with cross-platform detection:
+   - **Linux/macOS**: `bash scripts/sp-pulse-init.sh "$FEATURE_NAME" "$OPTIONAL_ID"`
+   - **Python Fallback**: `python scripts/sp-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. **Suggest specification creation**:
+   - Provide user with 2-3 AI-generated specification suggestions
+   - Ask user to choose one or create custom specification
+   - Guide user to use `/sp-spec` command after making selection
+
+5. **Validate structure** and report comprehensive status
+
+## 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: /sp-pulse user-authentication-oauth2
+```
+
+I will:
+- Run: `bash scripts/sp-pulse-init.sh "user-authentication-oauth2"`
+- Create: `specs/001-user-authentication-oauth2/` (empty, ready for spec)
+- Create: `plans/001-user-authentication-oauth2/` (empty, ready for plan)
+- Create: `tasks/001-user-authentication-oauth2/` (empty, ready for tasks)
+- Branch: `001-user-authentication-oauth2`
+- Suggest specification options:
+  1. "User authentication with OAuth2 providers and JWT tokens"
+  2. "Complete authentication system including registration, login, and profile management"
+  3. "OAuth2 integration with social login providers"
+- Ask: "Which specification would you like to use? (Choose 1-3 or provide your own)"
+- Guide: "After choosing, use `/sp-spec [your choice]` to create the specification"
+- Status: `STATUS=ready_for_spec, 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
+
+## Manual Workflow
+
+The `/sp-pulse` command creates the feature structure and then guides you through manual steps:
+
+1. **Phase -1**: **MANUAL** - Use `/sp-spec` to create specification with AI assistance
+2. **Phase 0**: **MANUAL** - Use `/sp-plan` to generate implementation plan  
+3. **Phase 1**: **MANUAL** - Use `/sp-task` to create task breakdown
+4. **Implementation**: Begin development following constitutional principles
+
+## Context Detection
+
+The system automatically detects which feature you're working on:
+- Checks `memory/context.md` for current feature
+- Uses git branch name if available
+- Falls back to most recently created feature directory
+- You can also specify feature directory explicitly in commands
+
+## 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
+
+## Feature Progress Tracking
+
+The system tracks progress across all features:
+
+### Active Features Overview
+```
+FEATURE_COUNT=3
+ACTIVE_FEATURE=001-user-authentication
+COMPLETED_FEATURES=1
+IN_PROGRESS_FEATURES=2
+```
+
+### Context Management
+- `memory/context.md` tracks current active feature
+- Progress percentages calculated from task completion
+- Feature status: active, completed, paused, blocked
+- Automatic context switching when working on different features
+
+### Multi-Feature Workflow
+```
+/sp-pulse feature-a → /sp-spec → /sp-plan → /sp-task → [work]
+/sp-pulse feature-b → /sp-spec → /sp-plan → /sp-task → [work]
+/sp-status feature-a → Check progress → /sp-continue feature-a
+```
+
+### Feature Switching
+When you have multiple features, the system helps you:
+- List all existing features with their status
+- Switch context between features
+- Continue work from where you left off
+- Track overall project progress across all features

specpulse/resources/commands/claude/{spec.md → sp-spec.md}

@@ -1,5 +1,5 @@
 ---
-name: spec
+name: sp-spec
 description: Create or manage feature specifications using AI-optimized templates
 allowed_tools:
   - Read
@@ -9,29 +9,35 @@ allowed_tools:
   - TodoWrite
 ---
 
-# /spec Command
+# /sp-spec Command
 
 Create, update, or validate feature specifications using SpecPulse methodology with AI-optimized templates.
 
 ## Usage
 ```
-/spec [action] [description|feature-name]
+/sp-spec [action] [description|feature-name]
 ```
 
 Actions: `create`, `update`, `validate`, `clarify` (defaults to `create`)
 
 ## Implementation
 
-When called with `/spec $ARGUMENTS`, I will:
+When called with `/sp-spec $ARGUMENTS`, I will:
 
-1. **Parse arguments** to determine action:
+1. **Detect current feature context**:
+   - Read `memory/context.md` for current feature metadata
+   - Use git branch name if available (e.g., `001-user-authentication`)
+   - Fall back to most recently created feature directory
+   - If no context found, ask user to specify feature or run `/sp-pulse` first
+
+2. **Parse arguments** to determine action:
    - If starts with `create`: Generate new specification
    - If starts with `update`: Modify existing specification
    - If starts with `validate`: Check specification completeness
    - If starts with `clarify`: Address [NEEDS CLARIFICATION] markers
    - If no action specified: Default to `create` with full arguments as description
 
-2. **For `/spec create [description]` or `/spec [description]`:**
+3. **For `/sp-spec create [description]` or `/sp-spec [description]`:**
    - Read AI-optimized template from `templates/spec.md`
    - Parse the description to identify:
      - Functional requirements (Must/Should/Could/Won't have)
@@ -43,32 +49,37 @@ When called with `/spec $ARGUMENTS`, I will:
      # Specification: {{ feature_name }}
      ## Metadata
      - **ID**: SPEC-{{ feature_id }}
+     - **Version**: {{ version }}
      - **Created**: {{ date }}
      ```
    - Mark any uncertainties with `[NEEDS CLARIFICATION: specific question]`
-   - Find current feature directory from context or create new
-   - Write specification to `specs/ID-feature-name/spec.md`
+   - Use detected feature context to determine target directory
+   - **Version management**: Check existing spec files and create next version (spec-001.md, spec-002.md, etc.)
+   - Write specification to `specs/ID-feature-name/spec-XXX.md`
    - Run enhanced validation with cross-platform detection:
-     - **Windows**: `powershell scripts/pulse-spec.ps1 "$FEATURE_DIR"`
-     - **Linux/macOS**: `bash scripts/pulse-spec.sh "$FEATURE_DIR"`
-     - **Python Fallback**: `python scripts/pulse-spec.py "$FEATURE_DIR"`
+     - **Linux/macOS**: `bash scripts/sp-pulse-spec.sh "$FEATURE_DIR"`
+     - **Python Fallback**: `python scripts/sp-pulse-spec.py "$FEATURE_DIR"`
 
-3. **For `/spec update`:**
-   - Read existing specification from current context
+4. **For `/sp-spec update`:**
+   - **Show existing spec files**: List all spec-XXX.md files in current feature directory
+   - **Ask user to select**: Which spec file to update
+   - Read selected specification file
    - Parse update requests and identify sections to modify
    - Update content while preserving AI-friendly template structure
    - Remove resolved `[NEEDS CLARIFICATION]` markers
    - Run validation to ensure completeness
 
-4. **For `/spec validate`:**
-   - Read current specification
+5. **For `/sp-spec validate`:**
+   - **Show existing spec files**: List all spec-XXX.md files in current feature directory
+   - **Ask user to select**: Which spec file to validate
+   - Read selected specification file from detected context
    - Check all required sections using enhanced validation:
      ```bash
      # Cross-platform detection
      if [[ "$OSTYPE" == "msys" || "$OSTYPE" == "win32" ]]; then
-         powershell scripts/pulse-spec.ps1 "$FEATURE_DIR"
+         python scripts/sp-pulse-spec.py "$FEATURE_DIR"
      else
-         bash scripts/pulse-spec.sh "$FEATURE_DIR" || python scripts/pulse-spec.py "$FEATURE_DIR"
+         bash scripts/sp-pulse-spec.sh "$FEATURE_DIR" || python scripts/sp-pulse-spec.py "$FEATURE_DIR"
      fi
      ```
    - Count `[NEEDS CLARIFICATION]` markers
@@ -76,7 +87,9 @@ When called with `/spec $ARGUMENTS`, I will:
    - Check constitutional compliance indicators
    - Report detailed validation results
 
-5. **For `/spec clarify`:**
+6. **For `/sp-spec clarify`:**
+   - **Show existing spec files**: List all spec-XXX.md files in current feature directory
+   - **Ask user to select**: Which spec file to clarify
    - Find all `[NEEDS CLARIFICATION]` markers
    - Address each uncertainty with user input
    - Update specification with resolved information
@@ -87,7 +100,7 @@ When called with `/spec $ARGUMENTS`, I will:
 
 ### Creating a new specification
 ```
-User: /spec create user authentication system with OAuth2 and JWT tokens
+User: /sp-spec create user authentication system with OAuth2 and JWT tokens
 ```
 I will create a comprehensive specification using AI-optimized templates with:
 - Jinja2-style variables for AI processing
@@ -97,13 +110,13 @@ I will create a comprehensive specification using AI-optimized templates with:
 
 ### Updating existing specification
 ```
-User: /spec update add password complexity requirements
+User: /sp-spec update add password complexity requirements
 ```
 I will read the current spec, update password requirements, and validate changes.
 
 ### Validating specification
 ```
-User: /spec validate
+User: /sp-spec validate
 ```
 I will run enhanced validation with detailed reporting:
 ```
@@ -115,7 +128,7 @@ STATUS=validation_complete
 
 ### Addressing clarifications
 ```
-User: /spec clarify
+User: /sp-spec clarify
 ```
 I will systematically address all [NEEDS CLARIFICATION] markers.
 
@@ -152,7 +165,7 @@ The AI-optimized specification template includes:
 ## Integration Features
 
 - **Cross-platform script execution** with automatic detection
-- **Enhanced script integration** with Bash, PowerShell, and Python support
+- **Enhanced script integration** with Bash and Python support
 - **Template variable processing** for AI optimization
 - **Automated validation** with detailed reporting
 - **Context-aware operation** using memory/context.md

specpulse/resources/commands/claude/sp-status.md

@@ -0,0 +1,170 @@
+---
+name: sp-status
+description: Track progress across all features and specific feature details
+allowed_tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - TodoWrite
+---
+
+# /sp-status Command
+
+Track progress across all features or get detailed status of a specific feature.
+
+## Usage
+```
+/sp-status [feature-name]
+```
+
+## Implementation
+
+When called with `/sp-status $ARGUMENTS`, I will:
+
+1. **Parse arguments** to determine scope:
+   - If feature name provided: Show detailed status for that feature
+   - Otherwise: Show overview of all features
+
+2. **Read feature context** from `memory/context.md`
+
+3. **For `/sp-status` (all features overview):**
+   - Scan all feature directories (specs/*, plans/*, tasks/*)
+   - Count features by status: active, completed, in_progress, paused
+   - Calculate overall project progress
+   - Show summary statistics:
+     ```
+     TOTAL_FEATURES=5
+     ACTIVE_FEATURES=2
+     COMPLETED_FEATURES=1
+     IN_PROGRESS_FEATURES=1
+     PAUSED_FEATURES=1
+     OVERALL_PROGRESS=42%
+     ```
+   - List all features with their status and progress percentage
+   - Highlight current active feature from context
+
+4. **For `/sp-status [feature-name]` (detailed feature status):**
+   - Detect feature directory (using context detection logic)
+   - Read all task files in the feature's tasks directory
+   - Calculate completion percentage based on task status
+   - Show detailed breakdown:
+     ```
+     FEATURE: 001-user-authentication
+     STATUS: active
+     PROGRESS: 65%
+     SPECS: 2 files
+     PLANS: 1 file  
+     TASKS: 1 file (25 total tasks)
+     COMPLETED_TASKS: 16
+     IN_PROGRESS_TASKS: 5
+     BLOCKED_TASKS: 1
+     LAST_UPDATED: 2025-01-09
+     ```
+   - Show phase-by-phase progress
+   - List any blockers or issues
+   - Provide recommendations for next steps
+
+5. **Progress calculation logic:**
+   - Scan task files for completion status: `[x]` for completed, `[ ]` for pending, `[-]` for in progress, `[!]` for blocked
+   - Calculate percentages: completed / total * 100
+   - Track trends over time if historical data available
+
+## Feature Status Indicators
+
+- **Active**: Currently being worked on (in context.md)
+- **Completed**: All tasks marked as complete
+- **In Progress**: Has task files with some completed tasks
+- **Paused**: No recent activity, not all tasks complete
+- **Blocked**: Has blocked tasks preventing progress
+
+## Examples
+
+### All features overview
+```
+User: /sp-status
+```
+
+I will display:
+```
+## Feature Status Overview
+
+**Total Features**: 5
+**Overall Progress**: 42%
+
+### Active Features
+- [🔄] 001-user-authentication (65%)
+- [🔄] 002-payment-processing (23%)
+
+### Completed Features  
+- [✅] 000-project-setup (100%)
+
+### In Progress Features
+- [⏳] 003-user-profile (45%)
+
+### Paused Features
+- [⏸️] 004-notifications (78%)
+
+### Current Context
+**Active Feature**: 001-user-authentication
+**Last Updated**: 2025-01-09
+```
+
+### Specific feature status
+```
+User: /sp-status user-authentication
+```
+
+I will display:
+```
+## Feature Status: 001-user-authentication
+
+**Overall Progress**: 65%
+**Status**: Active
+**Created**: 2025-01-09
+**Last Updated**: 2025-01-09
+
+### Files
+- **Specifications**: spec-001.md, spec-002.md (2 files)
+- **Plans**: plan-001.md (1 file)
+- **Tasks**: task-001.md (1 file, 25 total tasks)
+
+### Task Progress
+- **Completed**: 16 tasks (64%)
+- **In Progress**: 5 tasks (20%)
+- **Blocked**: 1 task (4%)
+- **Pending**: 3 tasks (12%)
+
+### Phase Progress
+- **Phase 0 (Critical Path)**: 80% complete
+- **Phase 1 (Foundation)**: 70% complete
+- **Phase 2 (Core Features)**: 50% complete
+- **Phase 3 (Polish)**: 20% complete
+- **Phase 4 (Testing)**: 0% complete
+
+### Blockers
+- T015: Database schema approval pending
+
+### Recommendations
+1. Resolve database schema blocker (T015)
+2. Continue with Phase 2 core features
+3. Consider starting Phase 4 testing in parallel
+```
+
+## Integration Features
+
+- **Multi-feature tracking** across entire project
+- **Progress percentage calculation** from task completion
+- **Status categorization** with visual indicators
+- **Blocker identification** and resolution tracking
+- **Context-aware operation** using memory/context.md
+- **Cross-platform compatibility** with proper path handling
+- **Historical trend tracking** for progress over time
+
+## Error Handling
+
+- Feature directory validation
+- Task file parsing with error recovery
+- Progress calculation validation
+- Context file fallback handling
+- Permission and access error handling