specpulse 1.0.3__tar.gz → 1.0.4__tar.gz

{specpulse-1.0.3/specpulse.egg-info → specpulse-1.0.4}/PKG-INFO

@@ -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 → specpulse-1.0.4}/README.md

@@ -21,7 +21,11 @@
 
 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?
 
@@ -69,25 +73,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
@@ -199,28 +199,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
 
@@ -380,7 +393,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 → specpulse-1.0.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "specpulse"
-version = "1.0.3"
+version = "1.0.4"
 description = "Specification-Driven Development Framework"
 readme = "README.md"
 requires-python = ">=3.11"

{specpulse-1.0.3 → specpulse-1.0.4}/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-1.0.4/specpulse/resources/commands/claude/plan.md

@@ -0,0 +1,73 @@
+---
+name: plan
+description: Generate or validate implementation plans
+allowed_tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+---
+
+# /plan Command
+
+Generate implementation plans from specifications following SpecPulse methodology.
+
+## Usage
+```
+/plan [action]
+```
+
+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
+
+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
+
+   c. **Generate plan sections**:
+   - Technology stack
+   - Architecture overview
+   - Implementation phases
+   - API contracts
+   - Data models
+   - Testing strategy
+
+   d. **Track complexity**:
+   - If >3 modules, document justification
+   - Create simplification roadmap
+
+   e. **Write plan** to `plans/XXX-feature/plan.md`
+
+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:
+- ✅ Using ≤3 projects/modules
+- ✅ Tests defined before code
+- ✅ Using framework features directly
+- ✅ No premature abstractions
+- ✅ Research completed
+
+## Example
+```
+/plan generate
+```

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

@@ -0,0 +1,52 @@
+---
+name: pulse
+description: Initialize a new feature with SpecPulse framework
+allowed_tools:
+  - Bash
+  - Read
+  - Write
+  - Edit
+---
+
+# /pulse Command
+
+Initialize a new feature following SpecPulse methodology.
+
+## Usage
+```
+/pulse <feature-name>
+```
+
+## 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` with current feature
+   - Create git branch if in git repository
+
+4. **Report results** to user with created structure
+
+## Example
+```
+User: /pulse user-authentication
+```
+
+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` to create the specification
+- Use `/plan` to generate implementation plan
+- Use `/task` to break down into tasks

specpulse-1.0.4/specpulse/resources/commands/claude/spec.md

@@ -0,0 +1,81 @@
+---
+name: spec
+description: Create or manage feature specifications
+allowed_tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+---
+
+# /spec Command
+
+Create, update, or validate feature specifications using SpecPulse methodology.
+
+## Usage
+```
+/spec [action] [description]
+```
+
+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
+
+### Creating a new specification
+```
+User: /spec user authentication with OAuth2 and email/password
+```
+I will create a comprehensive specification with all requirements.
+
+### Updating existing specification
+```
+User: /spec update
+```
+I will read the current spec and guide through updates.
+
+### 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 have)
+- User Stories with Acceptance Criteria  
+- Technical Specifications
+- Clarifications Needed
+- Validation Checklist

specpulse-1.0.4/specpulse/resources/commands/claude/task.md

@@ -0,0 +1,78 @@
+---
+name: task
+description: Generate and manage task breakdowns
+allowed_tools:
+  - Read
+  - Write  
+  - Edit
+  - Bash
+---
+
+# /task Command
+
+Generate task breakdowns from implementation plans using SpecPulse structure.
+
+## Usage
+```
+/task [action]
+```
+
+Actions: `breakdown`, `update`, `status` (defaults to `breakdown`)
+
+## Implementation
+
+When called with `/task $ARGUMENTS`, I will:
+
+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
+
+      - For each task:
+   - Use T[XXX] format (T001, T002)
+   - Include clear description
+   - Mark dependencies
+   - Estimate complexity (S/M/L/XL)
+   - Assign priority
+
+   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
+- [ ] T001: [S] Set up project structure
+- [ ] T002: [M] Create database schema
+- [x] T003: [L] Implement authentication
+```
+
+## Example
+```
+/task breakdown
+```

specpulse-1.0.4/specpulse/resources/commands/gemini/plan.toml

@@ -0,0 +1,51 @@
+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-1.0.4/specpulse/resources/commands/gemini/pulse.toml

@@ -0,0 +1,24 @@
+description = "Initialize a new feature with SpecPulse framework"
+prompt = """
+Initialize a new SpecPulse feature with the name: {{args}}
+
+Please follow these steps:
+
+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
+
+4. Report the results showing:
+   - Created structure paths
+   - Feature ID and branch name
+   - Next steps for the user
+
+If no feature name is provided, ask the user for the feature name first.
+
+Example usage: /pulse user-authentication
+"""

specpulse-1.0.4/specpulse/resources/commands/gemini/spec.toml

@@ -0,0 +1,37 @@
+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
+
+## 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. Check all required sections are filled
+2. Count [NEEDS CLARIFICATION] markers
+3. Verify acceptance criteria are testable
+4. Report validation results
+
+Examples:
+- /spec user authentication with OAuth2 and email/password
+- /spec update
+- /spec validate
+"""