create-sprint

Create New Sprint

You are executing the /create-sprint command to create a new sprint definition with all task files.

Purpose

Create a comprehensive sprint definition by copying templates, customizing task files, and updating configuration. Each sprint represents one strategic opportunity area with 6 research tasks.

Steps to Execute

Step 1: Validate Arguments

Check $1 (sprint-number):

• Must be 2-digit format: 01-99
• Example validation: if not [0-9][0-9], ERROR

Check $2 (sprint-name):

• Must be non-empty quoted string
• Will be used for directory naming (slugified)
• Example: "operation Control Verification", "AI Pilot Assistance"

Check $3 (description):

• Must be non-empty quoted string
• Brief description of opportunity area
• Example: "Automated operation control verification for new technology sector standards"

Verify prerequisites:

• config/sprint-config.yml exists
• templates/sprint-template/ exists (from template repo)
• Sprint $1 not already defined in config

Step 2: Slugify Sprint Name

Convert $2 to URL-safe slug:

• Lowercase all characters
• Replace spaces with hyphens
• Remove special characters
• Example: "AI Pilot Assistance" → "ai-pilot-assistance"

Store as $SLUG variable.

Step 3: Create Sprint Directory

Use Bash tool:

mkdir -p sprints/$1-$SLUG
mkdir -p temp/$1-$SLUG

Step 4: Copy and Customize Task Templates

For each task file (01-06), use Read to load template, customize, and Write to sprint directory:

Task 01 - Technical & Regulatory Landscape:

# Sprint $1, Task 01: Technical & Regulatory Landscape
## $2

### Objective
Research technical requirements, regulatory standards, and compliance pathways for: $3

### Research Questions
1. What are the relevant technical standards and regulations?
2. What are current compliance requirements?
3. What verification and validation approaches exist?
4. What precedents or prior approvals are relevant?
5. What technical risks or challenges exist?
6. What documentation and testing is required?

### Expected Deliverables
- Technical standards analysis (5-7 files)
- Regulatory pathway documentation
- Compliance requirements summary
- Risk assessment
- Synthesis document

### Success Criteria
- Minimum 5 research files created
- All claims cited with authoritative sources
- Technical accuracy verified
- Regulatory pathways clearly documented