specpulse 1.3.2__tar.gz → 1.4.0__tar.gz

{specpulse-1.3.2 → specpulse-1.4.0}/MANIFEST.in

@@ -2,7 +2,7 @@ include README.md
 include LICENSE
 include pyproject.toml
 include requirements.txt
-recursive-include specpulse/resources *.md *.sh *.toml *.yaml
+recursive-include specpulse/resources *.md *.sh *.ps1 *.toml *.yaml
 recursive-include specpulse/resources/templates *
 recursive-include specpulse/resources/memory *
 recursive-include specpulse/resources/scripts *

{specpulse-1.3.2/specpulse.egg-info → specpulse-1.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: specpulse
-Version: 1.3.2
+Version: 1.4.0
 Summary: Specification-Driven Development Framework
 Home-page: https://github.com/specpulse
 Author: SpecPulse
@@ -32,6 +32,7 @@ Requires-Dist: rich>=13.0
 Requires-Dist: jinja2>=3.0
 Requires-Dist: gitpython>=3.1
 Requires-Dist: toml>=0.10
+Requires-Dist: packaging>=21.0
 Provides-Extra: dev
 Requires-Dist: pytest>=7.0; extra == "dev"
 Requires-Dist: pytest-cov>=4.0; extra == "dev"
@@ -56,7 +57,7 @@ Dynamic: requires-python
 
 *Build better software faster by putting specifications first and letting AI handle the implementation details.*
 
-[Installation](#-installation) • [Quick Start](#-quick-start) • [Features](#-features) • [Documentation](#-documentation) • [Contributing](#-contributing)
+[Installation](#-installation) • [Quick Start](#-quick-start) • [Usage Guide](#-usage-guide) • [Features](#-features) • [Documentation](#-documentation) • [Contributing](#-contributing)
 
 </div>
 
@@ -64,21 +65,22 @@ Dynamic: requires-python
 
 ## 🎯 What is SpecPulse?
 
-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.
+SpecPulse is a universal **Specification-Driven Development (SDD)** framework that works with ANY software project - web apps, mobile apps, desktop software, games, APIs, ML projects, and more. It ensures every feature starts with clear specifications, validated plans, and tracked tasks.
 
-> **Latest Update (v1.3.0)**:
-> - 🚀 **Continuous Task Execution**: New `/sp-execute` command for non-stop task completion
-> - ⚡ **Flow State Development**: Execute all tasks without interruptions
-> - 🔄 **Smart Task Progression**: Automatic advancement through task lists
-> - 🎯 **Batch Processing**: Complete entire features in one command
-> - **Previous (v1.2.0)**: Microservice decomposition, service-based planning, smart workflow detection
-> - **Previous (v1.1.0)**: Command prefix system, multi-spec workflow, versioned files
+> **Latest Update (v1.4.0)** - Complete Framework Revolution:
+> - 🚀 **Universal SDD Framework**: Transformed from Constitutional to Specification-Driven Development
+> - 🎯 **No Technology Restrictions**: Support for ANY technology stack - web, mobile, desktop, games, ML
+> - 🧪 **86% Test Coverage**: Complete test suite rewrite with 98.3% success rate
+> - ✨ **9 Universal Principles**: Flexible principles replacing rigid articles
+> - 🔄 **Major API Updates**: All methods renamed from `constitution` to `sdd_compliance`
+> - 📝 **Enhanced Documentation**: Complete overhaul of docs and templates
 
 ### Why SpecPulse?
 
+- **🎯 Universal**: Works with ANY project type - web, mobile, desktop, games, APIs, ML
 - **🔍 Clarity First**: No more ambiguous requirements or scope creep
 - **🤖 AI-Optimized**: Designed specifically for Claude and Gemini workflows
-- **✅ Quality Gates**: Built-in checks prevent bad code from entering your codebase
+- **✅ Quality Gates**: Built-in checks ensure quality for your specific project type
 - **📊 Full Traceability**: Every decision, change, and requirement is tracked
 - **🚀 Faster Delivery**: Structured approach reduces rework and debugging time
 
@@ -175,21 +177,21 @@ specpulse sync
 
 ## ✨ Features
 
-### 🏛️ Constitutional Development
+### 🏛️ Universal SDD Principles
 
-Nine immutable principles guide every line of code:
+Nine principles that enable Specification-Driven Development for ANY project:
 
-| Article | Principle | Benefit |
-|---------|-----------|---------|
-| **I** | Library-First | Every feature is modular and reusable |
-| **II** | CLI Interface | Text-based interaction for automation |
-| **III** | Test-First | Tests before code, always |
-| **IV** | Staged Implementation | Incremental, validated progress |
-| **V** | Direct Framework Usage | No unnecessary abstractions |
-| **VI** | No Abstraction Layers | Keep it simple, keep it maintainable |
-| **VII** | Simplicity Enforcement | Maximum 3 modules per feature |
-| **VIII** | Complexity Tracking | Document and justify exceptions |
-| **IX** | Framework-First | Don't reinvent the wheel |
+| # | Principle | Purpose | Applies To |
+|---|-----------|---------|------------|
+| **1** | Specification First | Start with clear requirements | All projects |
+| **2** | Incremental Planning | Phased implementation | Web, mobile, desktop, games |
+| **3** | Task Decomposition | Concrete, executable tasks | Any technology stack |
+| **4** | Traceable Implementation | Link code to specs | All languages |
+| **5** | Continuous Validation | Ensure spec alignment | Any framework |
+| **6** | Quality Assurance | Appropriate testing | GUI, CLI, API, games |
+| **7** | Architecture Documentation | Record decisions | Any architecture |
+| **8** | Iterative Refinement | Evolve with learnings | All methodologies |
+| **9** | Stakeholder Alignment | Shared understanding | Any team size |
 
 ### 🚦 Phase Gates System
 
@@ -201,10 +203,10 @@ Before any code is written, features must pass:
 └────────┬────────┘
          ↓
 ┌─────────────────┐
-│ Phase Gates     │ → Constitutional compliance check
-└────────┬────────┘     Simplicity validation (≤3 modules)
-         ↓              Test strategy defined
-┌─────────────────┐     Framework selected
+│ Phase Gates     │ → SDD compliance check
+└────────┬────────┘     Quality assurance strategy defined
+         ↓              Architecture documented
+┌─────────────────┐     Stakeholder alignment confirmed
 │ Implementation  │     Research completed
 └────────┬────────┘
          ↓
@@ -253,7 +255,7 @@ memory/
 
 - **Persistent Context**: Never lose track of project state
 - **Decision History**: Understand why choices were made
-- **Constitutional Enforcement**: Principles that can't be violated
+- **SDD Enforcement**: Universal principles for any software project
 
 ### 🔍 [NEEDS CLARIFICATION] Markers
 
@@ -573,6 +575,45 @@ pytest tests/
 - **[GitHub Repository](https://github.com/specpulse/specpulse)** - Source code and issues
 - **Command Reference** - See AI Integration section above for full command list
 
+## 📚 Usage Guide
+
+### How to Break Your Project into Features (Pulses)
+
+A complete guide is available in **[SPECPULSE_USAGE_GUIDE.md](SPECPULSE_USAGE_GUIDE.md)** which covers:
+- Feature decomposition strategies
+- Sizing guidelines (3-15 tasks per pulse)
+- Naming conventions (001-feature-name format)
+- Real-world examples for different project types
+- Best practices for feature boundaries
+
+#### Quick Examples
+
+**E-Commerce Platform:**
+```
+001-user-authentication    # Registration, login, sessions
+002-product-catalog        # Products, categories, search
+003-shopping-cart          # Cart management, calculations
+004-payment-processing     # Gateway, transactions, receipts
+005-order-management       # History, tracking, refunds
+```
+
+**SaaS Application:**
+```
+001-tenant-management      # Multi-tenancy, workspaces
+002-subscription-billing   # Plans, payments, invoices
+003-api-management        # Keys, rate limiting, docs
+004-admin-dashboard       # Analytics, reports, settings
+005-webhook-system        # Events, notifications, logs
+```
+
+**Key Principles:**
+- Each pulse should be **independent** and **testable**
+- Size appropriately for your project type
+- Use **sequential numbering** (001, 002, 003...)
+- Follow the **9 universal SDD principles**
+
+See the full guide for detailed breakdowns and strategies.
+
 ## 📄 License
 
 MIT License - see [LICENSE](LICENSE) file for details.

{specpulse-1.3.2 → specpulse-1.4.0}/README.md

@@ -11,7 +11,7 @@
 
 *Build better software faster by putting specifications first and letting AI handle the implementation details.*
 
-[Installation](#-installation) • [Quick Start](#-quick-start) • [Features](#-features) • [Documentation](#-documentation) • [Contributing](#-contributing)
+[Installation](#-installation) • [Quick Start](#-quick-start) • [Usage Guide](#-usage-guide) • [Features](#-features) • [Documentation](#-documentation) • [Contributing](#-contributing)
 
 </div>
 
@@ -19,21 +19,22 @@
 
 ## 🎯 What is SpecPulse?
 
-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.
+SpecPulse is a universal **Specification-Driven Development (SDD)** framework that works with ANY software project - web apps, mobile apps, desktop software, games, APIs, ML projects, and more. It ensures every feature starts with clear specifications, validated plans, and tracked tasks.
 
-> **Latest Update (v1.3.0)**:
-> - 🚀 **Continuous Task Execution**: New `/sp-execute` command for non-stop task completion
-> - ⚡ **Flow State Development**: Execute all tasks without interruptions
-> - 🔄 **Smart Task Progression**: Automatic advancement through task lists
-> - 🎯 **Batch Processing**: Complete entire features in one command
-> - **Previous (v1.2.0)**: Microservice decomposition, service-based planning, smart workflow detection
-> - **Previous (v1.1.0)**: Command prefix system, multi-spec workflow, versioned files
+> **Latest Update (v1.4.0)** - Complete Framework Revolution:
+> - 🚀 **Universal SDD Framework**: Transformed from Constitutional to Specification-Driven Development
+> - 🎯 **No Technology Restrictions**: Support for ANY technology stack - web, mobile, desktop, games, ML
+> - 🧪 **86% Test Coverage**: Complete test suite rewrite with 98.3% success rate
+> - ✨ **9 Universal Principles**: Flexible principles replacing rigid articles
+> - 🔄 **Major API Updates**: All methods renamed from `constitution` to `sdd_compliance`
+> - 📝 **Enhanced Documentation**: Complete overhaul of docs and templates
 
 ### Why SpecPulse?
 
+- **🎯 Universal**: Works with ANY project type - web, mobile, desktop, games, APIs, ML
 - **🔍 Clarity First**: No more ambiguous requirements or scope creep
 - **🤖 AI-Optimized**: Designed specifically for Claude and Gemini workflows
-- **✅ Quality Gates**: Built-in checks prevent bad code from entering your codebase
+- **✅ Quality Gates**: Built-in checks ensure quality for your specific project type
 - **📊 Full Traceability**: Every decision, change, and requirement is tracked
 - **🚀 Faster Delivery**: Structured approach reduces rework and debugging time
 
@@ -130,21 +131,21 @@ specpulse sync
 
 ## ✨ Features
 
-### 🏛️ Constitutional Development
+### 🏛️ Universal SDD Principles
 
-Nine immutable principles guide every line of code:
+Nine principles that enable Specification-Driven Development for ANY project:
 
-| Article | Principle | Benefit |
-|---------|-----------|---------|
-| **I** | Library-First | Every feature is modular and reusable |
-| **II** | CLI Interface | Text-based interaction for automation |
-| **III** | Test-First | Tests before code, always |
-| **IV** | Staged Implementation | Incremental, validated progress |
-| **V** | Direct Framework Usage | No unnecessary abstractions |
-| **VI** | No Abstraction Layers | Keep it simple, keep it maintainable |
-| **VII** | Simplicity Enforcement | Maximum 3 modules per feature |
-| **VIII** | Complexity Tracking | Document and justify exceptions |
-| **IX** | Framework-First | Don't reinvent the wheel |
+| # | Principle | Purpose | Applies To |
+|---|-----------|---------|------------|
+| **1** | Specification First | Start with clear requirements | All projects |
+| **2** | Incremental Planning | Phased implementation | Web, mobile, desktop, games |
+| **3** | Task Decomposition | Concrete, executable tasks | Any technology stack |
+| **4** | Traceable Implementation | Link code to specs | All languages |
+| **5** | Continuous Validation | Ensure spec alignment | Any framework |
+| **6** | Quality Assurance | Appropriate testing | GUI, CLI, API, games |
+| **7** | Architecture Documentation | Record decisions | Any architecture |
+| **8** | Iterative Refinement | Evolve with learnings | All methodologies |
+| **9** | Stakeholder Alignment | Shared understanding | Any team size |
 
 ### 🚦 Phase Gates System
 
@@ -156,10 +157,10 @@ Before any code is written, features must pass:
 └────────┬────────┘
          ↓
 ┌─────────────────┐
-│ Phase Gates     │ → Constitutional compliance check
-└────────┬────────┘     Simplicity validation (≤3 modules)
-         ↓              Test strategy defined
-┌─────────────────┐     Framework selected
+│ Phase Gates     │ → SDD compliance check
+└────────┬────────┘     Quality assurance strategy defined
+         ↓              Architecture documented
+┌─────────────────┐     Stakeholder alignment confirmed
 │ Implementation  │     Research completed
 └────────┬────────┘
          ↓
@@ -208,7 +209,7 @@ memory/
 
 - **Persistent Context**: Never lose track of project state
 - **Decision History**: Understand why choices were made
-- **Constitutional Enforcement**: Principles that can't be violated
+- **SDD Enforcement**: Universal principles for any software project
 
 ### 🔍 [NEEDS CLARIFICATION] Markers
 
@@ -528,6 +529,45 @@ pytest tests/
 - **[GitHub Repository](https://github.com/specpulse/specpulse)** - Source code and issues
 - **Command Reference** - See AI Integration section above for full command list
 
+## 📚 Usage Guide
+
+### How to Break Your Project into Features (Pulses)
+
+A complete guide is available in **[SPECPULSE_USAGE_GUIDE.md](SPECPULSE_USAGE_GUIDE.md)** which covers:
+- Feature decomposition strategies
+- Sizing guidelines (3-15 tasks per pulse)
+- Naming conventions (001-feature-name format)
+- Real-world examples for different project types
+- Best practices for feature boundaries
+
+#### Quick Examples
+
+**E-Commerce Platform:**
+```
+001-user-authentication    # Registration, login, sessions
+002-product-catalog        # Products, categories, search
+003-shopping-cart          # Cart management, calculations
+004-payment-processing     # Gateway, transactions, receipts
+005-order-management       # History, tracking, refunds
+```
+
+**SaaS Application:**
+```
+001-tenant-management      # Multi-tenancy, workspaces
+002-subscription-billing   # Plans, payments, invoices
+003-api-management        # Keys, rate limiting, docs
+004-admin-dashboard       # Analytics, reports, settings
+005-webhook-system        # Events, notifications, logs
+```
+
+**Key Principles:**
+- Each pulse should be **independent** and **testable**
+- Size appropriately for your project type
+- Use **sequential numbering** (001, 002, 003...)
+- Follow the **9 universal SDD principles**
+
+See the full guide for detailed breakdowns and strategies.
+
 ## 📄 License
 
 MIT License - see [LICENSE](LICENSE) file for details.

{specpulse-1.3.2 → specpulse-1.4.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "specpulse"
-version = "1.3.2"
+version = "1.4.0"
 description = "Specification-Driven Development Framework"
 readme = "README.md"
 requires-python = ">=3.11"
@@ -45,6 +45,7 @@ dependencies = [
     "jinja2>=3.0",
     "gitpython>=3.1",
     "toml>=0.10",
+    "packaging>=21.0",
 ]
 
 [project.optional-dependencies]

{specpulse-1.3.2 → specpulse-1.4.0}/requirements.txt

@@ -3,4 +3,5 @@ click>=8.0
 rich>=13.0
 jinja2>=3.0
 gitpython>=3.1
-toml>=0.10
+toml>=0.10
+packaging>=21.0

{specpulse-1.3.2 → specpulse-1.4.0}/setup.py

@@ -11,7 +11,7 @@ long_description = (this_directory / "README.md").read_text(encoding="utf-8")
 
 setup(
     name="specpulse",
-    version="1.3.2",
+    version="1.3.4",
     author="SpecPulse",
     author_email="",
     description="Next-Generation Specification-Driven Development Framework",

{specpulse-1.3.2 → specpulse-1.4.0}/specpulse/__init__.py

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

{specpulse-1.3.2 → specpulse-1.4.0}/specpulse/cli/main.py

@@ -17,6 +17,7 @@ from ..core.specpulse import SpecPulse
 from ..core.validator import Validator
 from ..utils.console import Console
 from ..utils.git_utils import GitUtils
+from ..utils.version_check import check_pypi_version, compare_versions, get_update_message, should_check_version
 
 
 class SpecPulseCLI:
@@ -24,7 +25,32 @@ class SpecPulseCLI:
         self.console = Console(no_color=no_color, verbose=verbose)
         self.specpulse = SpecPulse()
         self.validator = Validator()
-        
+
+        # Check for updates (non-blocking)
+        self._check_for_updates()
+
+    def _check_for_updates(self):
+        """Check for available updates on PyPI"""
+        try:
+            if not should_check_version():
+                return
+
+            latest = check_pypi_version(timeout=1)
+            if latest:
+                current = __version__
+                is_outdated, is_major = compare_versions(current, latest)
+
+                if is_outdated:
+                    message, color = get_update_message(current, latest, is_major)
+                    # Only show for init command or when verbose
+                    # Don't spam on every command
+                    import sys
+                    if len(sys.argv) > 1 and sys.argv[1] in ['init', '--version']:
+                        self.console.info(message, style=color)
+        except:
+            # Never fail due to version check
+            pass
+
     def init(self, project_name: Optional[str] = None, 
              here: bool = False, 
              ai: str = "claude",
@@ -67,10 +93,11 @@ class SpecPulseCLI:
             ".gemini/commands",
             "memory",
             "specs",
-            "plans", 
+            "plans",
             "tasks",
             "scripts",
-            "templates"
+            "templates",
+            "templates/decomposition"
         ]
         
         # Create directories with progress bar
@@ -198,7 +225,17 @@ class SpecPulseCLI:
         task_template = self.specpulse.get_task_template()
         with open(templates_dir / "task.md", 'w', encoding='utf-8') as f:
             f.write(task_template)
-        
+
+        # Copy decomposition templates
+        decomp_dir = templates_dir / "decomposition"
+        decomp_dir.mkdir(parents=True, exist_ok=True)
+
+        resources_decomp_dir = self.specpulse.resources_dir / "templates" / "decomposition"
+        if resources_decomp_dir.exists():
+            for template_file in resources_decomp_dir.iterdir():
+                if template_file.is_file():
+                    shutil.copy2(template_file, decomp_dir / template_file.name)
+
         self.console.success("Created templates")
     
     def _create_memory_files(self, project_path: Path):
@@ -228,20 +265,20 @@ class SpecPulseCLI:
         resources_scripts_dir = self.specpulse.resources_dir / "scripts"
         
         # Copy all script files from resources
-        script_extensions = [".sh", ".py"]
+        script_extensions = [".sh", ".ps1", ".py"]
         scripts_copied = 0
-        
+
         for script_file in resources_scripts_dir.iterdir():
             if script_file.suffix in script_extensions:
                 dest_path = scripts_dir / script_file.name
                 shutil.copy2(script_file, dest_path)
-                
+
                 # Make shell scripts executable
-                if script_file.suffix == ".sh":
+                if script_file.suffix in [".sh", ".ps1"]:
                     try:
                         os.chmod(dest_path, 0o755)
                     except:
-                        pass  # Windows may not support chmod
+                        pass  # Windows may not support chmod for .sh files
                 
                 scripts_copied += 1
         

{specpulse-1.3.2 → specpulse-1.4.0}/specpulse/core/specpulse.py

@@ -41,7 +41,7 @@ class SpecPulse:
     
     def get_spec_template(self) -> str:
         """Get specification template from file"""
-        template_path = self.resources_dir / "templates" / "spec-001.md"
+        template_path = self.resources_dir / "templates" / "spec.md"
         if template_path.exists():
             with open(template_path, 'r', encoding='utf-8') as f:
                 return f.read()
@@ -125,7 +125,7 @@ FR-001: [Requirement]
     
     def get_plan_template(self) -> str:
         """Get implementation plan template from file"""
-        template_path = self.resources_dir / "templates" / "plan-001.md"
+        template_path = self.resources_dir / "templates" / "plan.md"
         if template_path.exists():
             with open(template_path, 'r', encoding='utf-8') as f:
                 return f.read()
@@ -294,14 +294,14 @@ indexes:
 - Performance Benchmarks
 - Security Scenarios
 
-## Constitution Compliance
+## SDD Compliance
 
 ### Principle Validation
-- [ ] Single Responsibility: Each component has one purpose
-- [ ] Test-First: Tests written before implementation
-- [ ] Documentation: All code is documented
-- [ ] Security: Security considered by design
-- [ ] Performance: Meets performance targets
+- [ ] Specification First: Requirements clearly defined
+- [ ] Incremental Planning: Phased approach planned
+- [ ] Task Decomposition: Broken into executable tasks
+- [ ] Quality Assurance: Appropriate testing strategy
+- [ ] Architecture Documentation: Decisions recorded
 
 ## Risk Assessment
 
@@ -317,7 +317,7 @@ indexes:
 
 ## Success Criteria
 - [ ] All functional requirements implemented
-- [ ] Test coverage > 80%
+- [ ] Appropriate test coverage for project type
 - [ ] Performance targets met
 - [ ] Security audit passed
 - [ ] Documentation complete
@@ -419,79 +419,9 @@ metrics:
         if template_path.exists():
             with open(template_path, 'r', encoding='utf-8') as f:
                 return f.read()
-        # Fallback to embedded template if file not found
-        return """# Project Constitution
-
-## Immutable Principles
-
-### Principle 1: Simplicity First
-Every solution must start with the simplest approach that could work.
-Complexity is added only when proven necessary.
-
-### Principle 2: Test-Driven Development
-No production code without tests.
-Tests are written first, implementation follows.
-
-### Principle 3: Single Responsibility
-Each module, function, and component does one thing well.
-If you need "and" to describe it, split it.
-
-### Principle 4: Documentation as Code
-Documentation lives with code.
-If it's not documented, it doesn't exist.
-
-### Principle 5: Security by Design
-Security is not an afterthought.
-Every feature considers security implications from the start.
-
-## Technical Standards
-
-### Code Style
-- Python: PEP 8 with type hints
-- JavaScript: StandardJS
-- Go: Official Go formatting
-
-### Testing Requirements
-- Minimum 80% code coverage
-- All API endpoints must have contract tests
-- Critical paths require E2E tests
-
-### Performance Targets
-- API response time: < 200ms (p95)
-- Page load time: < 2 seconds
-- Database queries: < 50ms
-
-### Security Requirements
-- All data encrypted in transit (TLS 1.3+)
-- Sensitive data encrypted at rest
-- Authentication: OAuth 2.0 / JWT
-- Authorization: RBAC with least privilege
-
-## Architecture Rules
-
-### Service Boundaries
-- Services communicate only through defined APIs
-- No shared databases between services
-- Each service owns its data
-
-### Data Management
-- Single source of truth for each data type
-- Event sourcing for audit requirements
-- CQRS where read/write patterns differ
-
-### Error Handling
-- All errors are handled explicitly
-- User-facing errors are helpful and actionable
-- System errors are logged with context
-
-## Amendment Process
-
-Changes to this constitution require:
-1. Documented rationale
-2. Team consensus
-3. Gradual migration plan
-4. Update to all affected documentation
-"""
+        # Fallback - return empty if template not found
+        # Templates should always be loaded from resources/memory/constitution.md
+        return ""
     
     def get_context_template(self) -> str:
         """Get context template from file"""
@@ -915,20 +845,24 @@ Validates specifications, plans, or project.
 4. Plan approved → Use `/sp-task breakdown`
 5. Before implementation → Use `/validate all`
 
-## Constitution Rules
+## SDD Principles
 
-Always enforce these principles:
-1. Simplicity first
-2. Test-driven development
-3. Single responsibility
-4. Documentation as code
-5. Security by design
+Follow these universal principles:
+1. Specification First
+2. Incremental Planning
+3. Task Decomposition
+4. Traceable Implementation
+5. Continuous Validation
+6. Quality Assurance
+7. Architecture Documentation
+8. Iterative Refinement
+9. Stakeholder Alignment
 
 ## Context Management
 
 - Read `memory/context.md` for project state
 - Update context after major decisions
-- Check `memory/constitution.md` for principles
+- Check `memory/constitution.md` for SDD principles
 - Reference previous specs for consistency
 
 ## Templates