specpulse 1.0.3__py3-none-any.whl → 1.0.4__py3-none-any.whl

specpulse/__init__.py

@@ -3,7 +3,7 @@ SpecPulse: Specification-Driven Development Framework
 Built for the AI era
 """
 
-__version__ = "1.0.3"
+__version__ = "1.0.4"
 __author__ = "SpecPulse"
 __url__ = "https://github.com/specpulse"
 

specpulse/resources/commands/claude/plan.md

@@ -1,25 +1,43 @@
-# /plan
+---
+name: plan
+description: Generate or validate implementation plans
+allowed_tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+---
 
-Generate implementation plans using SpecPulse methodology.
+# /plan Command
+
+Generate implementation plans from specifications following SpecPulse methodology.
 
 ## Usage
 ```
-/plan generate
-/plan validate
+/plan [action]
 ```
 
-## Commands
+Actions: `generate`, `validate` (defaults to `generate`)
+
+## Implementation
+
+When called with `/plan $ARGUMENTS`, I will:
+
+1. **Parse arguments** to determine action:
+   - If `$ARGUMENTS` is `validate`: Check plan against constitution
+   - Otherwise: Generate new plan
 
-### generate
-Create implementation plan from specification:
-1. Run Phase Gates checks:
+2. **For `/plan generate` or `/plan`:**
+   a. **Read current specification** from `specs/XXX-feature/spec.md`
+   
+   b. **Run Phase Gates checks**:
    - Constitutional compliance
    - Simplicity check (≤3 modules)
    - Test-first strategy defined
    - Framework selection complete
    - Research completed
 
-2. Generate plan sections:
+   c. **Generate plan sections**:
    - Technology stack
    - Architecture overview
    - Implementation phases
@@ -27,18 +45,19 @@ Create implementation plan from specification:
    - Data models
    - Testing strategy
 
-3. Track complexity:
+   d. **Track complexity**:
    - If >3 modules, document justification
    - Create simplification roadmap
 
-4. Write to plans/[feature]/plan.md
+   e. **Write plan** to `plans/XXX-feature/plan.md`
 
-### validate
-Check plan against constitution:
-1. Verify Phase Gates passed
-2. Check complexity tracking
-3. Ensure test-first approach
-4. Validate framework choices
+3. **For `/plan validate`:**
+   - Read existing plan from `plans/XXX-feature/plan.md`
+   - Verify Phase Gates compliance
+   - Check complexity tracking
+   - Ensure test-first approach
+   - Validate framework choices
+   - Report validation results
 
 ## Phase Gates (Phase -1)
 Must pass before implementation:

specpulse/resources/commands/claude/pulse.md

@@ -1,36 +1,52 @@
-# /pulse
+---
+name: pulse
+description: Initialize a new feature with SpecPulse framework
+allowed_tools:
+  - Bash
+  - Read
+  - Write
+  - Edit
+---
 
-Initialize a new feature with SpecPulse framework.
+# /pulse Command
+
+Initialize a new feature following SpecPulse methodology.
 
 ## Usage
 ```
-/pulse init <feature-name>
+/pulse <feature-name>
 ```
 
-## What This Does
-1. Runs `scripts/pulse-init.sh <feature-name>` to:
-   - Create feature ID (001, 002, etc.)
-   - Create branch name (001-feature-name)
-   - Create directories: specs/, plans/, tasks/
+## Implementation
+
+When called with `/pulse $ARGUMENTS`, I will:
+
+1. **Extract feature name** from `$ARGUMENTS`
+2. **Run initialization script**: `bash scripts/pulse-init.sh "$ARGUMENTS"`
+3. **Create feature structure**:
+   - Generate feature ID (001, 002, etc.)
+   - Create directories: `specs/XXX-feature/`, `plans/XXX-feature/`, `tasks/XXX-feature/`
    - Copy templates to feature directories
-   - Update memory/context.md
-   - Create git branch if in git repo
+   - Update `memory/context.md` with current feature
+   - Create git branch if in git repository
 
-2. Reports the created structure back to user
+4. **Report results** to user with created structure
 
 ## Example
 ```
-/pulse init user-authentication
+User: /pulse user-authentication
 ```
 
-Creates:
-- Branch: 001-user-authentication
-- specs/001-user-authentication/spec.md
-- plans/001-user-authentication/plan.md
-- tasks/001-user-authentication/tasks.md
+I will:
+- Run: `bash scripts/pulse-init.sh "user-authentication"`
+- Create: `specs/001-user-authentication/spec.md`
+- Create: `plans/001-user-authentication/plan.md`  
+- Create: `tasks/001-user-authentication/tasks.md`
+- Switch to branch: `001-user-authentication` (if git)
+- Report success and next steps
 
 ## Next Steps
-After initialization, use:
-- `/spec create` to write the specification
-- `/plan generate` to create implementation plan
-- `/task breakdown` to generate tasks
+After initialization:
+- Use `/spec` to create the specification
+- Use `/plan` to generate implementation plan
+- Use `/task` to break down into tasks

specpulse/resources/commands/claude/spec.md

@@ -1,47 +1,81 @@
-# /spec
+---
+name: spec
+description: Create or manage feature specifications
+allowed_tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+---
 
-Create or update feature specifications using SpecPulse.
+# /spec Command
+
+Create, update, or validate feature specifications using SpecPulse methodology.
 
 ## Usage
 ```
-/spec create <description>
-/spec update
-/spec validate
+/spec [action] [description]
 ```
 
-## Commands
+Actions: `create`, `update`, `validate` (defaults to `create`)
+
+## Implementation
+
+When called with `/spec $ARGUMENTS`, I will:
+
+1. **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 no action specified: Default to `create` with full arguments as description
+
+2. **For `/spec create [description]` or `/spec [description]`:**
+   - Read template from `templates/spec.md`
+   - Parse the description to identify:
+     - Functional requirements (Must/Should/Could have)
+     - User stories and acceptance criteria
+     - Technical requirements
+   - Mark any uncertainties with `[NEEDS CLARIFICATION: detail]`
+   - Find current feature directory (latest in specs/)
+   - Write specification to `specs/XXX-feature/spec.md`
+
+3. **For `/spec update`:**
+   - Read existing specification
+   - Ask user for clarifications or changes
+   - Update content while preserving structure
+   - Remove resolved `[NEEDS CLARIFICATION]` markers
+
+4. **For `/spec validate`:**
+   - Check all required sections are filled
+   - Count `[NEEDS CLARIFICATION]` markers
+   - Verify acceptance criteria are testable
+   - Report validation results
+
+## Examples
 
-### create
-Generate a specification from user requirements:
-1. Parse the user's description
-2. Identify functional requirements
-3. Create user stories
-4. Mark uncertainties with [NEEDS CLARIFICATION]
-5. Write to specs/[feature]/spec.md
+### Creating a new specification
+```
+User: /spec user authentication with OAuth2 and email/password
+```
+I will create a comprehensive specification with all requirements.
 
-### update
-Update existing specification:
-1. Read current spec.md
-2. Apply changes based on clarifications
-3. Remove resolved [NEEDS CLARIFICATION] markers
-4. Update acceptance criteria
+### Updating existing specification
+```
+User: /spec update
+```
+I will read the current spec and guide through updates.
 
-### validate
-Check specification completeness:
-1. Ensure all sections are filled
-2. Check for remaining [NEEDS CLARIFICATION] markers
-3. Verify acceptance criteria are testable
-4. Confirm technical specs are defined
+### Validating specification
+```
+User: /spec validate
+```
+I will check completeness and report any issues.
 
 ## Template Structure
+The specification follows this structure:
 - Project Overview
-- Functional Requirements (Must/Should/Could)
-- User Stories with Acceptance Criteria
+- Functional Requirements (Must/Should/Could have)
+- User Stories with Acceptance Criteria  
 - Technical Specifications
 - Clarifications Needed
-- Validation Checklist
-
-## Example
-```
-/spec create "Build a user authentication system with email/password and OAuth2"
-```
+- Validation Checklist

specpulse/resources/commands/claude/task.md

@@ -1,47 +1,69 @@
-# /task
+---
+name: task
+description: Generate and manage task breakdowns
+allowed_tools:
+  - Read
+  - Write  
+  - Edit
+  - Bash
+---
 
-Generate task breakdowns using SpecPulse structure.
+# /task Command
+
+Generate task breakdowns from implementation plans using SpecPulse structure.
 
 ## Usage
 ```
-/task breakdown
-/task update
-/task status
+/task [action]
 ```
 
-## Commands
+Actions: `breakdown`, `update`, `status` (defaults to `breakdown`)
+
+## Implementation
+
+When called with `/task $ARGUMENTS`, I will:
 
-### breakdown
-Generate tasks from plan:
-1. Create task categories:
+1. **Parse arguments** to determine action:
+   - If `$ARGUMENTS` is `update`: Update task status
+   - If `$ARGUMENTS` is `status`: Show progress
+   - Otherwise: Generate task breakdown
+
+2. **For `/task breakdown` or `/task`:**
+   
+   a. **Read implementation plan** from `plans/XXX-feature/plan.md`
+   
+   b. **Generate tasks from plan**:
+      - Create task categories:
    - Critical Path (Phase 0)
    - Phase 1: Foundation
    - Phase 2: Core Features
    - Phase 3: Polish
    - Phase 4: Testing
 
-2. For each task:
+      - For each task:
    - Use T[XXX] format (T001, T002)
    - Include clear description
    - Mark dependencies
    - Estimate complexity (S/M/L/XL)
    - Assign priority
 
-3. Write to tasks/[feature]/tasks.md
-
-### update
-Update task status:
-1. Mark tasks as completed
-2. Add new discovered tasks
-3. Update dependencies
-4. Track blockers
-
-### status
-Show task progress:
-1. Count completed vs total
-2. Show current phase
-3. List blockers
-4. Estimate remaining work
+   c. **Write tasks** to `tasks/XXX-feature/tasks.md`
+
+3. **For `/task update`:**
+   - Read current tasks from `tasks/XXX-feature/tasks.md`
+   - Ask which tasks to update
+   - Mark tasks as completed/in-progress
+   - Add newly discovered tasks
+   - Update dependencies and blockers
+   - Save updated task list
+
+4. **For `/task status`:**
+   - Read current tasks
+   - Count completed vs total
+   - Show current phase progress
+   - List any blockers
+   - Estimate remaining work
+   - Display progress summary
 
 ## Task Format
 ```markdown

specpulse/resources/commands/gemini/plan.toml

@@ -1,48 +1,51 @@
-[command]
-name = "plan"
-description = "Generate implementation plans"
-
-[command.subcommands.generate]
-description = "Create plan from specification"
-usage = "/plan generate"
-
-[[command.subcommands.generate.phase_gates]]
-name = "Constitutional Compliance"
-checks = [
-    "simplicity_check",
-    "test_first_check",
-    "framework_usage_check"
-]
-
-[[command.subcommands.generate.phase_gates]]
-name = "Complexity Check"
-max_modules = 3
-requires_justification = true
-
-[[command.subcommands.generate.actions]]
-step = "read_spec"
-file = "specs/{{feature}}/spec.md"
-
-[[command.subcommands.generate.actions]]
-step = "generate_plan"
-template = "templates/plan.md"
-sections = [
-    "technology_stack",
-    "architecture",
-    "phases",
-    "api_contracts",
-    "data_models",
-    "test_strategy"
-]
-
-[[command.subcommands.generate.actions]]
-step = "write_file"
-path = "plans/{{feature}}/plan.md"
-
-[command.subcommands.validate]
-description = "Validate plan against constitution"
-checks = [
-    "phase_gates_passed",
-    "complexity_tracked",
-    "test_first_defined"
-]
+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
+
+## For /plan validate:
+1. Read existing plan from @{plans/*/plan.md}
+2. Verify Phase Gates compliance
+3. Check complexity tracking
+4. Ensure test-first approach
+5. Validate framework choices
+6. 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/pulse.toml

@@ -1,45 +1,24 @@
-[command]
-name = "pulse"
-description = "Initialize SpecPulse features"
+description = "Initialize a new feature with SpecPulse framework"
+prompt = """
+Initialize a new SpecPulse feature with the name: {{args}}
 
