g-agents

Behavior

/g-agents runs at its normal /g-run slot (between /g-tasks and /g-implement). It operates in two modes, selected automatically based on whether AGENTS.md already exists:

• First-run mode — no AGENTS.md yet, generate from scratch
• Update mode — AGENTS.md exists, diff and merge changes

AGENTS.md is a project-wide document. The only feature-scoped section is Non-Goals, which is replaced wholesale from the current feature's PRD each cycle.

---

1. Entry: feature selection and context loading

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 is in scope. If there's only one, use it.

Read the selected feature's PRD.md at docs/features/[name]/PRD.md (required — the PRD Non-Goals section is needed for update mode).

Check if the selected feature has a PLAN.md at docs/features/[name]/PLAN.md. If it doesn't, warn: "No plan found. I recommend running /g-plan first so agent config reflects actual architecture. Proceed anyway?"

Read all ADRs in docs/adr/ (extract number, title, status from each).

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.