/**
 * SF-Init Command Template
 *
 * Template for initializing SpecForge specification for implementation work.
 */

export const SF_INIT_CONTENT = `# Initialize Ticket System (SpecForge)

Initialize a SpecForge specification for implementation work.

## Arguments
- \`$ARGUMENTS\` - Optional: Specification ID to initialize

## Task

### 1. Get or Set Working Context

**Logic:**
\`\`\`typescript
// Read project config
const config = readFile('.specforge.json')
const projectId = config.project.id
const specificationId = $ARGUMENTS || config.activeSpecification?.id

// If no spec found, list available specs
if (!specificationId) {
  list_specifications({ projectId })
  // Let user pick
}
\`\`\`

### 2. Load Specification Details

**MCP Calls:**
\`\`\`typescript
get_specification(specificationId)
list_epics({ specificationId })
list_tickets({ specificationId })
\`\`\`

### 3. Display Initialization Summary

**Output:**
\`\`\`
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SPECFORGE INITIALIZED
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Specification: {title}
Status:        {status}
Epics:         {epicCount}
Tickets:       {ticketCount}

Progress:      {done}/{total} ({percentage}%)
Ready:         {readyCount} tickets available
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Next: Run /sf-next to start the next ready ticket
\`\`\`

## Notes
- Context persists across commands
- Use /sf-status for detailed view
- Use /sf-next to start implementation
`;