-[command.subcommands.init]
-description = "Initialize a new feature with proper structure"
-usage = "/pulse init <feature-name>"
+Please follow these steps:
 
-[[command.subcommands.init.steps]]
-action = "run_script"
-script = "scripts/pulse-init.sh"
-args = ["{{feature_name}}"]
+1. Extract the feature name from the provided arguments
+2. Run the initialization script: !{bash scripts/pulse-init.sh "{{args}}"}
+3. Create the feature structure:
+   - Generate feature ID (001, 002, etc.)
+   - Create directories: specs/XXX-feature/, plans/XXX-feature/, tasks/XXX-feature/
+   - Copy templates to feature directories
+   - Update memory/context.md with current feature
+   - Create git branch if in git repository
 
-[[command.subcommands.init.steps]]
-action = "create_files"
-files = [
-    "specs/{{branch_name}}/spec.md",
-    "plans/{{branch_name}}/plan.md",
-    "tasks/{{branch_name}}/tasks.md"
-]
+4. Report the results showing:
+   - Created structure paths
+   - Feature ID and branch name
+   - Next steps for the user
 
-[[command.subcommands.init.steps]]
-action = "update_context"
-file = "memory/context.md"
-content = """
-## Active Feature: {{feature_name}}
-- Feature ID: {{feature_id}}
-- Branch: {{branch_name}}
-- Started: {{timestamp}}
-"""
+If no feature name is provided, ask the user for the feature name first.
 
