frames

(Re)build the frame-set indexes of: $ARGUMENTS

design/ is a reserved subdirectory of any folder under specifications/ — a BRD folder, a PRD folder, or an Epic folder alike — and each of its immediate subdirectories is one exported frame set (${CLAUDE_PLUGIN_ROOT}/references/grounding-format.md §6.1). That section makes each set's index mandatory, and a set without one a refusal: design-grounder returns NO_INDEX rather than reading a set without one, because a filename is not a reliable statement of what a frame shows.

This command is the recovery path for that. The obvious workflow — a human exports frames and drops the folder in — produces a set nothing can read, and until this command the only way out was hand-authoring an index. /frames looks at the frames and writes the index for every set of one resolved folder.

/frames is not design grounding, and must not be mistaken for it. Indexing makes frames readable; grounding makes them [DG#n] findings. This command dispatches no design-grounder, produces no finding, cites no requirement id or [CG#n], and never reaches grounding-verifier, on either route. The one command that grounds a frame set is /prd-ground, now on both routes — the BRD route's [BR#n] inventory and the idea route's PRD-level [AC#n]/[FR#n]/[US#n] inventory.

The name. design/ and frame set are §6.1's own vocabulary, so /frames names what it acts on. It is deliberately not /design-index: /design is the engineering-design workflow, and a name adjacent to it would invite an operator who wanted an index into the wrong command.

Phase 0 — Resolve the address + model routing

1. The environment. $SPECS_PATH must resolve: every path this command reads or writes is under it. Unset or not a directory → apply the Required path environment variable unset rule in ${CLAUDE_PLUGIN_ROOT}/references/escalation-rules.md and stop there. Without this, an address that resolves by key reaches the key-resolution stop below and is told "no folder under /specifications/" — a message naming a failure that is not the failure — and an @<path> address reaches no stop at all, since the path branch resolves without consulting $SPECS_PATH (workflows-core:addressing) and the run then fails at its first write. Neither is the diagnosis the operator needs, which is why this gate is taken first. (The argument-shape stops in this same step fire either way; they never needed $SPECS_PATH, so the only reachable stop, which this sentence used to say, was wrong in both directions.)

   /frames defines no flags, and takes exactly one address. A second non-flag token, or a token beginning with --, is a stop rather than a silent discard: FRAMES_EXTRA_ARGUMENT: /frames takes one address and no flags; '<token>' is neither. It indexes the frame sets of one folder per run — re-run once per folder. A discarded second address is a folder the operator believes was indexed and was not.

2. The address (mandatory). Parse the first non-flag token and resolve it with resolve-address (${CLAUDE_PLUGIN_ROOT}/references/addressing.md §3) — a key, or @<path> to a folder or a file inside one. Pass no <KIND>: design/ is reserved at every level, so a BRD folder, a PRD folder and an Epic folder are all valid targets and narrowing the resolution would refuse two of the three. Absent or malformed → stop: FRAMES_NEEDS_ADDRESS: /frames needs the folder whose frame sets it should index — a key (^[A-Z][A-Z0-9_]*(-\d+)+$, e.g. ACME-77) or '@<path>' to the folder. Re-run '/workflows-core:frames <KEY>|@<path>'.

   Handle the resolution record exactly as it comes back:

   • status: invalid → the same stop above, naming the token that failed the grammar.
   • status: absent → stop: FRAMES_NO_FOLDER: no folder under $SPECS_PATH/specifications/ asserts key <KEY>. This command indexes an existing folder's frame sets and creates no folder. Re-run with '@<path>' to the folder, or with the key of one that exists. This command creates no folder, so absent is a stop rather than a create.
   • status: ambiguous → §3 rule 5's hard stop, naming every match and @<path> as the way through it. Never choose between them.
   • status: found → carry path, kind and key. Report legacy: true once as deprecated when §5's fallback resolved it.