Problem
ea-methodologist authors packs, but the "light half" — authoring a preset (select methods across packs, group types into domains, pick settings) — was deferred in spec 14 (at archive/pre-github): "a pack composes into a manifest without a preset via the spec 04 tailoring verbs". True, but an org that wants to publish its tailoring as a reusable archetype still hand-writes the preset YAML.
Direction
Surface-only: an eliciting flow (in ea-methodologist, or its own reference file) that discovers available packs/methods at runtime via the CLI (P4 — no hardcoded vocabulary), elicits the org's shape, and drafts the preset gated by adopting it in a scratch repo. No core change expected — preset schema and adopt already exist. Must follow the Phase-28 lesson: elicit-first, no batch-authoring.
Forks
Problem
ea-methodologistauthors packs, but the "light half" — authoring a preset (select methods across packs, group types into domains, pick settings) — was deferred in spec 14 (atarchive/pre-github): "a pack composes into a manifest without a preset via the spec 04 tailoring verbs". True, but an org that wants to publish its tailoring as a reusable archetype still hand-writes the preset YAML.Direction
Surface-only: an eliciting flow (in
ea-methodologist, or its own reference file) that discovers available packs/methods at runtime via the CLI (P4 — no hardcoded vocabulary), elicits the org's shape, and drafts the preset gated by adopting it in a scratch repo. No core change expected — preset schema and adopt already exist. Must follow the Phase-28 lesson: elicit-first, no batch-authoring.Forks
ea-architect's adopt flow — but authoring a publishable preset is methodologist work, not org tailoring.pack add-type/add-rule/add-method+ preset writes #6) and design both together.