-[[command.subcommands.init.steps]]
-action = "git_branch"
-branch = "{{branch_name}}"
-
-[command.response]
-template = """
-✅ Feature initialized: {{feature_name}}
-- Branch: {{branch_name}}
-- Spec: specs/{{branch_name}}/spec.md
-- Plan: plans/{{branch_name}}/plan.md
-- Tasks: tasks/{{branch_name}}/tasks.md
-
-Next: Use /spec create to define requirements
+Example usage: /pulse user-authentication
 """

specpulse/resources/commands/gemini/spec.toml

@@ -1,33 +1,37 @@
-[command]
-name = "spec"
-description = "Manage feature specifications"
+description = "Create or manage feature specifications"
+prompt = """
+Handle the /spec command with arguments: {{args}}
 
-[command.subcommands.create]
-description = "Create specification from requirements"
-usage = "/spec create <description>"
+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
 
-[[command.subcommands.create.actions]]
-step = "analyze_requirements"
-input = "{{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
 
-[[command.subcommands.create.actions]]
-step = "generate_spec"
-template = "templates/spec.md"
-markers = ["[NEEDS CLARIFICATION]"]
+## 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
 
-[[command.subcommands.create.actions]]
-step = "write_file"
-path = "specs/{{feature}}/spec.md"
+## For /spec validate:
+1. Check all required sections are filled
+2. Count [NEEDS CLARIFICATION] markers
+3. Verify acceptance criteria are testable
+4. Report validation results
 
-[command.subcommands.validate]
-description = "Validate specification completeness"
-checks = [
-    "all_sections_filled",
-    "no_clarification_markers",
-    "testable_criteria",
-    "technical_specs_defined"
-]
-
-[command.subcommands.update]
-description = "Update existing specification"
-usage = "/spec update"
+Examples:
+- /spec user authentication with OAuth2 and email/password
+- /spec update
+- /spec validate
+"""

