feat(autoplan): carve the four review phases + tasks aggregator into sections

Phase bodies (CEO/Design/Eng/DX consensus flows) and the Implementation Tasks
aggregator load on demand; Design and DX stay separate sections because each
is independently conditional on scope. Skeleton 83.7KB -> 58.7KB (-30%
always-loaded); the 6 decision principles, classification, sequencing, and
explicit skip-condition dispatch stay always-loaded. The chain E2E's
phase-complete markers now live only in sections, so its assertions double as
section-read proof (behavioral: external).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-08-25 17:03:12 +00:00
co-authored by Claude Fable 5
parent 2877b63afe
commit c593c93268
17 changed files with 980 additions and 873 deletions
+11 -2
View File
@@ -51,6 +51,14 @@ describeIfSelected('Autoplan dual-voice E2E', ['autoplan-dual-voice'], () => {
const dest = path.join(skillsBase, skill);
fs.mkdirSync(dest, { recursive: true });
fs.copyFileSync(path.join(ROOT, skill, 'SKILL.md'), path.join(dest, 'SKILL.md'));
// Carved skills (autoplan + the plan-* reviews) keep their phase/review
// bodies in on-demand sections/ that the skeleton STOP-Reads — mirror the
// real install (which links sections/ next to SKILL.md) so the registered
// skeleton's section reads resolve inside the fixture.
const sections = path.join(ROOT, skill, 'sections');
if (fs.existsSync(sections)) {
copyDirSync(sections, path.join(dest, 'sections'));
}
}
// Write a tiny plan file for /autoplan to review.
@@ -139,8 +147,9 @@ Add a new /greet skill that prints a welcome message.
// Full Phase 1 COMPLETION (three parallel review subagents, each loading a
// 25-35K-token skill) routinely exceeds 10 minutes on sonnet, so requiring
// the "Phase 1 complete" banner would force a 20-minute test for no extra
// dual-voice signal. Accept EITHER the completion banner (autoplan/SKILL.md
// "PHASE 1 COMPLETE" mandatory output) OR structural evidence that the
// dual-voice signal. Accept EITHER the completion banner (the "PHASE 1
// COMPLETE" mandatory output in autoplan/sections/ceo-phase.md, which the
// skeleton STOP-Reads) OR structural evidence that the
// Phase 1 review dispatch actually happened: an Agent tool_use whose input
// carries review instructions (execution artifact built by the skill, not
// an echo of our prompt).