add-spec

Add Spec to Existing Folder

Adds an implementation spec (feature/bug/issue) to an existing spec folder that contains a PRD. Routes to the appropriate generate command with context.

Variables

• $param1: $1 (required) - 10-digit spec ID of existing folder (e.g., 2511131522)

Instructions

• IMPORTANT: This is a ROUTER command - it does NOT generate specs itself
• IMPORTANT: Read the appropriate generate command instructions and follow them exactly
• This command adds a spec to a folder that already has a PRD (or empty folder)
• Auto-detects spec type from conversation context (feature/bug/issue)
• References existing PRD content if available for better accuracy
• Routes to: generate-feature-spec, generate-bug-spec, or generate-issue-spec

Workflow

1. Validate Spec ID:

   • Verify $param1 is a 10-digit number matching format YYMMDDHHmm
   • If invalid format: Show error and exit
   • Example valid: 2511131522
   • Example invalid: 123 (too short), abc (not numeric)

2. Read Index and Verify Folder:

   • Read .agent/specs/index.json
   • Look up entry with key matching $param1
   • If not found: Show error listing available spec IDs and exit
   • Extract folder path from entry
   • Verify folder exists at .agent/specs/{folder}
   • If folder doesn't exist: Show error and exit

3. Check for Existing Spec:

   • Check if entry has path field in index.json
   • If path field exists and points to spec.md: Show error "Spec already exists at {path}" and exit
   • This prevents overwriting existing specs

4. Read Existing PRD (if present):

   • Check if prd.md exists in folder
   • If exists: Read prd.md content to use as additional context
   • If not: Continue without PRD context

5. Detect Spec Type:

   • Analyze conversation history and PRD content (if available)
   • Determine if this is a:
     • feature: New functionality, enhancement, or major change
     • bug: Fixing broken behavior, errors, or unexpected results
     • issue: Small task, minor fix, or simple change