specpulse/resources/commands/gemini/task.toml

@@ -1,51 +1,57 @@
-[command]
-name = "task"
-description = "Manage task breakdowns"
-
-[command.subcommands.breakdown]
-description = "Generate tasks from plan"
-usage = "/task breakdown"
-
-[[command.subcommands.breakdown.categories]]
-name = "Critical Path"
-phase = 0
-prefix = "T0"
-
-[[command.subcommands.breakdown.categories]]
-name = "Foundation"
-phase = 1
-prefix = "T1"
-
-[[command.subcommands.breakdown.categories]]
-name = "Core Features"
-phase = 2
-prefix = "T2"
-
-[[command.subcommands.breakdown.categories]]
-name = "Polish"
-phase = 3
-prefix = "T3"
-
-[[command.subcommands.breakdown.categories]]
-name = "Testing"
-phase = 4
-prefix = "T4"
-
-[command.subcommands.breakdown.format]
-pattern = "T{id:03d}"
-complexity = ["S", "M", "L", "XL"]
-template = "- [ ] {id}: [{complexity}] {description}"
-
-[command.subcommands.update]
-description = "Update task status"
-actions = ["complete", "add", "block", "unblock"]
-
-[command.subcommands.status]
-description = "Show task progress"
-shows = [
-    "completed_count",
-    "total_count",
-    "current_phase",
-    "blockers",
-    "estimate"
-]
+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
+
+## 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
+
+## For /task status:
+1. Read current tasks
+2. Count completed vs total
+3. Show current phase progress
+4. List any blockers
+5. Estimate remaining work
+6. 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-1.0.3.dist-info → specpulse-1.0.4.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: specpulse
-Version: 1.0.3
+Version: 1.0.4
 Summary: Specification-Driven Development Framework
 Home-page: https://github.com/specpulse
 Author: SpecPulse
