devflow-kit 3.17.0 → 3.18.0

package/CHANGELOG.md

@@ -5,6 +5,14 @@ All notable changes to Devflow will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.18.0] - 2026-11-07
+
+### Added
+
+- **`/plan` adds a Size forecast line to the plan** ([#771](https://github.com/dean0x/devflow/issues/771)). The design artifact's Implementation Plan section ends with one plain line, `Size forecast: files a-b, added a-b, removed a-b, commits a-b`: whole-number ranges, a <= b, for the files the change writes, the added and removed diff lines (tests and docs included) and the commits `/implement` makes before review. Gate 2 and the run report show it. `/plan` copies the line only when it has this shape, else leaves it out and says so. It changes no gate, depth or level, and `/implement` does not pass it to its agents. The four `/plan` build ceilings rise by 690 bytes and the four `/implement` ceilings by 39.
+
+---
+
 ## [3.17.0] - 2026-11-06
 
 ### Added
@@ -2513,6 +2521,7 @@ devflow init
 ---
 
 [Unreleased]: https://github.com/dean0x/devflow/compare/v3.8.0...HEAD
+[3.18.0]: https://github.com/dean0x/devflow/compare/v3.17.0...v3.18.0
 [3.17.0]: https://github.com/dean0x/devflow/compare/v3.16.0...v3.17.0
 [3.16.0]: https://github.com/dean0x/devflow/compare/v3.15.0...v3.16.0
 [3.15.0]: https://github.com/dean0x/devflow/compare/v3.14.0...v3.15.0

package/dist/commands/implement.md

@@ -54,7 +54,7 @@ Set `EVIDENCE_POLICY`, `ISSUE_REQUIRED`, `APPLY_CONVENTIONS` and `REQUIRE_NON_AU
 **Plan Document Handling** (when `COMMAND_INPUT` is a path ending in `.md`):
 1. Read the plan document. From its YAML frontmatter, take `execution-strategy` and `issue`.
 2. If the frontmatter `issue` is present and is not `pending`: forward it verbatim as the setup-task `ISSUE_INPUT` (`pending` means /plan's issue step degraded or was declined — treat it as absent)
-3. Extract its Subtask Breakdown, Implementation Plan, Patterns to Follow, Known limits and Acceptance Criteria as `EXECUTION_PLAN`. Captured values override defaults from Git agent where present.
+3. Extract its Subtask Breakdown, Implementation Plan (without its Size forecast line), Patterns to Follow, Known limits and Acceptance Criteria as `EXECUTION_PLAN`. Captured values override defaults from Git agent where present.
 
 `PR_DESCRIPTION_GUIDANCE` is the full `## PR Description Guidance` section of the plan document. Any other input, empty input included, or a plan without that section, gives `(none)`.
 
@@ -206,7 +206,7 @@ A KB with no Rules section labels its entries `Rules ({section name}):` and give
 **Produces:** CODE_AGENT_OUTPUT, FILES_CHANGED
 **Requires:** TASK_ID, BASE_BRANCH, EXECUTION_PLAN
 
-Setup context is the plan document, issue body or conversation.
+Setup context is EXECUTION_PLAN, else the issue body or conversation.
 
 **Strategy Selection**:
 - If plan document provided: use `execution-strategy` from frontmatter (if absent, use the table below)

package/dist/commands/plan.md

@@ -351,7 +351,7 @@ Combine into: patterns to follow, integration points, reusable code, edge cases"
 **Produces:** PLAN_OUTPUTS
 **Requires:** IMPL_EXPLORATION_SYNTHESIS, GAP_SYNTHESIS
 
-Spawn 3 `Agent(subagent_type="Plan")` agents **in a single message**, each with implementation exploration synthesis and `GAP_SYNTHESIS`. Ask each agent for a final report of at most about 1,500 tokens: the plan itself, not a restatement of the exploration. Add this line to every Plan prompt, at every level: `Per step give its files, the callers and consumers to update, its Must lines (what has to hold) and one rung, the lowest that meets the acceptance criteria: not needed, reuse, standard library, installed dependency, one line, minimum new code. Add Known limits: accepted risks and deferred items of the whole change, each with one reason; a limit of one step goes on its Must line. Never lower or flag a trust-boundary, security, data-loss or fail-closed guard, or its test.`
+Spawn 3 `Agent(subagent_type="Plan")` agents **in a single message**, each with implementation exploration synthesis and `GAP_SYNTHESIS`. Ask each agent for a final report of at most about 1,500 tokens: the plan itself, not a restatement of the exploration. Add this line to every Plan prompt, at every level: `Per step give its files, the callers and consumers to update, its Must lines (what has to hold) and one rung, the lowest that meets the acceptance criteria: not needed, reuse, standard library, installed dependency, one line, minimum new code. Add Known limits: accepted risks and deferred items of the whole change, each with one reason; a limit of one step goes on its Must line. Never lower or flag a trust-boundary, security, data-loss or fail-closed guard, or its test.` Ask the agent that reports the steps for one plain line right after them, in the message (no bullet, bold or backticks): `Size forecast: files a-b, added a-b, removed a-b, commits a-b`, whole numbers, a <= b, for the whole change with tests and docs: files written (created, changed or deleted), diff lines added and removed, commits `/implement` makes before review. Never drop or shrink a step to fit it.
 
 | Focus | Output |
 |-------|--------|
@@ -396,7 +396,7 @@ Use AskUserQuestion to present:
 
 1. **Implementation Plan Summary**
    - Execution strategy
-   - Key implementation steps with files
+   - Key implementation steps with files, and the steps report's Size forecast line if it fits the Phase 10 shape, else its absence
    - Test strategy — the test plan as TP lines, at least one per acceptance criterion (shape below)
 
 2. **Design Review Findings**
@@ -461,7 +461,7 @@ context-risk: LOW
 Required sections, in this order, no others:
 1. **Acceptance Criteria** — testable success conditions, numbered AC-1, AC-2, ...: `ACCEPTANCE_CRITERIA` when fetched, refined by exploration + gap analysis
 2. **Subtask Breakdown** — phases with domains, dependencies and a Serves cell (the item-1 ACs it serves); only with more than one subtask
-3. **Implementation Plan** — ordered steps, each with Files, Callers and consumers to update, Must lines and Rung
+3. **Implementation Plan** — ordered steps, each with Files, Callers and consumers to update, Must lines and Rung; last, after a blank line, the one Size forecast line Gate 2 showed (the latest Plan run's), unchanged, and no other copy; none if Gate 2 showed none
 4. **Patterns to Follow** — from exploration synthesis (file:line references)
 5. **Known limits and deferrals** — accepted risks, deferred and excluded items, each with one reason
 6. **PR Description Guidance** — the block below
@@ -550,6 +550,7 @@ Display completion summary:
 - Gap analysis summary (N blocking, M should-address)
 - Design review summary (N anti-patterns found, M mitigated in plan)
 - Gate level: {GATE_LEVEL}, depth {depth from CONFIRMED_SCOPE, else normal}, with any level note
+- Size forecast line, or why it is absent
 - Suggested next step: `/implement {artifact-path}` or `/implement #{issue-number}`
 
 ## Principles

package/dist/compliance-off/commands/implement.md

@@ -55,7 +55,7 @@ When `EVIDENCE_POLICY` is `required`, record `TRACEABILITY: DEGRADED (compliance
 **Plan Document Handling** (when `COMMAND_INPUT` is a path ending in `.md`):
 1. Read the plan document. From its YAML frontmatter, take `execution-strategy` and `issue`.
 2. If the frontmatter `issue` is present and is not `pending`: forward it verbatim as the setup-task `ISSUE_INPUT` (`pending` means /plan's issue step degraded or was declined — treat it as absent)
-3. Extract its Subtask Breakdown, Implementation Plan, Patterns to Follow, Known limits and Acceptance Criteria as `EXECUTION_PLAN`. Captured values override defaults from Git agent where present.
+3. Extract its Subtask Breakdown, Implementation Plan (without its Size forecast line), Patterns to Follow, Known limits and Acceptance Criteria as `EXECUTION_PLAN`. Captured values override defaults from Git agent where present.
 
 `PR_DESCRIPTION_GUIDANCE` is the full `## PR Description Guidance` section of the plan document. Any other input, empty input included, or a plan without that section, gives `(none)`.
 
@@ -218,7 +218,7 @@ A KB with no Rules section labels its entries `Rules ({section name}):` and give
 **Produces:** CODE_AGENT_OUTPUT, FILES_CHANGED
 **Requires:** TASK_ID, BASE_BRANCH, EXECUTION_PLAN
 
-Setup context is the plan document, issue body or conversation.
+Setup context is EXECUTION_PLAN, else the issue body or conversation.
 
 **Strategy Selection**:
 - If plan document provided: use `execution-strategy` from frontmatter (if absent, use the table below)

package/dist/compliance-off/commands/plan.md

@@ -351,7 +351,7 @@ Combine into: patterns to follow, integration points, reusable code, edge cases"
 **Produces:** PLAN_OUTPUTS
 **Requires:** IMPL_EXPLORATION_SYNTHESIS, GAP_SYNTHESIS
 
-Spawn 3 `Agent(subagent_type="Plan")` agents **in a single message**, each with implementation exploration synthesis and `GAP_SYNTHESIS`. Ask each agent for a final report of at most about 1,500 tokens: the plan itself, not a restatement of the exploration. Add this line to every Plan prompt, at every level: `Per step give its files, the callers and consumers to update, its Must lines (what has to hold) and one rung, the lowest that meets the acceptance criteria: not needed, reuse, standard library, installed dependency, one line, minimum new code. Add Known limits: accepted risks and deferred items of the whole change, each with one reason; a limit of one step goes on its Must line. Never lower or flag a trust-boundary, security, data-loss or fail-closed guard, or its test.`
+Spawn 3 `Agent(subagent_type="Plan")` agents **in a single message**, each with implementation exploration synthesis and `GAP_SYNTHESIS`. Ask each agent for a final report of at most about 1,500 tokens: the plan itself, not a restatement of the exploration. Add this line to every Plan prompt, at every level: `Per step give its files, the callers and consumers to update, its Must lines (what has to hold) and one rung, the lowest that meets the acceptance criteria: not needed, reuse, standard library, installed dependency, one line, minimum new code. Add Known limits: accepted risks and deferred items of the whole change, each with one reason; a limit of one step goes on its Must line. Never lower or flag a trust-boundary, security, data-loss or fail-closed guard, or its test.` Ask the agent that reports the steps for one plain line right after them, in the message (no bullet, bold or backticks): `Size forecast: files a-b, added a-b, removed a-b, commits a-b`, whole numbers, a <= b, for the whole change with tests and docs: files written (created, changed or deleted), diff lines added and removed, commits `/implement` makes before review. Never drop or shrink a step to fit it.
 
 | Focus | Output |
 |-------|--------|
@@ -396,7 +396,7 @@ Use AskUserQuestion to present:
 
 1. **Implementation Plan Summary**
    - Execution strategy
-   - Key implementation steps with files
+   - Key implementation steps with files, and the steps report's Size forecast line if it fits the Phase 10 shape, else its absence
    - Test strategy — the test plan as TP lines, at least one per acceptance criterion (shape below)
 
 2. **Design Review Findings**
@@ -461,7 +461,7 @@ context-risk: LOW
 Required sections, in this order, no others:
 1. **Acceptance Criteria** — testable success conditions, numbered AC-1, AC-2, ...: `ACCEPTANCE_CRITERIA` when fetched, refined by exploration + gap analysis
 2. **Subtask Breakdown** — phases with domains, dependencies and a Serves cell (the item-1 ACs it serves); only with more than one subtask
-3. **Implementation Plan** — ordered steps, each with Files, Callers and consumers to update, Must lines and Rung
+3. **Implementation Plan** — ordered steps, each with Files, Callers and consumers to update, Must lines and Rung; last, after a blank line, the one Size forecast line Gate 2 showed (the latest Plan run's), unchanged, and no other copy; none if Gate 2 showed none
 4. **Patterns to Follow** — from exploration synthesis (file:line references)
 5. **Known limits and deferrals** — accepted risks, deferred and excluded items, each with one reason
 6. **PR Description Guidance** — the block below
@@ -545,6 +545,7 @@ Display completion summary:
 - Gap analysis summary (N blocking, M should-address)
 - Design review summary (N anti-patterns found, M mitigated in plan)
 - Gate level: {GATE_LEVEL}, depth {depth from CONFIRMED_SCOPE, else normal}, with any level note
+- Size forecast line, or why it is absent
 - Suggested next step: `/implement {artifact-path}` or `/implement #{issue-number}`
 
 ## Principles

package/dist/curation-compliance-off/commands/implement.md

@@ -55,7 +55,7 @@ When `EVIDENCE_POLICY` is `required`, record `TRACEABILITY: DEGRADED (compliance
 **Plan Document Handling** (when `COMMAND_INPUT` is a path ending in `.md`):
 1. Read the plan document. From its YAML frontmatter, take `execution-strategy` and `issue`.
 2. If the frontmatter `issue` is present and is not `pending`: forward it verbatim as the setup-task `ISSUE_INPUT` (`pending` means /plan's issue step degraded or was declined — treat it as absent)
-3. Extract its Subtask Breakdown, Implementation Plan, Patterns to Follow, Known limits and Acceptance Criteria as `EXECUTION_PLAN`. Captured values override defaults from Git agent where present.
+3. Extract its Subtask Breakdown, Implementation Plan (without its Size forecast line), Patterns to Follow, Known limits and Acceptance Criteria as `EXECUTION_PLAN`. Captured values override defaults from Git agent where present.
 
 `PR_DESCRIPTION_GUIDANCE` is the full `## PR Description Guidance` section of the plan document. Any other input, empty input included, or a plan without that section, gives `(none)`.
 
@@ -192,7 +192,7 @@ A KB with no Rules section labels its entries `Rules ({section name}):` and give
 **Produces:** CODE_AGENT_OUTPUT, FILES_CHANGED
 **Requires:** TASK_ID, BASE_BRANCH, EXECUTION_PLAN
 
-Setup context is the plan document, issue body or conversation.
+Setup context is EXECUTION_PLAN, else the issue body or conversation.
 
 **Strategy Selection**:
 - If plan document provided: use `execution-strategy` from frontmatter (if absent, use the table below)

package/dist/curation-compliance-off/commands/plan.md

@@ -323,7 +323,7 @@ Combine into: patterns to follow, integration points, reusable code, edge cases"
 **Produces:** PLAN_OUTPUTS
 **Requires:** IMPL_EXPLORATION_SYNTHESIS, GAP_SYNTHESIS
 
-Spawn 3 `Agent(subagent_type="Plan")` agents **in a single message**, each with implementation exploration synthesis and `GAP_SYNTHESIS`. Ask each agent for a final report of at most about 1,500 tokens: the plan itself, not a restatement of the exploration. Add this line to every Plan prompt, at every level: `Per step give its files, the callers and consumers to update, its Must lines (what has to hold) and one rung, the lowest that meets the acceptance criteria: not needed, reuse, standard library, installed dependency, one line, minimum new code. Add Known limits: accepted risks and deferred items of the whole change, each with one reason; a limit of one step goes on its Must line. Never lower or flag a trust-boundary, security, data-loss or fail-closed guard, or its test.`
+Spawn 3 `Agent(subagent_type="Plan")` agents **in a single message**, each with implementation exploration synthesis and `GAP_SYNTHESIS`. Ask each agent for a final report of at most about 1,500 tokens: the plan itself, not a restatement of the exploration. Add this line to every Plan prompt, at every level: `Per step give its files, the callers and consumers to update, its Must lines (what has to hold) and one rung, the lowest that meets the acceptance criteria: not needed, reuse, standard library, installed dependency, one line, minimum new code. Add Known limits: accepted risks and deferred items of the whole change, each with one reason; a limit of one step goes on its Must line. Never lower or flag a trust-boundary, security, data-loss or fail-closed guard, or its test.` Ask the agent that reports the steps for one plain line right after them, in the message (no bullet, bold or backticks): `Size forecast: files a-b, added a-b, removed a-b, commits a-b`, whole numbers, a <= b, for the whole change with tests and docs: files written (created, changed or deleted), diff lines added and removed, commits `/implement` makes before review. Never drop or shrink a step to fit it.
 
 | Focus | Output |
 |-------|--------|
@@ -368,7 +368,7 @@ Use AskUserQuestion to present:
 
 1. **Implementation Plan Summary**
    - Execution strategy
-   - Key implementation steps with files
+   - Key implementation steps with files, and the steps report's Size forecast line if it fits the Phase 10 shape, else its absence
    - Test strategy — the test plan as TP lines, at least one per acceptance criterion (shape below)
 
 2. **Design Review Findings**
@@ -433,7 +433,7 @@ context-risk: LOW
 Required sections, in this order, no others:
 1. **Acceptance Criteria** — testable success conditions, numbered AC-1, AC-2, ...: `ACCEPTANCE_CRITERIA` when fetched, refined by exploration + gap analysis
 2. **Subtask Breakdown** — phases with domains, dependencies and a Serves cell (the item-1 ACs it serves); only with more than one subtask
-3. **Implementation Plan** — ordered steps, each with Files, Callers and consumers to update, Must lines and Rung
+3. **Implementation Plan** — ordered steps, each with Files, Callers and consumers to update, Must lines and Rung; last, after a blank line, the one Size forecast line Gate 2 showed (the latest Plan run's), unchanged, and no other copy; none if Gate 2 showed none
 4. **Patterns to Follow** — from exploration synthesis (file:line references)
 5. **Known limits and deferrals** — accepted risks, deferred and excluded items, each with one reason
 6. **PR Description Guidance** — the block below
@@ -517,6 +517,7 @@ Display completion summary:
 - Gap analysis summary (N blocking, M should-address)
 - Design review summary (N anti-patterns found, M mitigated in plan)
 - Gate level: {GATE_LEVEL}, depth {depth from CONFIRMED_SCOPE, else normal}, with any level note
+- Size forecast line, or why it is absent
 - Suggested next step: `/implement {artifact-path}` or `/implement #{issue-number}`
 
 ## Principles

package/dist/curation-off/commands/implement.md

@@ -54,7 +54,7 @@ Set `EVIDENCE_POLICY`, `ISSUE_REQUIRED`, `APPLY_CONVENTIONS` and `REQUIRE_NON_AU
 **Plan Document Handling** (when `COMMAND_INPUT` is a path ending in `.md`):
 1. Read the plan document. From its YAML frontmatter, take `execution-strategy` and `issue`.
 2. If the frontmatter `issue` is present and is not `pending`: forward it verbatim as the setup-task `ISSUE_INPUT` (`pending` means /plan's issue step degraded or was declined — treat it as absent)
-3. Extract its Subtask Breakdown, Implementation Plan, Patterns to Follow, Known limits and Acceptance Criteria as `EXECUTION_PLAN`. Captured values override defaults from Git agent where present.
+3. Extract its Subtask Breakdown, Implementation Plan (without its Size forecast line), Patterns to Follow, Known limits and Acceptance Criteria as `EXECUTION_PLAN`. Captured values override defaults from Git agent where present.
 
 `PR_DESCRIPTION_GUIDANCE` is the full `## PR Description Guidance` section of the plan document. Any other input, empty input included, or a plan without that section, gives `(none)`.
 
@@ -180,7 +180,7 @@ A KB with no Rules section labels its entries `Rules ({section name}):` and give
 **Produces:** CODE_AGENT_OUTPUT, FILES_CHANGED
 **Requires:** TASK_ID, BASE_BRANCH, EXECUTION_PLAN
 
-Setup context is the plan document, issue body or conversation.
+Setup context is EXECUTION_PLAN, else the issue body or conversation.
 
 **Strategy Selection**:
 - If plan document provided: use `execution-strategy` from frontmatter (if absent, use the table below)

package/dist/curation-off/commands/plan.md

@@ -323,7 +323,7 @@ Combine into: patterns to follow, integration points, reusable code, edge cases"
 **Produces:** PLAN_OUTPUTS
 **Requires:** IMPL_EXPLORATION_SYNTHESIS, GAP_SYNTHESIS
 
-Spawn 3 `Agent(subagent_type="Plan")` agents **in a single message**, each with implementation exploration synthesis and `GAP_SYNTHESIS`. Ask each agent for a final report of at most about 1,500 tokens: the plan itself, not a restatement of the exploration. Add this line to every Plan prompt, at every level: `Per step give its files, the callers and consumers to update, its Must lines (what has to hold) and one rung, the lowest that meets the acceptance criteria: not needed, reuse, standard library, installed dependency, one line, minimum new code. Add Known limits: accepted risks and deferred items of the whole change, each with one reason; a limit of one step goes on its Must line. Never lower or flag a trust-boundary, security, data-loss or fail-closed guard, or its test.`
+Spawn 3 `Agent(subagent_type="Plan")` agents **in a single message**, each with implementation exploration synthesis and `GAP_SYNTHESIS`. Ask each agent for a final report of at most about 1,500 tokens: the plan itself, not a restatement of the exploration. Add this line to every Plan prompt, at every level: `Per step give its files, the callers and consumers to update, its Must lines (what has to hold) and one rung, the lowest that meets the acceptance criteria: not needed, reuse, standard library, installed dependency, one line, minimum new code. Add Known limits: accepted risks and deferred items of the whole change, each with one reason; a limit of one step goes on its Must line. Never lower or flag a trust-boundary, security, data-loss or fail-closed guard, or its test.` Ask the agent that reports the steps for one plain line right after them, in the message (no bullet, bold or backticks): `Size forecast: files a-b, added a-b, removed a-b, commits a-b`, whole numbers, a <= b, for the whole change with tests and docs: files written (created, changed or deleted), diff lines added and removed, commits `/implement` makes before review. Never drop or shrink a step to fit it.
 
 | Focus | Output |
 |-------|--------|
@@ -368,7 +368,7 @@ Use AskUserQuestion to present:
 
 1. **Implementation Plan Summary**
    - Execution strategy
-   - Key implementation steps with files
+   - Key implementation steps with files, and the steps report's Size forecast line if it fits the Phase 10 shape, else its absence
    - Test strategy — the test plan as TP lines, at least one per acceptance criterion (shape below)
 
 2. **Design Review Findings**
@@ -433,7 +433,7 @@ context-risk: LOW
 Required sections, in this order, no others:
 1. **Acceptance Criteria** — testable success conditions, numbered AC-1, AC-2, ...: `ACCEPTANCE_CRITERIA` when fetched, refined by exploration + gap analysis
 2. **Subtask Breakdown** — phases with domains, dependencies and a Serves cell (the item-1 ACs it serves); only with more than one subtask
-3. **Implementation Plan** — ordered steps, each with Files, Callers and consumers to update, Must lines and Rung
+3. **Implementation Plan** — ordered steps, each with Files, Callers and consumers to update, Must lines and Rung; last, after a blank line, the one Size forecast line Gate 2 showed (the latest Plan run's), unchanged, and no other copy; none if Gate 2 showed none
 4. **Patterns to Follow** — from exploration synthesis (file:line references)
 5. **Known limits and deferrals** — accepted risks, deferred and excluded items, each with one reason
 6. **PR Description Guidance** — the block below
@@ -522,6 +522,7 @@ Display completion summary:
 - Gap analysis summary (N blocking, M should-address)
 - Design review summary (N anti-patterns found, M mitigated in plan)
 - Gate level: {GATE_LEVEL}, depth {depth from CONFIRMED_SCOPE, else normal}, with any level note
+- Size forecast line, or why it is absent
 - Suggested next step: `/implement {artifact-path}` or `/implement #{issue-number}`
 
 ## Principles

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devflow-kit",
-  "version": "3.17.0",
+  "version": "3.18.0",
   "description": "A meta-harness for Claude Code — turns a single coding agent into an engineering team: orchestration, parallel review, persistent memory and curated decisions",
   "type": "module",
   "bin": {

package/src/assets/commands/implement.mds

@@ -59,7 +59,7 @@ When `EVIDENCE_POLICY` is `required`, record `TRACEABILITY: DEGRADED (compliance
 **Plan Document Handling** (when `COMMAND_INPUT` is a path ending in `.md`):
 1. Read the plan document. From its YAML frontmatter, take `execution-strategy` and `issue`.
 2. If the frontmatter `issue` is present and is not `pending`: forward it verbatim as the setup-task `ISSUE_INPUT` (`pending` means /plan's issue step degraded or was declined — treat it as absent)
-3. Extract its Subtask Breakdown, Implementation Plan, Patterns to Follow, Known limits and Acceptance Criteria as `EXECUTION_PLAN`. Captured values override defaults from Git agent where present.
+3. Extract its Subtask Breakdown, Implementation Plan (without its Size forecast line), Patterns to Follow, Known limits and Acceptance Criteria as `EXECUTION_PLAN`. Captured values override defaults from Git agent where present.
 
 `PR_DESCRIPTION_GUIDANCE` is the full `## PR Description Guidance` section of the plan document. Any other input, empty input included, or a plan without that section, gives `(none)`.
 
@@ -197,7 +197,7 @@ Pass `DECISIONS_CONTEXT` to Code agent (Phase 2) and Harden agent (Phase 4).
 **Produces:** CODE_AGENT_OUTPUT, FILES_CHANGED
 **Requires:** TASK_ID, BASE_BRANCH, EXECUTION_PLAN
 
-Setup context is the plan document, issue body or conversation.
+Setup context is EXECUTION_PLAN, else the issue body or conversation.
 
 **Strategy Selection**:
 - If plan document provided: use `execution-strategy` from frontmatter (if absent, use the table below)

package/src/assets/commands/plan.mds

@@ -290,7 +290,7 @@ Combine into: patterns to follow, integration points, reusable code, edge cases"
 **Produces:** PLAN_OUTPUTS
 **Requires:** IMPL_EXPLORATION_SYNTHESIS, GAP_SYNTHESIS
 
-Spawn 3 `Agent(subagent_type="Plan")` agents **in a single message**, each with implementation exploration synthesis and `GAP_SYNTHESIS`. Ask each agent for a final report of at most about 1,500 tokens: the plan itself, not a restatement of the exploration. Add this line to every Plan prompt, at every level: `Per step give its files, the callers and consumers to update, its Must lines (what has to hold) and one rung, the lowest that meets the acceptance criteria: not needed, reuse, standard library, installed dependency, one line, minimum new code. Add Known limits: accepted risks and deferred items of the whole change, each with one reason; a limit of one step goes on its Must line. Never lower or flag a trust-boundary, security, data-loss or fail-closed guard, or its test.`
+Spawn 3 `Agent(subagent_type="Plan")` agents **in a single message**, each with implementation exploration synthesis and `GAP_SYNTHESIS`. Ask each agent for a final report of at most about 1,500 tokens: the plan itself, not a restatement of the exploration. Add this line to every Plan prompt, at every level: `Per step give its files, the callers and consumers to update, its Must lines (what has to hold) and one rung, the lowest that meets the acceptance criteria: not needed, reuse, standard library, installed dependency, one line, minimum new code. Add Known limits: accepted risks and deferred items of the whole change, each with one reason; a limit of one step goes on its Must line. Never lower or flag a trust-boundary, security, data-loss or fail-closed guard, or its test.` Ask the agent that reports the steps for one plain line right after them, in the message (no bullet, bold or backticks): `Size forecast: files a-b, added a-b, removed a-b, commits a-b`, whole numbers, a <= b, for the whole change with tests and docs: files written (created, changed or deleted), diff lines added and removed, commits `/implement` makes before review. Never drop or shrink a step to fit it.
 
 | Focus | Output |
 |-------|--------|
@@ -335,7 +335,7 @@ Use AskUserQuestion to present:
 
 1. **Implementation Plan Summary**
    - Execution strategy
-   - Key implementation steps with files
+   - Key implementation steps with files, and the steps report's Size forecast line if it fits the Phase 10 shape, else its absence
    - Test strategy — the test plan as TP lines, at least one per acceptance criterion (shape below)
 
 2. **Design Review Findings**
@@ -395,7 +395,7 @@ context-risk: LOW
 Required sections, in this order, no others:
 1. **Acceptance Criteria** — testable success conditions, numbered AC-1, AC-2, ...: `ACCEPTANCE_CRITERIA` when fetched, refined by exploration + gap analysis
 2. **Subtask Breakdown** — phases with domains, dependencies and a Serves cell (the item-1 ACs it serves); only with more than one subtask
-3. **Implementation Plan** — ordered steps, each with Files, Callers and consumers to update, Must lines and Rung
+3. **Implementation Plan** — ordered steps, each with Files, Callers and consumers to update, Must lines and Rung; last, after a blank line, the one Size forecast line Gate 2 showed (the latest Plan run's), unchanged, and no other copy; none if Gate 2 showed none
 4. **Patterns to Follow** — from exploration synthesis (file:line references)
 5. **Known limits and deferrals** — accepted risks, deferred and excluded items, each with one reason
 6. **PR Description Guidance** — the block below
@@ -491,6 +491,7 @@ Display completion summary:
 - Gap analysis summary (N blocking, M should-address)
 - Design review summary (N anti-patterns found, M mitigated in plan)
 - Gate level: {GATE_LEVEL}, depth {depth from CONFIRMED_SCOPE, else normal}, with any level note
+- Size forecast line, or why it is absent
 - Suggested next step: `/implement {artifact-path}` or `/implement #{issue-number}`
 
 ## Principles

package/src/assets/skills/agent-references/references/synthesize/planning.md

@@ -24,7 +24,6 @@ Each phase or subtask names the AC numbers it serves.
 ### Execution Strategy
 **Type**: {SINGLE_CODE_AGENT | SEQUENTIAL_CODE_AGENTS | PARALLEL_CODE_AGENTS}
 **Context Risk**: {LOW | MEDIUM | HIGH | CRITICAL}
-**File Estimate**: {n} files across {m} modules
 **Reason**: {why this strategy}
 
 ### Subtask Breakdown (if not SINGLE_CODE_AGENT)
@@ -39,6 +38,8 @@ Each phase or subtask names the AC numbers it serves.
 | 1 | {action} | `file` | `caller` | {what has to hold} | {lowest rung that works} | `test_file` | - |
 | 2 | {action} | `file` | `caller` | {what has to hold} | {lowest rung that works} | `test_file` | Step 1 |
 
+{the steps report's Size forecast line, unchanged; no line when it has none}
+
 ### Known limits and deferrals
 | Limit | Reason |
 |-------|--------|