mmprompt/h3-plan-gate
Z User df8df95d39 User-approved scene guide is a mandatory workflow step
Encoded the intended user flow end to end: story + scene count ->
scene guide (outline.json) -> USER APPROVAL (hard stop, changes applied
to the guide first) -> scenes composed one at a time (~10s each) from
the approved guide -> continuity verified across the handoff chain ->
final plan.json.

SKILL.md: goal line states the five moves; new Step 2 'Present the
guide for approval (do not skip)' — plain-language presentation, STOP
and wait, approved guide is the contract; Step 3 works only from the
approved guide; Step 4 renamed 'Verify the continuity, put it all
together'; revising section split into guide-level vs single-scene.

README: workflow reframed as 4 stages with Stage 2 = approval (human in
the loop, never skipped); example gains a real guide-presentation +
'Approved — go' exchange between outline and scene writing; steps
renumbered.

Scene-agent prompt: stage table gains the Approval row and a 'Stage 2 is
a hard stop' note; assembler prompt re-labeled Stage 4. Suite + --check
green.
2026-10-29 19:28:18 +00:00
..
h3_agent_workflow_examples Realign: one plan JSON, written one scene at a time 2026-10-29 19:00:11 +00:00
build_plan.py Realign: one plan JSON, written one scene at a time 2026-10-29 19:00:11 +00:00
count_prompt_tokens.py Realign: one plan JSON, written one scene at a time 2026-10-29 19:00:11 +00:00
h3_plan_assembler_system_prompt.md User-approved scene guide is a mandatory workflow step 2026-10-29 19:28:18 +00:00
h3_plan_json_system_prompt.md Scene composition is the gate, not word counts 2026-10-29 19:13:27 +00:00
h3_scene_agent_system_prompt.md User-approved scene guide is a mandatory workflow step 2026-10-29 19:28:18 +00:00
SKILL.md User-approved scene guide is a mandatory workflow step 2026-10-29 19:28:18 +00:00
verify_plan_rules.py Scene composition is the gate, not word counts 2026-10-29 19:13:27 +00:00