@@ -66,7 +66,11 @@ 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.1)**: Fixed command documentation and improved AI integration clarity.
+> **Latest Update (v1.0.4)**: 
+> - ✅ **100% Working AI Commands**: Both Claude and Gemini commands now properly support arguments
+> - ✅ **95% Test Coverage**: Comprehensive test suite with 193+ tests
+> - ✅ **Fixed Command Formats**: Claude uses `$ARGUMENTS`, Gemini uses `{{args}}`
+> - ✅ **Enhanced Documentation**: Clearer examples and usage instructions
 
 ### Why SpecPulse?
 
@@ -114,25 +118,21 @@ specpulse init --ai gemini
 
 ```bash
 # Initialize a new feature
-/pulse init user-authentication
+/pulse user-authentication
+# Creates structure for 001-user-authentication feature
 
-# Create the specification
-/spec create "User login with OAuth2 and email/password"
-
-# Validate the specification
-/spec validate
+# Create the specification  
+/spec create user login with OAuth2 and email/password
+# Or just: /spec (for interactive mode)
 
 # Generate implementation plan
 /plan generate
-
-# Validate plan against constitution
-/plan validate
+# Or: /plan validate (to check existing plan)
 
 # Break down into tasks
 /task breakdown
-
-# Check task progress
-/task status
+# Or: /task update (to update task status)
+# Or: /task status (to see progress)
 ```
 
 ### Step 4: Validate & Ship
@@ -244,28 +244,41 @@ Stop guessing what users want:
 
 ### 🤖 Deep AI Integration
 
-**Claude Commands:**
+**How AI Commands Work:**
+
+Claude and Gemini use slash commands that accept arguments via `$ARGUMENTS`:
+
 ```bash
-# Feature initialization
-/pulse init <feature-name>        # Initialize new feature with structure
-
-# Specification management
-/spec create <description>        # Generate specification from requirements
-/spec update                      # Update existing specification
-/spec validate                    # Check specification completeness
-
-# Planning commands
-/plan generate                    # Create implementation plan from spec
-/plan validate                    # Validate plan against constitution
-
-# Task management
-/task breakdown                   # Generate tasks from plan
-/task update                      # Update task status
-/task status                      # Show task progress
+/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
 ```
 
