specpulse 1.3.3__py3-none-any.whl → 1.4.0__py3-none-any.whl

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

@@ -11,7 +11,7 @@ allowed_tools:
 
 # /sp-pulse Command
 
-Initialize a new feature following SpecPulse methodology with constitutional compliance.
+Initialize a new feature following SpecPulse methodology with SDD compliance.
 
 ## CRITICAL SECURITY NOTE
 **NEVER edit files in these protected directories:**
@@ -53,17 +53,17 @@ When called with `/sp-pulse $ARGUMENTS`, I will:
 
 5. **Validate structure** and report comprehensive status
 
-## Constitutional Compliance
+## SDD Compliance
 
-**Article I: Simplicity**
+**Principle 1: Specification First**
 - [ ] Feature name is clear and specific
-- [ ] No unnecessary abstractions in initial structure
-- [ ] Single responsibility per feature
+- [ ] Ready for requirements documentation
+- [ ] Structure supports specifications
 
-**Article II: Anti-Abstraction**  
-- [ ] Direct template usage (no wrapper layers)
-- [ ] Minimal initial structure
-- [ ] Framework-ready files
+**Principle 2: Incremental Planning**
+- [ ] Initial structure supports phased development
+- [ ] Templates ready for iterative work
+- [ ] Supports any project type
 
 ## Example
 ```
@@ -100,7 +100,7 @@ The `/sp-pulse` command creates the feature structure and then guides you throug
 1. **Phase -1**: **MANUAL** - Use `/sp-spec` to create specification with AI assistance
 2. **Phase 0**: **MANUAL** - Use `/sp-plan` to generate implementation plan  
 3. **Phase 1**: **MANUAL** - Use `/sp-task` to create task breakdown
-4. **Implementation**: Begin development following constitutional principles
+4. **Implementation**: Begin development following SDD principles
 
 ## Context Detection
 

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

@@ -85,7 +85,7 @@ When called with `/sp-spec $ARGUMENTS`, I will:
      ```
    - Count `[NEEDS CLARIFICATION]` markers
    - Verify acceptance criteria follow Given-When-Then format
-   - Check constitutional compliance indicators
+   - Check SDD compliance indicators
    - Report detailed validation results
 
 6. **For `/sp-spec clarify`:**
@@ -105,7 +105,7 @@ User: /sp-spec create user authentication system with OAuth2 and JWT tokens
 ```
 I will create a comprehensive specification using AI-optimized templates with:
 - Jinja2-style variables for AI processing
-- Constitutional compliance sections
+- SDD compliance sections
 - Testable acceptance criteria
 - Automated validation
 
@@ -137,23 +137,28 @@ I will systematically address all [NEEDS CLARIFICATION] markers.
 
 The AI-optimized specification template includes:
 - **Metadata**: Template variables for AI processing
-- **Constitutional Gates**: Pre-implementation validation
+- **SDD Gates**: Pre-implementation validation
 - **Functional Requirements**: Structured Must/Should/Could/Won't
 - **User Stories**: Given-When-Then acceptance criteria
 - **Validation Checklist**: Automated completeness checks
 - **Integration Points**: AI command workflow guidance
 
-## Constitutional Compliance
+## SDD Compliance
 
-**Article III: Test-First**
-- [ ] Acceptance criteria written before implementation
-- [ ] Test scenarios clearly defined
-- [ ] Integration points identified
+**Principle 1: Specification First**
+- [ ] Requirements clearly documented
+- [ ] Acceptance criteria defined
+- [ ] User stories included
+
+**Principle 6: Quality Assurance**
+- [ ] Test scenarios defined
+- [ ] Acceptance criteria testable
+- [ ] Quality metrics specified
 
-**Article VI: Research**
+**Principle 7: Architecture Documentation**
 - [ ] Technology choices documented
+- [ ] Integration points identified
 - [ ] Security considerations addressed
-- [ ] Performance requirements specified
 
 ## Enhanced Error Handling
 

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

@@ -81,7 +81,7 @@ When called with `/sp-task $ARGUMENTS`, I will:
         * Layer-based tasks (data, business, API)
         * Module-specific tasks
       - **Common categories**:
-        * Constitutional Gates Compliance
+        * SDD Gates Compliance
         * Critical Path identification
         * Parallel vs Sequential grouping
         * Progress Tracking configuration
@@ -120,7 +120,7 @@ When called with `/sp-task $ARGUMENTS`, I will:
    d. **Parse current tasks** from selected file with comprehensive status:
      - Total tasks, completed, pending, blocked
      - Parallel tasks identification
-     - Constitutional gates status
+     - SDD gates status
      - Completion percentage calculation
    e. **Interactive task updates**:
      - Mark tasks as completed/in-progress/blocked
@@ -137,20 +137,20 @@ When called with `/sp-task $ARGUMENTS`, I will:
      TOTAL_TASKS=25
      COMPLETED_TASKS=10
      COMPLETION_PERCENTAGE=40%
-     CONSTITUTIONAL_GATES_PENDING=2
+     SDD_GATES_PENDING=2
      ```
    d. **Display comprehensive progress**:
      - Overall completion percentage
      - Phase-by-phase progress
      - Blocker identification and resolution
      - Velocity metrics and estimates
