spec:rename

Compatibility: If AskUserQuestion is unavailable, present options as a numbered list and wait for the user's reply. If Task is unavailable, run parallel steps sequentially. The context: fork and agent: frontmatter fields are Claude Code-specific — on OpenCode and VS Code Copilot they are ignored and the skill runs inline using the current model.

Rename a plan and update all references.

Overview

Renames a plan's directory and updates the registry. Useful for clarifying plan purpose or fixing typos in plan names.

Step 1: Select Plan

• Check for arguments: /rename old-name new-name
• If only one argument, treat as old name and prompt for new name
• If no arguments:
  • Get all plans
  • If no plans exist, report error
  • If only one plan, auto-select it
  • If multiple plans, use AskUserQuestion tool:

    question: "Which plan do you want to rename?"
    header: "Rename Plan"
    options:
      - label: "feature-auth (Active - 52%)"
        description: "Add authentication system"
      - label: "refactor-api (Paused - 33%)"
        description: "Refactor API layer"
    

Step 2: Get New Name (if not provided)

If new name wasn't provided as argument, ask user: "What should the new name be for plan '{old-name}'?"

Step 3: Validate New Name

1. Slugify the new name (lowercase, hyphens, alphanumeric)
2. Check if new name already exists
3. If collision, offer to append -2, -3, etc. or let user choose different name

Step 4: Confirm Rename

Use AskUserQuestion tool:

question: "Rename plan '{old-name}' to '{new-name}'?"
header: "Confirm Rename"
multiSelect: false
options:
  - label: "Rename plan"
    description: "Update directory name and registry, preserve all files"
  - label: "Cancel"
    description: "Keep original name"

Step 5: Perform Rename

1. Rename via CLI:

   npx @codevoyant/agent-kit plans rename --old-name "$OLD_NAME" --new-name "$NEW_NAME"
   

2. Rename directory: .codevoyant/plans/{old-name}/ → .codevoyant/plans/{new-name}/
3. Check plan.md for self-references: search for any occurrence of {old-name} as a string (e.g., in path comments or the plan title line) and update to {new-name}. This is rare but can happen when /new embeds the plan name in the description.
4. Note: Git worktrees and branches are NOT renamed — only the plan directory name changes. If plan.md metadata references a branch or worktree, those entries remain valid and do not need updating.

Step 6: Report Completion

Plan renamed successfully!

Old name: {old-name}
New name: {new-name}
Location: .codevoyant/plans/{new-name}/

Continue execution: /go {new-name}
Check status: /status {new-name}