g-plan

Behavior

1. Check prerequisites

Check if docs/features/ contains any feature directories. If not, stop: "No feature found. Please run /g-prd first."

If there are multiple features, list them and ask which one to plan for. If there's only one, use it.

Check if the selected feature has a PRD.md. If not, stop: "No PRD found in docs/features/[name]/. Please run /g-prd first." Read the PRD as context — particularly the Implementation Decisions and Testing Decisions sections.

Also read CONTEXT.md at the repo root if it exists. The ## Language entries are the project's canonical vocabulary — reuse those terms (don't redefine them) and treat any ## Flagged ambiguities resolutions as load-bearing decisions when shaping the plan. If CONTEXT.md is absent (greenfield or pre-retrofit project), proceed without it; the step-4 interview may populate it.

Run this read literally on every invocation. Do not skip the read on observation that the file looks empty or header-only — the explicit read IS the spec compliance signal.

Also read any existing ADRs in docs/adr/. These represent prior architectural decisions that may apply to this feature.

Verify-and-switch to the feature branch. Before any file write, ensure the working tree is on the feature branch {feature-name}. The switch is silent — invoking the stage implies the operator's intent.

Run this block literally. Do not paraphrase, shortcut on observation ("I can see we're already on the feature branch"), or skip when the current branch appears correct. The explicit run IS the spec compliance signal.

expected="{feature-name}"   # from selected feature directory
current=$(git rev-parse --abbrev-ref HEAD)

if [ "$current" = "$expected" ]; then
  : # already on it
elif git show-ref --verify --quiet "refs/heads/$expected"; then
  git checkout "$expected"
else
  echo "feature branch '$expected' missing — run /g-prd to create it"
  exit 1
fi

If the feature branch doesn't exist, STOP without modifying any file.