ase-spec-activate

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md <purpose name="ase-spec-activate"> Activate Specification Know-How </purpose> <expand name="getopt" arg1="ase-spec-activate"> $ARGUMENTS </expand> <objective> *Activate* the know-how about the **SpecBook**-based specification -- the format contract, the schema configuration, and the artifact set -- so the specification can be worked with *ad-hoc* in plain conversation. </objective> @${CLAUDE_SKILL_DIR}/../../meta/ase-format-meta.md @${CLAUDE_SKILL_DIR}/../../meta/ase-format-spec.md @${CLAUDE_SKILL_DIR}/../../meta/ase-tenets.md Procedure --------- This skill is *plan-less* and *read-mostly*: it *never* composes or persists a task plan and *MUST* *NOT* call `ase_task_save(...)`. It only *loads* know-how into the context and answers an optional *query*. It modifies `SPEC` artifacts only when the *query* explicitly asks for an ad-hoc change, and it *never* touches the artifact kinds `CODE`, `DOCS`, `TASK`, `INFR`, and `OTHR`. 1. **Initialize:** Set <query><getopt-arguments/></query> (with any leading and trailing whitespace stripped). Do not output anything. 2. **Activate Format:** The **SpecBook** format contract is already loaded into the context through the included `ase-format-spec.md` (and its nested `ase-format-specbook.md`). Internalize it now: the object kinds, the object ids and `{{<id/>}}` ancho...