openspec-replan

OpenSpec Replan

Adaptive refinement skill for blocked or drifted changes. Proposes revised tasks or pivots.

⚠️ AskUserQuestion Guard

CRITICAL: After EVERY AskUserQuestion call, check if answers are empty/blank. Known Claude Code bug: outside Plan Mode, AskUserQuestion silently returns empty answers without showing UI.

If answers are empty: DO NOT proceed with assumptions. Instead:

1. Output: "⚠️ Questions didn't display (known Claude Code bug outside Plan Mode)."
2. Present the options as a numbered text list and ask user to reply with their choice number.
3. WAIT for user reply before continuing.

Workflow: Analyze → Propose → Confirm → Apply

flowchart LR
    A["Analyze blocker/drift"] --> B["Read context"]
    B --> C["Propose revisions"]
    C --> D{"User approval?"}
    D -->|Yes| E["Apply changes"]
    D -->|No| F["Discard"]
    E --> G["Document blocker"]

    classDef action fill:#C8E6C9,stroke:#388E3C,color:#000
    classDef gate fill:#E1BEE7,stroke:#7B1FA2,color:#000
    classDef discard fill:#FFCDD2,stroke:#D32F2F,color:#000

    class A,B,C,E,G action
    class D gate
    class F discard

Critical: Always wait for user confirmation before applying changes (ask_first trust zone).

Guardrails

Trust Zone: ask_first (all changes require human approval)

Always ask before:

• Modifying tasks.md
• Modifying proposal.md
• Archiving files
• Any scope changes

Scope deviation threshold: >20%

• If openspec-reflect reports >20% drift, suggest replan
• Show deviation calculation in proposal

Minimal change preference:

• Count affected vs unaffected tasks
• If <50% affected, revise only those tasks
• If >50% affected, consider pivot instead

Commands

replan

Revise tasks when implementation is blocked.

Input: $ARGUMENTS = change-id [blocker-description]

Workflow:

1. Read openspec/changes/{change-id}/tasks.md, proposal.md, specs
2. Identify blocker (from argument or ask user)
3. Analyze which tasks are affected
4. Minimal change preference: Revise only affected tasks, not entire list
5. Propose revised tasks with blocker context
6. Wait for user approval before applying
7. If approved: Update tasks.md with revisions
8. Document blocker as comment in tasks.md