update-plan

Update Plan from User Responses

Process user responses in the questions document and update all related planning documents accordingly.

Prerequisites

• A plan created by the planning or planning-mode skills must already exist
• For default (non-ask) mode: the plan's questions document must contain at least one question with a non-empty ### Response section
• For ask mode: the plan's questions document must contain at least one unprocessed question (with or without a response)

Argument parsing

The skill takes a single optional argument:

• If the argument is the literal string ask (case-insensitive, trimmed) → enable ask mode and locate the plan via the Phase 1 strategies below (plan is not specified separately).
• If the argument is anything else → treat it as a plan name (existing behaviour).
• If the argument is empty → no mode flag and no plan name; fall through to the Phase 1 strategies.

ask is standalone — it cannot be combined with a plan name on the same invocation. If the user needs ask mode against a specific plan in a multi-plan repo, the Phase 1 multi-plan prompt will let them choose.

Throughout the rest of this skill, ask mode refers specifically to the case where the argument was ask.

Persistence

This skill belongs to the plans skill group. A persistence implementation decides where and how plans are stored. Before locating the plan, find the setting:

R="$(git rev-parse --show-toplevel 2>/dev/null)/.ai/config.properties"; { cat "$R" ~/.ai/config.properties | grep '^persistence\.plans[[:space:]]*=[[:space:]]*[^[:space:]]'; cat "$R" ~/.ai/config.properties | grep '^persistence[[:space:]]*=[[:space:]]*[^[:space:]]'; } 2>/dev/null | head -1 | tr -d ' \t\r'

• No output: use local-ai-folder-markdown, the default for this skill group
• persistence.plans={value} or persistence={value}: use {value}. If ../planning/persistence/{value}.md does not exist, tell the user the plans skill group has no {value} implementation and use local-ai-folder-markdown