grimoire-construct-update

[Required Reading]

1. Read ${CLAUDE_PLUGIN_ROOT}/GRIMOIRE-CONVENTIONS.md. The sections that apply to this skill are: § Construct (the single source of truth for the construct artifact — definition, folder layout, CONSTRUCT.md format, writer contract, and the Alteration rules subsection that governs every in-place change), § .grimoire/ layout (the constructs/ folder structure), § Sub-agent spawning (research for add/edit operations runs in sub-agents; the orchestrator stays lucid and owns the interview, resolution, and writes), § Skill composition, § Commits (the docs(grimoire): update construct <name> commit), § User-facing language, § Pause-point pattern (the resolution hard-stop, the locked-[specced] refusal, the clarifying-questions / operation-selection pause, and the draft-review pause), § Project context (read PROJECT.md; never write it), and § IDE-aware review (the draft surface). Not applicable: § TDD, § Historic, and the Spec → Plan → Execute page lifecycle do not apply — this skill is orthogonal (same family as grimoire-init / grimoire-note / grimoire-construct) and is the construct analog of grimoire-note: it writes no page, no SPEC.md, and no HISTORIC.md entry. Do not restate any § Construct / Alteration rule in this body — reference it.
2. If .grimoire/PROJECT.md exists in the project root, read it for project context. If it does not exist, proceed without it and, at the end of the run, give the non-blocking reminder to run grimoire-init once (per § Project context).
3. If .grimoire/HISTORIC.md exists, read it read-only for recent-page recency context. Absence is non-blocking — this skill does not write or depend on HISTORIC.md.

[Objective] Alter an existing construct in place per the § Construct Alteration rules: add, remove, or reorder references in the [pending] tail, refine a [pending] reference's detail, rewrite the construct intro/objective, or rename the construct (preserving NNN). The construct is the roadmap-of-record; this skill keeps it accurate without ever spawning a page or disturbing the work already specced.

User's target + requested alteration:

$ARGUMENTS

[Hard constraints — orthogonal skill]

• Never write to .grimoire/HISTORIC.md. Never write to .grimoire/PROJECT.md. Never create a page folder under .grimoire/pages/.
• Never create a construct — bringing a construct into existence belongs to grimoire-construct. This skill only alters one that already exists, and hard-stops otherwise (see Phase 1).
• The [specced] prefix is immutable and the construct stays flat and self-contained — these are the § Construct Alteration rules and self-containment guarantees; do not restate them here, enforce them.

[Phase 1: Target Resolution & Precondition Check (HARD STOP)] Resolve the user's input to an existing .grimoire/constructs/NNN-<name>/ folder — by the NNN number or by the <name>. List .grimoire/constructs/ and match. If the target does not exist, STOP immediately, creating or changing nothing, with the canonical message from § Pause-point pattern:

❌ Construct NNN does not exist. Run /grimoire-construct first.

Do not offer to run grimoire-construct automatically; do not create the folder. Once resolved, read CONSTRUCT.md and identify the locked [specced] prefix (the leading 1..k references, lowest-numbered) versus the [pending] tail (k+1..n). Every alteration in the following phases is confined to that pending tail (or to construct-level metadata), per § Construct Alteration rules.

[Phase 2: Research (conditional)] For add/edit operations that need codebase or external grounding (e.g. a new reference whose shape depends on how the project is structured, or a refined detail that must reflect an established external convention), spawn research sub-agent(s) per § Sub-agent spawning so the orchestrator's context stays lucid. Equip each sub-agent with Read, Grep, Glob, read-only Bash, and — when the alteration's shape depends on facts outside the repo — WebSearch / WebFetch. The sub-agent returns its findings plus an explicit list of anything it was uncertain about (these become questions for Phase 3). For pure structural operations (remove, reorder, rename) that need no grounding, skip this phase — do not spawn a sub-agent gratuitously.