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

specpulse/resources/commands/claude/plan.md

@@ -1,184 +0,0 @@
----
-name: plan
-description: Generate or validate implementation plans using AI-optimized templates
-allowed_tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - TodoWrite
----
-
-# /plan Command
-
-Generate implementation plans from specifications following SpecPulse methodology with constitutional compliance and AI-optimized templates.
-
-## Usage
-```
-/plan [action] [feature-directory]
-```
-
-Actions: `generate`, `validate`, `optimize` (defaults to `generate`)
-
-## Implementation
-
-When called with `/plan $ARGUMENTS`, I will:
-
-1. **Parse arguments** and determine action:
-   - If `validate`: Check plan against constitutional gates
-   - If `optimize`: Improve existing plan complexity
-   - Otherwise: Generate new plan
-
-2. **For `/plan generate` or `/plan`:**
-   a. **Find and validate specification** from current context or provided directory
-   
-   b. **Enhanced validation** using cross-platform script:
-      ```bash
-      # Cross-platform detection
-      if [[ "$OSTYPE" == "msys" || "$OSTYPE" == "win32" ]]; then
-          powershell scripts/pulse-plan.ps1 "$FEATURE_DIR"
-      else
-          bash scripts/pulse-plan.sh "$FEATURE_DIR" || python scripts/pulse-plan.py "$FEATURE_DIR"
-      fi
-      ```
-
-   c. **Run Constitutional Phase Gates** (Article VII):
-      - Simplicity Gate: ≤3 modules justification
-      - Anti-Abstraction Gate: Direct framework usage
-      - Test-First Gate: Tests before implementation
-      - Integration-First Gate: Real services over mocks
-      - Research Gate: Technology choices documented
-
-   d. **Generate AI-optimized plan** using template variables:
-      ```markdown
-      # Implementation Plan: {{ feature_name }}
-      ## Specification Reference
-      - **Spec ID**: SPEC-{{ feature_id }}
-      - **Generated**: {{ date }}
-      ```
-
-   e. **Generate comprehensive sections**:
-      - Technology stack with performance implications
-      - Architecture overview with component relationships
-      - Implementation phases with timeline estimates
-      - API contracts with authentication requirements
-      - Data models with validation rules
-      - Testing strategy with coverage targets
-      - Security considerations with compliance requirements
-      - Deployment strategy with rollback plans
-
-   f. **Complexity tracking** (Article VII):
-      - Document all complexity exceptions with justifications
-      - Create mitigation strategies for each exception
-      - Track optimization opportunities
-
-   g. **Write optimized plan** to `plans/XXX-feature/plan.md`
-
-3. **For `/plan validate`:**
-   - **Enhanced validation** using cross-platform script:
-     ```bash
-     # Cross-platform detection
-     if [[ "$OSTYPE" == "msys" || "$OSTYPE" == "win32" ]]; then
-         powershell scripts/pulse-plan.ps1 "$FEATURE_DIR"
-     else
-         bash scripts/pulse-plan.sh "$FEATURE_DIR" || python scripts/pulse-plan.py "$FEATURE_DIR"
-     fi
-     ```
-   - Verify all constitutional gates are addressed
-   - Check complexity exceptions have proper justifications
-   - Validate test-first approach is documented
-   - Ensure integration strategy uses real services
-   - Report detailed validation results
-
-4. **For `/plan optimize`:**
-   - **Read existing plan** and analyze complexity
-   - **Identify optimization opportunities**:
-     - Module consolidation opportunities
-     - Abstraction layer removal candidates
-     - Simplification strategies
-   - **Generate optimization recommendations**
-   - **Update plan** with reduced complexity
-
-## Constitutional Phase Gates (Phase -1)
-
-**Must pass before implementation:**
-
-### Article VII: Simplicity Gate
-- [ ] Using ≤3 projects/modules for initial implementation
-- [ ] No future-proofing without documented need
-- [ ] Direct framework usage (no unnecessary wrappers)
-- [ ] Single model representation per concept
-
-### Article VII: Anti-Abstraction Gate  
-- [ ] Using framework features directly
-- [ ] No unnecessary abstraction layers
-- [ ] Clear, simple interfaces
-- [ ] Avoiding premature optimization
-
-### Article III: Test-First Gate
-- [ ] Test specifications written
-- [ ] Tests reviewed and approved
-- [ ] Tests confirmed to FAIL before implementation
-- [ ] TDD cycle planned (Red-Green-Refactor)
-
-### Article VIII: Integration-First Gate
-- [ ] Contract tests defined
-- [ ] Using real services over mocks
-- [ ] Production-like test environment planned
-- [ ] End-to-end test scenarios identified
-
-### Article VI: Research Gate
-- [ ] Library options researched
-- [ ] Performance implications documented
-- [ ] Security considerations analyzed
-- [ ] Trade-offs documented
-
-## Examples
-
-### Generate plan with validation
-```
-User: /plan generate
-```
-I will:
-- Run: `bash scripts/pulse-plan.sh "$FEATURE_DIR"`
-- Validate: Constitutional gates compliance
-- Create: AI-optimized plan with template variables
-- Output: `CONSTITUTIONAL_GATES_STATUS=PENDING`
-
-### Validate existing plan
-```
-User: /plan validate
-```
-I will run comprehensive validation:
-```
-PLAN_FILE=plans/001-user-authentication/plan.md
-CONSTITUTIONAL_GATES_STATUS=COMPLETED
-MISSING_SECTIONS=0
-STATUS=validation_complete
-```
-
-### Optimize plan complexity
-```
-User: /plan optimize
-```
-I will analyze and recommend complexity reductions.
-
-## Enhanced Features
-
-- **AI-optimized templates** with Jinja2-style variables
-- **Cross-platform script execution** with automatic detection
-- **Enhanced script integration** for Bash, PowerShell, and Python
-- **Constitutional compliance tracking** with gate status
-- **Complexity exception management** with justifications
-- **Performance and security considerations** integrated
-- **Integration-first approach** with real service usage
-- **Detailed validation reporting** with specific recommendations
-- **Platform-agnostic operation** for any development environment
-
-## Error Handling
-
-- Specification existence validation
-- Constitutional gate compliance checking
-- Template structure validation
-- Directory structure verification
-- Feature context auto-discovery

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/claude/task.md