-**Gemini Commands:**
-Same commands with TOML-based configuration for enhanced parsing.
+**Behind the Scenes:**
+- Commands capture arguments using `$ARGUMENTS` variable
+- Shell scripts in `scripts/` folder process the arguments
+- AI reads templates from `templates/` folder
+- Results are saved in `specs/`, `plans/`, `tasks/` folders
+- Memory system tracks progress in `memory/` folder
+
+**Claude vs Gemini:**
+- **Claude**: Uses Markdown command files (`.claude/commands/*.md`) with YAML frontmatter
+  - Arguments passed via `$ARGUMENTS` variable to shell scripts
+- **Gemini**: Uses TOML command files (`.gemini/commands/*.toml`) with simple format
+  - Arguments handled via `{{args}}` placeholder in prompts
+- Both support arguments and work the same way from user perspective
+
+**Command Arguments:**
+- Commands can accept arguments: `/command arg1 arg2`
+- Claude: Arguments passed to scripts via `$ARGUMENTS`
+- Gemini: Arguments injected via `{{args}}` placeholder
+- Commands can be used without arguments for interactive mode
 
 ## 📊 Real-World Impact
 
@@ -425,7 +438,8 @@ Built with inspiration from:
 ## 🚦 Project Status
 
 [![Build Status](https://img.shields.io/badge/build-passing-brightgreen)](https://github.com/specpulse/specpulse)
-[![Coverage](https://img.shields.io/badge/coverage-94%25-brightgreen)](https://github.com/specpulse/specpulse)
+[![Coverage](https://img.shields.io/badge/coverage-95%25-brightgreen)](https://github.com/specpulse/specpulse)
+[![Tests](https://img.shields.io/badge/tests-193%20passed-brightgreen)](https://github.com/specpulse/specpulse)
 [![Maintainability](https://img.shields.io/badge/maintainability-A-brightgreen)](https://github.com/specpulse/specpulse)
 
 ---

{specpulse-1.0.3.dist-info → specpulse-1.0.4.dist-info}/RECORD

@@ -1,17 +1,17 @@
-specpulse/__init__.py,sha256=jyEZnW74ap-Myn1nXo5LOSr7bZ2uRw-hHKJzQe4vQcY,270
+specpulse/__init__.py,sha256=af-q2jbt5GBQQ_WYRCFUC-vRvvxW5Yqi97Sd11wMTOg,270
 specpulse/cli/__init__.py,sha256=DpX6FoRJtSNjudsmZ3mTih_RIaWyiIgxew4-f8mOmFY,70
 specpulse/cli/main.py,sha256=bnf9xka3AIAyhkjCXGKI-T45eTKyzx0bwE68TOkTfU0,24486
 specpulse/core/__init__.py,sha256=VKHGdPDM38QM9yDIq05jxol4q8WFlFAeltOzYLsPuto,132
 specpulse/core/specpulse.py,sha256=YVqZMDO3AIbCsAHY32wIuUV1cH-hIKAcFkqR5WrInVw,29962
 specpulse/core/validator.py,sha256=dnaNUx7tj8V2K1TE6WPwrNWEiCpqC_b_DKryq6-A7Hk,12057
-specpulse/resources/commands/claude/plan.md,sha256=X9VZjJn5_BFDdAEsZDajDY3jIka71O-7UzuZrkhDuUM,1097
-specpulse/resources/commands/claude/pulse.md,sha256=ZP5ro49q-vTlILhvSs-yVG3KrPDHxnepqM12s5CT-fQ,854
-specpulse/resources/commands/claude/spec.md,sha256=CqbsQ0iyOVXPx0Shw7LCwD1U5ArLTuQkLwG_qaXenKI,1095
-specpulse/resources/commands/claude/task.md,sha256=fmWx9Un_gN3QpRpcTuN7IBjuCKfN27vX9EeKSgaAtVw,973
-specpulse/resources/commands/gemini/plan.toml,sha256=W6BtdGu6as7bBgaRQjvMpehraLnnk9MGw6bE0dzDMgY,1056
-specpulse/resources/commands/gemini/pulse.toml,sha256=3lfbWMBC2tVOanGQ1uNaLozUj9rAgcyNIgvAmgWCJVI,1078
-specpulse/resources/commands/gemini/spec.toml,sha256=5xL6lWzLncedC6KKAidZ9OBDheKcEWcxCYfOuRcR_Pk,822
-specpulse/resources/commands/gemini/task.toml,sha256=HRMB11jTENZ0iWNUDKQfKXThJmU96wCNYGtRW-J-l-c,1048
+specpulse/resources/commands/claude/plan.md,sha256=QAr9kmue7dtj7uWBMTL4xd9NWClUTNEPdErEWmYJHSs,1672
+specpulse/resources/commands/claude/pulse.md,sha256=liq46kHS4SfKvnmzclti3-Z2DsyYydHLn_4XmQC05zk,1323
+specpulse/resources/commands/claude/spec.md,sha256=1jWELtO02M6WnhUQ2QwBZjEUyKVqgfTdn5XtkNVVxV0,2227
+specpulse/resources/commands/claude/task.md,sha256=lpgdzyqEKfDP-c6CzAUMTFzcVegrSFLl7_QtYx-3rGc,1748
+specpulse/resources/commands/gemini/plan.toml,sha256=cQAIrFZZarJxzCc8BJp22ot0livEAHXNxqsJaRHenps,1308
+specpulse/resources/commands/gemini/pulse.toml,sha256=-OpmaMIZd9AASp00onGH5t4-CCKaoQvNYLSxfv3ztdw,837
+specpulse/resources/commands/gemini/spec.toml,sha256=OJhrcFRgnSyaqPOKg-3NhWzOZw1XiDYj3zg_XmQ79po,1346
+specpulse/resources/commands/gemini/task.toml,sha256=wed7v0XL0QPGysr1dMKF-Q5M7qeT-cbpf94l7vae1CY,1398
 specpulse/resources/memory/constitution.md,sha256=MUrX9a6inWAa58Oas-Ff_s1sIs04ehr7sSGOYjdAFv4,8286
 specpulse/resources/memory/context.md,sha256=6021CJIJNTMOIB6xTxc3ehEGOUglIfl_IyJQXwzjw3U,562
 specpulse/resources/memory/decisions.md,sha256=ZwzVyOPB2mIzwveWpGmedej7ncI81GALg8WVy6AeZA4,686
@@ -25,9 +25,9 @@ specpulse/resources/templates/task.md,sha256=TBR0BSbQFWKwFZBx1NU6wmzeRVdzrydS4X4
 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.0.3.dist-info/licenses/LICENSE,sha256=ImSFezK-Phy0oTBqZipcajsJfPZT8mmg8m3jkgNdNhA,1066
-specpulse-1.0.3.dist-info/METADATA,sha256=45aL3igvbm_kSF04qBSu3hhMepngB9B9VOT5mWmkgoI,14325
-specpulse-1.0.3.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
-specpulse-1.0.3.dist-info/entry_points.txt,sha256=GwMaCKWSCFZlJMrTNavEYrnREynIS6dM3B0ILxnaouA,83
-specpulse-1.0.3.dist-info/top_level.txt,sha256=pEfkFil5xe38J00OHrBrJ07xpbm6bRnGhI8B07O9KeI,10
-specpulse-1.0.3.dist-info/RECORD,,
+specpulse-1.0.4.dist-info/licenses/LICENSE,sha256=ImSFezK-Phy0oTBqZipcajsJfPZT8mmg8m3jkgNdNhA,1066
+specpulse-1.0.4.dist-info/METADATA,sha256=txplotk_lJ4sSQp7Or2PQ78RFOfIhalB_MQHCGCjVh4,15612
+specpulse-1.0.4.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
+specpulse-1.0.4.dist-info/entry_points.txt,sha256=GwMaCKWSCFZlJMrTNavEYrnREynIS6dM3B0ILxnaouA,83
+specpulse-1.0.4.dist-info/top_level.txt,sha256=pEfkFil5xe38J00OHrBrJ07xpbm6bRnGhI8B07O9KeI,10
+specpulse-1.0.4.dist-info/RECORD,,