SpecPulse v2.4.4 - AI-Enhanced Specification-Driven Development Framework
Project description
SpecPulse v2.4.4
AI-Enhanced Specification-Driven Development Framework
Build better software with specifications first, enhanced by AI
๐ Quick Start
Install
pip install specpulse
Initialize Project
# New project
specpulse init my-project --ai claude
cd my-project
# Or add to existing project
cd existing-project
specpulse init --here --ai claude
Start Your First Feature
# Initialize feature
specpulse feature init user-authentication
# CLI creates empty template
specpulse spec create "OAuth2 authentication with JWT tokens"
# AI ESSENTIAL: Expand specification with details
# In Claude Code or Gemini CLI:
/sp-spec expand "OAuth2 authentication with JWT tokens"
# Generate implementation plan (CLI creates template)
specpulse plan create "Secure authentication flow"
# AI ESSENTIAL: Expand plan with detailed steps
# In Claude Code or Gemini CLI:
/sp-plan expand "Secure authentication flow"
# Break into tasks (CLI creates template)
specpulse task breakdown plan-001
# AI ESSENTIAL: Create detailed task breakdown
# In Claude Code or Gemini CLI:
/sp-task expand plan-001
Use AI Commands
In Claude Code or Gemini CLI:
/sp-pulse payment-system # Initialize feature
/sp-spec create "Payment processing" # Create specification
/sp-plan expand # Generate and expand implementation plan
/sp-task breakdown # Break into tasks
/sp-status # Check progress
๐ What It Does
SpecPulse helps you build software systematically:
โ Specification First - Clear specs before coding โ AI-Enhanced - Essential for creating and expanding specifications โ CLI-First Architecture - Fast, reliable commands for structure โ Privacy-First - No external API calls, completely local โ Git Integration - Automatic branch and context management
Important: SpecPulse CLI provides the structure, but AI assistants are essential for creating detailed specifications and implementation plans.
๐ค AI Integration
Supported AI Platforms
- Claude Code - Custom slash commands (
/sp-*) - Gemini CLI - Custom commands (
/sp-*)
How It Works
Critical CLI-AI Balance:
User Request: /sp-spec "OAuth2 login with JWT"
โ
Step 1: TRY CLI FIRST (Never fail)
Bash: specpulse spec create "OAuth2 login with JWT"
โ
Step 2: CLI creates structure and files
โ Empty spec file created
โ Metadata added
โ Directory structure ready
โ
Step 3: AI expands content (Safe file operations)
Claude reads created file, adds detailed content
โ
Step 4: Result: Complete specification
Critical Balance Rules:
- CLI First - Always try CLI commands first
- No CLI Errors - CLI commands must never fail with valid input
- Safe File Operations - AI only works on files CLI creates
- Cross-Platform - Works on Windows, macOS, Linux without issues
- Unicode Safe - No encoding problems on any platform
๐ Project Structure
After initialization:
my-project/
โโโ .specpulse/ # All project data
โ โโโ specs/ # Feature specifications
โ โโโ plans/ # Implementation plans
โ โโโ tasks/ # Development tasks
โ โโโ memory/ # Project context and decisions
โ โโโ templates/ # Specification templates
โโโ .claude/ # Claude Code commands
โโโ .gemini/ # Gemini CLI commands
๐ป Core Commands
Project Management
specpulse init <project-name> # Initialize new project
specpulse init --here --ai claude # Add to existing project
specpulse doctor # Health check
specpulse doctor # Check project health and validate
Feature Development
specpulse feature init <name> # Start new feature
specpulse feature continue <id> # Switch to existing feature
specpulse feature list # List all features
Specifications
specpulse spec create "<description>" # Create empty template (AI needed for content)
specpulse spec validate # Validate specs
Note: specpulse spec create creates empty templates. Use AI commands (/sp-spec) to fill with detailed content.
Planning & Tasks
specpulse plan create "<description>" # Create empty plan template (AI needed for details)
specpulse task breakdown <plan-id> # Create empty task breakdown (AI needed for details)
Note: CLI creates templates, but AI is essential for detailed planning and task breakdown.
๐ค AI Commands (Slash Commands)
Feature Commands
/sp-pulse <feature-name> # Initialize feature
/sp-continue <feature-id> # Switch to existing feature
/sp-status # Track progress across features
Specification Commands (ESSENTIAL)
/sp-spec create "<description>" # Create and expand detailed specification
/sp-spec validate <spec-id> # Validate specification
/sp-spec expand <spec-id> # Expand existing specification with more details
Planning Commands (ESSENTIAL)
/sp-plan expand # Generate and expand implementation plan
/sp-plan validate <plan-id> # Validate plan
/sp-plan expand <plan-id> # Expand plan with more implementation details
Task Commands (ESSENTIAL)
/sp-task breakdown # Break plan into detailed tasks
/sp-task expand <plan-id> # Expand tasks with implementation details
/sp-task status <task-id> # Check task status
Advanced Commands
/sp-execute # Execute next pending task and continue
/sp-execute next # Same as above
/sp-execute all # Execute ALL pending tasks non-stop
/sp-execute T001 # Execute specific task
/sp-execute AUTH-T001 # Execute specific service task
/sp-decompose <spec-id> # Decompose spec into components
/sp-clarify <spec-id> # Clarify specification
๐ค Custom Commands Architecture
How Custom Commands Work
All /sp-* commands follow the same CLI-First Pattern:
User: /sp-spec "Create user authentication"
โ
Step 1: Try CLI Command (Never fails)
Bash: specpulse spec create "Create user authentication"
โ Creates empty spec file
โ Adds metadata
โ Updates project structure
โ
Step 2: AI Expands Content (Safe operations)
Claude reads the created file
Claude expands with detailed requirements
Claude saves the enhanced content
โ
Result: Complete, detailed specification
Critical Design Principles
โ CLI First, Always
- Custom commands ALWAYS try CLI commands first
- CLI commands are guaranteed to work on all platforms
- CLI handles cross-platform path and encoding issues
- CLI creates the foundation that AI builds upon
โ Safe File Operations
- AI only works on files that CLI has already created
- AI uses proper encoding and path handling
- AI never creates files in protected directories
- AI respects file permissions and ownership
โ Platform Independence
- Same behavior on Windows, macOS, Linux
- Unicode and emoji support on all platforms
- Automatic path separator handling
- Consistent error handling and recovery
โ Error Resilience
- CLI commands validate input and provide helpful errors
- AI gracefully handles file operation failures
- Built-in recovery mechanisms
- Clear error messages and suggestions
Custom Command Examples
Specification Creation
# User: /sp-spec "OAuth2 authentication with JWT"
# Command execution:
# Step 1: CLI (Always succeeds)
specpulse spec create "OAuth2 authentication with JWT"
# โ Creates: .specpulse/specs/001-feature/spec-001.md
# Step 2: AI (Safe content expansion)
# Claude reads the created file
# Claude adds detailed requirements, security considerations, API design
# Claude saves the enhanced specification
Task Breakdown
# User: /sp-task breakdown plan-001
# Command execution:
# Step 1: CLI (Always succeeds)
specpulse task breakdown plan-001
# โ Creates: .specpulse/tasks/001-feature/task-001.md, task-002.md, etc.
# Step 2: AI (Safe content expansion)
# Claude reads task files
# Claude adds implementation details, dependencies, time estimates
# Claude enhances task descriptions with technical specifics
Continuous Execution
# User: /sp-execute
# Command execution:
# Step 1: CLI (Status check)
specpulse --no-color doctor
# โ Gets current project status and pending tasks
# Step 2: AI (Safe task execution)
# Claude reads next task file
# Claude implements the task requirements
# Claude marks task as completed and moves to next
Cross-Platform Handling
Windows (CMD/PowerShell)
# Works with Unicode and emojis
/sp-spec "User authentication ๐ with JWT tokens"
# Automatic path handling
# CLI: Creates C:\project\.specpulse\specs\001-feature\spec-001.md
# AI: Reads and writes with UTF-8 encoding
macOS (zsh/bash)
# Works with native macOS paths
/sp-spec "iOS notification system ๐ฑ"
# Automatic path handling
# CLI: Creates /Users/user/project/.specpulse/specs/001-feature/spec-001.md
# AI: Reads and writes with proper macOS encoding
Linux (bash/zsh)
# Works with Linux file permissions
/sp-spec "Docker container orchestration ๐ณ"
# Automatic path handling
# CLI: Creates /home/user/project/.specpulse/specs/001-feature/spec-001.md
# AI: Reads and writes with proper Linux permissions
Benefits of This Architecture
- โ Reliability: CLI commands are tested and stable
- โ Consistency: Same behavior across all platforms
- โ Safety: AI only operates on CLI-created foundation
- โ Recovery: Clear error handling and fallback mechanisms
- โ Flexibility: AI can enhance without breaking core functionality
๐ Task Execution with /sp-execute
What is /sp-execute?
/sp-execute is a continuous execution mode that executes tasks without stopping between them. It implements tasks sequentially and automatically moves to the next task until all are completed or blocked.
How /sp-execute Works
Non-Stop Execution Pattern:
/sp-execute
โ
Step 1: Find next pending task (T001 or AUTH-T001)
โ
Step 2: Mark as in-progress: [ ] โ [>]
โ
Step 3: Implement the task
โ
Step 4: Mark as completed: [>] โ [x]
โ
Step 5: Automatically continue to next task
โ
Repeat until all tasks complete
/sp-execute Usage
In Claude Code or Gemini CLI:
# Execute next pending task and continue
/sp-execute
# Execute ALL pending tasks non-stop
/sp-execute all
# Execute specific task and continue with related tasks
/sp-execute T001
/sp-execute AUTH-T001
Task Status Markers
[ ]- Pending task (ready to execute)[>]- In progress (currently working on)[x]- Completed (done)[!]- Blocked (waiting for dependency)
Continuous Execution Example
# User: /sp-execute
# AI response:
Found 15 pending tasks
Starting with T001: Implementing user model...
โ User model created
Moving to T002: Creating authentication service...
โ Authentication service implemented
Continue with T003, T004, T005... WITHOUT STOPPING
All 15 tasks completed successfully!
Batch Execution
# User: /sp-execute all
# AI response:
Processing ALL pending tasks in one go
No interruptions or pauses
Complete the entire task list
Final report only
Non-Stop Execution Rules
CRITICAL: /sp-execute follows strict non-stop execution rules:
- NO EXPLANATIONS between tasks - just execute
- NO WAITING for confirmation - keep going
- NO SUMMARIES after each task - save for the end
- ONLY STOP when:
- All tasks completed
- Hit a blocker
- Critical error occurs
- User explicitly says "stop"
Workflow Integration
Starting Fresh
/sp-pulse new-feature
/sp-spec "Create user authentication with OAuth2"
/sp-plan
/sp-task
/sp-execute all # Complete everything!
Resuming Work
/sp-continue 001-user-auth
/sp-execute # Continue from where we left off
Error Handling
If an error occurs during task execution:
- Mark task as blocked:
[!] - Note the error in task file
- Skip to next available task
- Continue execution
- Report all blockers at the end
Progress Tracking
During execution, AI maintains:
- Task completion counter
- Progress percentage
- List of completed tasks
- List of any blockers encountered
Final Report Example
## Execution Complete
**Progress**: 100% (25/25 tasks)
**Duration**: Continuous execution
**Status**: All tasks completed
### Summary
โ 25 tasks completed
โ 0 tasks blocked
โ 0 tasks remaining
Ready for validation: /sp-validate
Benefits of /sp-execute
- Maximum efficiency - No time wasted between tasks
- Flow state - Continuous productive work
- Rapid delivery - Complete features faster
- Reduced context switching - Stay focused on implementation
- Automated workflow - Let AI handle the execution
Perfect for: Completing entire feature sets, maintaining momentum, and rapid prototyping.
๐ค CLI vs AI: Essential Partnership
What CLI Does (Structure)
- โ Creates directory structure
- โ Generates empty templates
- โ Manages metadata and IDs
- โ Validates syntax and structure
- โ Handles file operations
- โ Provides health checks
What AI Does (Content)
- โ Fills templates with detailed content
- โ Creates comprehensive specifications
- โ Generates implementation plans
- โ Breaks down complex tasks
- โ Provides technical insights
- โ Executes implementation tasks
They Work Together (Critical Balance)
CLI: Creates structure (NEVER FAILS)
AI: Expands with detailed content
CLI: Validates and organizes
AI: Suggests improvements
CLI: Manages cross-platform paths
AI: Executes implementation
Critical Balance: CLI creates safe, cross-platform foundation. AI adds value without breaking the system.
Platform Guarantee: Works identically on Windows, macOS, Linux with proper Unicode handling.
๐ Complete Workflow Example
# 1. Initialize project
specpulse init my-app --ai claude
cd my-app
# 2. Start feature
specpulse feature init user-auth
# 3. Create specification (CLI)
specpulse spec create "OAuth2 login with JWT"
# 4. Or use AI commands
# In Claude Code:
# /sp-spec create "OAuth2 login with JWT"
# 5. Generate plan
specpulse plan create "OAuth2 implementation"
# 6. Break into tasks
specpulse task breakdown plan-001
# 7. Validate everything
specpulse doctor --fix
specpulse doctor
๐ง Requirements
- Python: 3.11 or higher
- Git: Recommended for branch-based features
- Platform: Windows, macOS, Linux (full cross-platform support)
๐ Cross-Platform Guarantees
SpecPulse works identically on all platforms:
โ Windows Support
- Unicode Safe: No encoding issues with emojis and special characters
- Path Handling: Automatic path separator conversion (
\โ/) - PowerShell + CMD: Works with both Windows shells
- Long Paths: Handles Windows path length limitations
โ macOS Support
- Native Compatibility: Works with macOS file system and shell
- Homebrew Integration: Easy installation and updates
- Xcode Tools: All development dependencies supported
โ Linux Support
- All Distributions: Ubuntu, CentOS, Fedora, Arch, etc.
- Package Managers: Works with apt, yum, dnf, pacman
- File Permissions: Proper handling of Linux file permissions
๐ Documentation
- Installation Guide - Detailed installation
- AI Integration Guide - AI assistant setup
- Migration Guide - Upgrading from previous versions
- Troubleshooting Guide - Common issues
Getting Help
specpulse --help # General help
specpulse doctor # Project health check
specpulse doctor --fix # Health check with auto-fix
๐ What's New in v2.4.1
CLI-First Architecture
- AI assistants try CLI commands before file operations
- Deprecated
specpulse ai *commands - Better performance and reliability
Enhanced Features
- Improved validation system with auto-fix
- Better error handling and recovery
- Optimized performance and memory usage
๐ Get Started Now
# Install SpecPulse (cross-platform)
pip install specpulse
# Create your first project
specpulse init my-project --ai claude
cd my-project
# Start developing with AI assistance
specpulse feature init my-feature
# CLI creates structure, AI fills content
specpulse spec create "My first feature"
# Then in Claude Code: /sp-spec expand "My first feature"
# Or use AI commands directly
# In Claude Code or Gemini CLI:
# /sp-pulse my-new-feature
# /sp-spec create "Detailed feature description"
# /sp-plan expand
# /sp-execute all
# Validate and enjoy
specpulse doctor
Guaranteed to work on: Windows, macOS, Linux with full Unicode support! ๐
Made with โค๏ธ for developers who value specifications and quality
SpecPulse v2.4.4 - CLI-First โข AI-Enhanced โข Cross-Platform โข Reliable
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file specpulse-2.4.4.tar.gz.
File metadata
- Download URL: specpulse-2.4.4.tar.gz
- Upload date:
- Size: 212.0 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.13.9
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
93371df13cf47522bee1af4f3abbf86e6724365aa5ac8b877f3e7f004ef2283b
|
|
| MD5 |
37c51e374bd361d4beca3847dfddbd53
|
|
| BLAKE2b-256 |
7dea5a66524f25d3e1da1fcd6c79d641d4b169b08dc4c7008fe853f5b9114d3a
|
File details
Details for the file specpulse-2.4.4-py3-none-any.whl.
File metadata
- Download URL: specpulse-2.4.4-py3-none-any.whl
- Upload date:
- Size: 226.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.13.9
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
c03d8ffa96a440b4ed0889c2408d43d2979d9ed346eda063d70d04fe448ef05e
|
|
| MD5 |
c0d80aa57f71f6dfb90e3b223a77aaab
|
|
| BLAKE2b-256 |
cb3df27c44218f7e33060c96263888bf6db41faee1a2fc51507ee68a98694082
|