@@ -1,237 +0,0 @@
----
-name: task
-description: Generate and manage task breakdowns using AI-optimized templates
-allowed_tools:
-  - Read
-  - Write  
-  - Edit
-  - Bash
-  - TodoWrite
----
-
-# /task Command
-
-Generate task breakdowns from implementation plans using SpecPulse methodology with AI-optimized templates and enhanced validation.
-
-## Usage
-```
-/task [action] [feature-directory]
-```
-
-Actions: `breakdown`, `update`, `status`, `execute` (defaults to `breakdown`)
-
-## Implementation
-
-When called with `/task $ARGUMENTS`, I will:
-
-1. **Parse arguments** to determine action:
-   - If `update`: Update task status and dependencies
-   - If `status`: Show comprehensive progress with metrics
-   - If `execute`: Execute task with script integration
-   - Otherwise: Generate task breakdown
-
-2. **For `/task breakdown` or `/task`:**
-   
-   a. **Enhanced validation** using cross-platform script:
-      ```bash
-      # Cross-platform detection
-      if [[ "$OSTYPE" == "msys" || "$OSTYPE" == "win32" ]]; then
-          powershell scripts/pulse-task.ps1 "$FEATURE_DIR"
-      else
-          bash scripts/pulse-task.sh "$FEATURE_DIR" || python scripts/pulse-task.py "$FEATURE_DIR"
-      fi
-      ```
-   
-   b. **Read implementation plan** from `plans/XXX-feature/plan.md`
-   
-   c. **Generate AI-optimized tasks** using template variables:
-      ```markdown
-      # Task List: {{ feature_name }}
-      ## Metadata
-      - **Total Tasks**: {{ task_count }}
-      - **Estimated Duration**: {{ total_duration }}
-      ```
-
-   d. **Generate structured task categories**:
-      - **Constitutional Gates Compliance**: Pre-implementation validation
-      - **Critical Path (Phase 0)**: Tasks that impact timeline
-      - **Parallel Groups**: Tasks that can execute simultaneously
-      - **Sequential Tasks**: Tasks with dependencies
-      - **Execution Schedule**: Time-based task organization
-      - **Progress Tracking**: YAML configuration for monitoring
-
-   e. **For each task**, generate comprehensive metadata:
-      - **ID**: T[XXX] format (T001, T002)
-      - **Type**: setup, development, testing, documentation
-      - **Priority**: HIGH, MEDIUM, LOW
-      - **Estimate**: Hours or complexity points
-      - **Dependencies**: Task ID dependencies
-      - **Description**: Clear what needs to be done
-      - **Acceptance**: How to verify completion
-      - **Files**: Files to be created/modified
-      - **Assignable**: Role/skill required
-      - **Parallel**: Whether can run in parallel [P]
-
-   f. **Generate execution commands** with script integration:
-      ```bash
-      # Execute parallel tasks
-      parallel_tasks="T001 T002 T003"
-      for task in $parallel_tasks; do
-          ./scripts/execute-task.sh "$task" &
-      done
-      wait
-      ```
-
-   g. **Write comprehensive task breakdown** to `tasks/XXX-feature/tasks.md`
-
-3. **For `/task update`:**
-   - **Enhanced analysis** using cross-platform script:
-     ```bash
-     # Cross-platform detection
-     if [[ "$OSTYPE" == "msys" || "$OSTYPE" == "win32" ]]; then
-         powershell scripts/pulse-task.ps1 "$FEATURE_DIR"
-     else
-         bash scripts/pulse-task.sh "$FEATURE_DIR" || python scripts/pulse-task.py "$FEATURE_DIR"
-     fi
-     ```
-   - **Parse current tasks** with comprehensive status:
-     - Total tasks, completed, pending, blocked
-     - Parallel tasks identification
-     - Constitutional gates status
-     - Completion percentage calculation
-   - **Interactive task updates**:
-     - Mark tasks as completed/in-progress/blocked
-     - Update dependencies and blockers
-     - Add newly discovered tasks with proper metadata
-     - Adjust estimates based on actual progress
-   - **Generate updated progress tracking** YAML
-
-4. **For `/task status`:**
-   - **Enhanced reporting** from script output:
-     ```bash
-     TOTAL_TASKS=25
-     COMPLETED_TASKS=10
-     COMPLETION_PERCENTAGE=40%
-     CONSTITUTIONAL_GATES_PENDING=2
-     ```
-   - **Display comprehensive progress**:
-     - Overall completion percentage
-     - Phase-by-phase progress
-     - Blocker identification and resolution
-     - Velocity metrics and estimates
-     - Constitutional gates compliance status
-
-5. **For `/task execute`:**
-   - **Validate task readiness** using constitutional gates
-   - **Execute task** with enhanced error handling:
-     ```bash
-     ./scripts/execute-task.sh "$TASK_ID"
-     ```
-   - **Track execution results** and update status
-   - **Update progress tracking** automatically
-
-## Enhanced Task Format
-```markdown
-### Parallel Group A
-#### T001: Initialize project structure
-- **Type**: setup
-- **Priority**: HIGH
-- **Estimate**: 2 hours
-- **Dependencies**: None
-- **Description**: Set up project directory structure and configuration
-- **Acceptance**: All directories exist and config files are valid
-- **Files**: package.json, README.md, .gitignore
-- **Assignable**: developer
-- **Parallel**: [P]
-
-## Progress Tracking
-```yaml
-status:
-  total: 25
-  completed: 10
-  in_progress: 3
-  blocked: 0
-  
-metrics:
-  velocity: 2-3 tasks/day
-  estimated_completion: 2025-09-15
-  completion_percentage: 40%
-```
-
-## Constitutional Gates Integration
-
-Each task breakdown includes constitutional compliance validation:
-- **Simplicity Gate**: Tasks avoid unnecessary complexity
-- **Test-First Gate**: Test tasks before implementation tasks
-- **Integration-First Gate**: Real service integration preferred
-- **Research Gate**: Technology research tasks included
-
-## Examples
-
-### Generate task breakdown
-```
-User: /task breakdown
-```
-I will:
-- Run: Cross-platform detection and execution
-  ```bash
-  # Cross-platform detection
-  if [[ "$OSTYPE" == "msys" || "$OSTYPE" == "win32" ]]; then
-      powershell scripts/pulse-task.ps1 "$FEATURE_DIR"
-  else
-      bash scripts/pulse-task.sh "$FEATURE_DIR" || python scripts/pulse-task.py "$FEATURE_DIR"
-  fi
-  ```
-- Create: AI-optimized task structure with template variables
-- Output: `TOTAL_TASKS=25, PARALLEL_TASKS=8, STATUS=generated`
-
-### Update task status
-```
-User: /task update mark T001-T005 as completed
-```
-I will update task status and recalculate progress metrics.
-
-### Show comprehensive status
-```
-User: /task status
-```
-I will display detailed progress with constitutional gates compliance.
-
-### Execute specific task
-```
-User: /task execute T001
-```
-I will:
-- Validate: Constitutional gates compliance and task readiness
-- Execute: Cross-platform task execution
-  ```bash
-  # Cross-platform task execution
-  if [[ "$OSTYPE" == "msys" || "$OSTYPE" == "win32" ]]; then
-      powershell scripts/pulse-task.ps1 "$FEATURE_DIR" "execute:$TASK_ID"
-  else
-      bash scripts/pulse-task.sh "$FEATURE_DIR" "execute:$TASK_ID" || python scripts/pulse-task.py "$FEATURE_DIR" "execute:$TASK_ID"
-  fi
-  ```
-- Track: Results and update progress automatically
-
-## Enhanced Features
-
-- **Cross-platform script execution** with automatic detection (PowerShell/Bash/Python)
-- **AI-optimized templates** with Jinja2-style variables
-- **Enhanced script integration** for validation and execution
-- **Constitutional gates compliance** tracking
-- **Parallel task identification** and execution
-- **Comprehensive progress tracking** with YAML configuration
-- **Automatic percentage calculation** and velocity metrics
-- **Task dependency management** with conflict detection
-- **Execution command generation** with script integration
-- **Platform-agnostic operation** for Windows, Linux, and macOS
-
-## Error Handling
-
-- Plan existence validation before task generation
-- Constitutional gates compliance checking
-- Template structure validation
-- Dependency conflict detection
-- Task execution error handling with rollback
-- Progress tracking validation and correction

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
-"""