iter pr.1.3: planner Step 2 dispatches ailang-plan-recon

This commit is contained in:
2026-05-11 12:34:13 +02:00
parent d5f312c0a7
commit 0f785369ba
+28 -10
View File
@@ -59,18 +59,34 @@ iteration's worth of work onto a task list.
### Step 2 — Map file structure
Before defining tasks, list every file the iteration will create or
modify, and what each one is responsible for. This is where
decomposition decisions are locked in.
Dispatch `ailang-plan-recon` with the spec path and iteration scope.
Read the returned file-map. Lift the relevant entries into the plan's
"Files this plan creates or modifies" section; the Boss may add or
amend entries that recon missed.
Dispatch carrier:
| Field | Content |
|-------|---------|
| `spec_path` | path to the parent spec |
| `iteration_scope` | which sections of the spec this iteration covers |
| `focus_hint` | optional — subsystem or symbol to prioritise |
Recon does NOT decide decomposition. Two recon dispatches per planner
run is unusual but legitimate (e.g. one for the main spec sections,
one with a sharper `focus_hint` for a tricky subsystem). Three or
more is a smell — re-read the spec; the iteration scope is probably
too broad.
The plan's "Files this plan creates or modifies" section keeps the
same shape:
```markdown
**Files this plan creates or modifies:**
- Create: `crates/ailang-codegen/src/<new>.rs` — <one-line
responsibility>
- Modify: `crates/ailang-check/src/typeclass.rs` — adds
<responsibility>
- Test: `crates/ail/tests/e2e.rs` — adds <case>
- Create: `<exact path>` — <one-line responsibility>
- Modify: `<exact path>:<line range if known>`
- Test: `<exact path>` — <one-line case description>
```
Files that change together stay in the same task. Files that change
@@ -209,5 +225,7 @@ task focus ("only Tasks 1-3 this run").
spec this skill consumes.
- **Output target:** `skills/implement/SKILL.md` — runs the plan
task-by-task.
- **No private agents.** This skill is dialogue-driven (orchestrator
+ spec).
- **Agents dispatched:**
- `skills/planner/agents/ailang-plan-recon.md` — Step 2,
file-structure mapping (read-only). Mandatory; the Boss does
NOT do recon in-context.