-     - Constitutional gates compliance status
+     - SDD gates compliance status
 
 6. **For `/sp-task execute`:**
    a. **Show existing task files**: List all task-XXX.md files in current feature directory
    b. **Ask user to select**: Which task file to execute from
    c. **Ask user to specify**: Which specific task ID to execute
-   d. **Validate task readiness** using constitutional gates
+   d. **Validate task readiness** using SDD gates
    e. **Execute task** using AI assistant capabilities:
      ```markdown
      ## Task Execution: {{ TASK_ID }}
@@ -215,13 +215,13 @@ metrics:
   completion_percentage: 40%
 ```
 
-## Constitutional Gates Integration
+## SDD Gates Integration
 
-Each task breakdown includes constitutional compliance validation:
-- **Simplicity Gate**: Tasks avoid unnecessary complexity
-- **Test-First Gate**: Test tasks before implementation tasks
-- **Integration-First Gate**: Real service integration preferred
-- **Research Gate**: Technology research tasks included
+Each task breakdown includes SDD compliance validation:
+- **Specification First**: Tasks trace to specifications
+- **Task Decomposition**: Concrete, actionable tasks
+- **Quality Assurance**: Appropriate testing tasks included
+- **Traceable Implementation**: Clear linkage to requirements
 
 ## Examples
 
@@ -264,14 +264,14 @@ I will update task status and recalculate progress metrics.
 ```
 User: /sp-task status
 ```
-I will display detailed progress with constitutional gates compliance.
+I will display detailed progress with SDD gates compliance.
 
 ### Execute specific task
 ```
 User: /sp-task execute T001
 ```
 I will:
-- Validate: Constitutional gates compliance and task readiness
+- Validate: SDD gates compliance and task readiness
 - Execute: Cross-platform task execution
   ```bash
   bash scripts/sp-pulse-task.sh "$FEATURE_DIR" "execute:$TASK_ID"
@@ -283,7 +283,7 @@ I will:
 - **Script execution** with Bash
 - **AI-optimized templates** with Jinja2-style variables
 - **Script integration** for validation and execution
-- **Constitutional gates compliance** tracking
+- **SDD gates compliance** tracking
 - **Parallel task identification** and execution
 - **Comprehensive progress tracking** with YAML configuration
 - **Automatic percentage calculation** and velocity metrics
@@ -294,7 +294,7 @@ I will:
 ## Error Handling
 
 - Plan existence validation before task generation
-- Constitutional gates compliance checking
+- SDD gates compliance checking
 - Template structure validation
 - Dependency conflict detection
 - Task execution error handling with rollback

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

@@ -9,7 +9,7 @@ First, detect current feature context:
 - If no context found, ask user to specify feature or run /sp-pulse first
 
 Parse arguments to determine action:
-- If "validate": Check plan against constitution
+- If "validate": Check plan against SDD principles
 - Otherwise: Generate new plan
 
 ## For /sp-plan generate or /sp-plan:
@@ -18,11 +18,11 @@ Parse arguments to determine action:
 3. Read selected specification from @{specs/*/spec-XXX.md}
 
 4. Run Phase Gates checks:
-   - Constitutional compliance
-   - Simplicity check (≤3 modules)
-   - Test-first strategy defined
-   - Framework selection complete
-   - Research completed
+   - SDD compliance verification
+   - Architecture documentation check
+   - Quality assurance strategy defined
+   - Stakeholder alignment confirmed
+   - Incremental planning validated
 
 5. Generate plan sections:
    - Technology stack
@@ -32,9 +32,9 @@ Parse arguments to determine action:
    - Data models
    - Testing strategy
 
-6. Track complexity:
-   - If >3 modules, document justification
-   - Create simplification roadmap
+6. Track architectural decisions:
+   - Document all technology choices
+   - Record trade-offs and rationale
 
 7. Check existing plan files and create next version (plan-001.md, plan-002.md, etc.)
 8. Write plan to plans/XXX-feature/plan-XXX.md
@@ -48,17 +48,17 @@ Parse arguments to determine action:
 4. Run validation:
    - !{bash scripts/sp-pulse-plan.sh "XXX-feature"}
 5. Verify Phase Gates compliance
-6. Check complexity tracking
-7. Ensure test-first approach
+6. Check architecture documentation
+7. Ensure quality assurance strategy
 8. Validate framework choices
 9. 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
+SDD Compliance Gates must pass before implementation:
+- ✅ Specification clearly defined
+- ✅ Incremental phases planned
+- ✅ Tasks properly decomposed
+- ✅ Quality strategy appropriate
+- ✅ Architecture documented
 
 Examples:
 - /sp-plan generate