@sabaiway/agent-workflow-engine 2.0.0 → 2.1.0

package/CHANGELOG.md

@@ -4,6 +4,22 @@ All notable changes to the methodology engine. Versions are this **package's** n
 they are distinct from the **deployment-lineage** stamp written into a project's `docs/ai/`
 (which tracks the shared `agent-workflow` lineage, head `3.0.0`).
 
+## 2.1.0 — the plan names the layout it is about to create (AD-091)
+
+The authoring canon now asks for the layout while the plan is still text: every Step that creates a
+file names that file and the single responsibility it carries — and where the project declares a
+source-size cap, the planned layout fits it.
+
+- **`procedures.md` plan-authoring, Draft (step 2)** — every Step that CREATES a file names that file
+  and the single responsibility it carries, and **where the project declares a source-size cap**, the
+  planned layout fits it. The conditional is canon, not decoration: a project that declares no
+  practice must never be handed an invented limit.
+- **`planning.md` §8 self-review checklist** — the matching line, so the draft is re-checked against
+  it before the plan is finalized. The line carries the canon's own rationale for asking at plan
+  time: "a gate that refuses an oversized file after it is written only pays for a rewrite".
+- The rung lives in **plan-authoring only** — plan-execution grows no rival copy of it. Both canon
+  pins are enforced by the existing canon suites, including the conditional form.
+
 ## 2.0.0 — strip-the-kit: the planning canon teaches the computed loop (AD-059)
 
 > ### ⚠ BREAKING — the §9 "Computed instrument" canon is rewritten

package/SKILL.md

@@ -3,7 +3,7 @@ name: agent-workflow-engine
 description: Canonical home of the agent-workflow planning methodology — the Plan→Phase→Step→Substep vocabulary, plan lifecycle, queue.md series index, mandatory Cleanup phase, the bounded methodology slot fragment, the orchestration-recipe vocabulary (Solo / Reviewed / Council / Delegated), and the activity-procedures canon (plan-authoring / plan-execution, with typed recipe slots). A published, installable npm package (available:true) that *provides* the methodology text; it mutates nothing. The composition root (agent-workflow-kit) reads this canon LIVE from the installed engine and injects the bounded slots from it — one source of truth, no bundled mirror; `npx @sabaiway/agent-workflow-kit@latest init` installs the engine.
 disable-model-invocation: true
 metadata:
-  version: '2.0.0'
+  version: '2.1.0'
 ---
 
 # agent-workflow-engine

package/capability.json

@@ -3,7 +3,7 @@
   "schema": 1,
   "name": "agent-workflow-engine",
   "kind": "methodology-engine",
-  "version": "2.0.0",
+  "version": "2.1.0",
   "available": true,
   "provides": ["plan"],
   "roles": {},

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sabaiway/agent-workflow-engine",
-  "version": "2.0.0",
+  "version": "2.1.0",
   "description": "Canonical home of the agent-workflow planning methodology — the Plan→Phase→Step vocabulary, plan lifecycle, queue.md series index, and mandatory Cleanup phase, consumed by the kit (composition root). The methodology engine of the agent-workflow family.",
   "keywords": [
     "ai-agents",

package/references/planning.md

@@ -104,6 +104,7 @@ A harness "approved — you can now start coding" prompt (e.g. Claude Code's **E
 ## 8. Self-review checklist (before finalizing a Plan)
 
 - Every Step has exact file paths and exact commands.
+- Every Step that CREATES a file names that file and its single responsibility; where the project declares a source-size cap, the planned layout fits it (no declared cap → no invented limit). Deciding the layout here is the cheap lever — a gate that refuses an oversized file after it is written only pays for a rewrite.
 - Every recommendation that used to live outside the Plan is now a Step (§5).
 - Vocabulary is strict (§1); the Plan ends with **Phase N: Cleanup** (§4).
 - If part of a series: `queue.md` is initialised / updated (§3).

package/references/procedures.md

@@ -50,9 +50,16 @@ Produce a self-contained, cold-readable plan, reviewed to the configured depth b
 
 1. **Research** — gather the exact files, contracts, and constraints the plan will touch.
 2. **Draft** — write the plan to the document structure defined in [`planning.md`](planning.md) §7,
-   with exact paths and commands per Step. Bind to that structure; do not restate it here.
+   with exact paths and commands per Step. Bind to that structure; do not restate it here. Name the
+   LAYOUT as you draft: every Step that CREATES a file names that file and the single responsibility
+   it carries, and — **when the project declares a source-size cap** (the composition root's
+   `procedures` advisor prints the declared practice; a project that declares none carries no limit
+   to invent) — the planned layout fits that cap. Scope fixed before any code exists is what keeps a
+   module small; a size gate is only the backstop.
 3. **Self-review** — run the [`planning.md`](planning.md) §8 checklist (exact paths/commands, strict
-   vocabulary, every out-of-plan recommendation folded into a Step, `queue.md` updated for a series).
+   vocabulary, every created file named with its single responsibility (fitting the declared cap
+   where there is one), every out-of-plan recommendation folded into a Step, `queue.md` updated for a
+   series).
    Apply the [`planning.md`](planning.md) §9 lens — fold by code (read and cite the `file:line`), and
    hold the right altitude.
 4. **review {recipe}** — review the draft at the depth the resolved `review` recipe selects: Solo