⚡ EXECUTION INSTRUCTIONS FOR CLAUDE

When this command is invoked, YOU (Claude) must execute these steps immediately: This is NOT documentation - these are COMMANDS to execute right now. Use TodoWrite to track progress through multi-phase workflows.

🚨 EXECUTION WORKFLOW

Phase 1: Template Selection

Action Steps: Load appropriate Spec Kit template from .claude/templates/spec-kit/

Phase 2: Feature Analysis

Action Steps: Using Spec Kit methodology:

1. Parse user description from input arguments
2. Extract key concepts: actors, actions, data, constraints
3. Identify ambiguities: Mark with [NEEDS CLARIFICATION: specific question]
4. Focus on WHAT/WHY: Avoid HOW/technical implementation details

Phase 3: Structured Generation

Action Steps: Generate specification using Spec Kit template structure:

1. Feature Branch: Auto-generate branch name
2. Execution Flow: Step-by-step validation logic
3. User Scenarios: Testable user flows
4. Functional Requirements: Each requirement must be testable
5. Acceptance Criteria: Concrete validation steps

Phase 4: Anti-Mock Validation Integration

Action Steps: Apply enhanced Genesis validation:

1. Mark ambiguous requirements as [NEEDS CLARIFICATION]
2. Ensure all requirements are testable and unambiguous
3. Validate against anti-mock patterns from Genesis success criteria
4. Cross-reference with existing codebase to prevent fabricated API references

Phase 5: Integration with Genesis

Action Steps:

1. Save specification to appropriate goals/ directory
2. Format compatible with Genesis goal loading system
3. Maintain Genesis directory structure and naming conventions

Phase 6: 🔗 WORKFLOW INTEGRATION

Action Steps: Compatible with existing commands:

1. /plan - Our context-aware planning (unchanged)
2. /gene - Genesis will use improved specifications
3. /consensus - Multi-agent validation includes Spec Kit criteria
4. Memory MCP - Spec patterns stored for reuse

Enhanced Genesis Goals:

goals/2025-09-24-feature-name/
├── 00-spec-kit-specification.md    # Generated by /spec command
├── 01-success-criteria.md          # Enhanced with Spec Kit acceptance criteria
├── 02-progress-tracking.md         # Existing Genesis tracking
└── tests/                          # Auto-generated validation tests

📋 REFERENCE DOCUMENTATION

Spec Command - GitHub Spec Kit Integration

Purpose: Create structured specifications using GitHub Spec Kit methodology without conflicts

Usage: /spec [feature-description] - Generate Spec Kit compliant specifications

🎯 CONFLICT-FREE DESIGN

✅ No Installation Required: Uses extracted templates, no CLI tool conflicts ✅ Preserves /plan Command: Our sophisticated 171-line /plan command remains untouched ✅ Compatible Integration: Enhances Genesis workflow without disruption

🚀 EXECUTION PROTOCOL

🚨 KEY ADVANTAGES

1. Prevents Fake Code: Systematic specification validation prevents mock implementations
2. Preserves Workflow: Enhances rather than replaces existing commands
3. No Dependencies: Template-based approach, no external tools
4. Genesis Compatible: Direct integration with our goal directory system

Example Usage

/spec implement user authentication system with OAuth2 support

Generates: Structured specification with:

• Clear user scenarios
• Testable requirements
• Ambiguity markers
• Integration with Genesis validation
• No technical implementation details (WHAT/WHY only)

Implementation Details

Template Location: .claude/templates/spec-kit/spec-template.md Output Location: goals/[date-feature]/00-spec-kit-specification.md Genesis Integration: Automatic loading by Genesis goal directory system Validation: Anti-mock patterns + Spec Kit acceptance criteria