Commit Graph

16 Commits

Author SHA1 Message Date
Z User
f6be7ffcc5 Refmod verbatim is now machine-checked: outline_refmods() extracts the story's identity/voice block from the outline's subjects strings and diffs every scene's subject_definitions line against it (fragment --outline + the merge); rewrites, form swaps and invented refmods fail with actionable errors; embedded suite gains the gate fixtures and stays under Cline's 8k output cap (7,712 B) 2026-10-31 01:19:46 +00:00
Z User
dc8d9fab81 Skill is install-location independent: SKILL_DIR concept (loaded-from folder) replaces project-root assumption; all command forms use %USERPROFILE%\.agent\skills\h3-plan-gate; generated files go to the working folder; README install section rewritten for global skills dirs (.clinerules/.cline kept as repo-workspace extras) 2026-10-31 00:49:45 +00:00
Z User
eb1b626648 Cline-native integration: .clinerules standing rules + /h3-plan workflow + .cline/skills stub; SKILL.md gains 6,000-char editor split pattern (@@CONTINUE@@) and 8,000-char command-output fallback (suite is 7.6KB, at the edge); py -3 fallback 2026-10-31 00:33:14 +00:00
Z User
39a38c7c64 Cline caps are hard-coded char budgets, not context-relative: read caps 48k chars / 2k lines / 2k chars-per-line documented exactly, one-line plan files marked never-read-back, README notes -c 131072 does not lift them 2026-10-31 00:24:44 +00:00
Z User
36c2dbf46e Cline-aware bounded reads: cite exact line ranges (PROMPT A 53-156, PROMPT B 157-568, single-pass fence 30-428), run-don't-read the 62KB validator, chunking fallback for truncated reads - Cline caps reads at ~50k chars and cuts sooner on small model contexts 2026-10-31 00:12:22 +00:00
Z User
c0d377b894 build_plan.py delivery print and docstring now route the paste to the internal plan_json widget (dynamicPrompts:False) - stops the LLM from steering the user back into a multiline/dynamic-prompt input 2026-10-30 23:19:56 +00:00
Z User
99c3e89beb Step 5 corrected: internal plan_json widget is the only safe paste surface - ComfyUI frontend dynamic-prompt serializer strips braces from dynamicPrompts:true widgets at queue time (Extra data fingerprint = quoted first key length; probe calibration included) 2026-10-30 22:40:34 +00:00
Z User
fb271a8399 Six-section Ref2VA setup: three definition forms, refmod isolation, no length caps 2026-10-30 21:53:22 +00:00
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
Z User
f5575fa678 Scene composition is the gate, not word counts
The skill exists so the LLM writes/rewrites each scene one at a time
with full attention on making it a complete scene composition — not so
it can hit a word target.

Prompts: the word-budget craft bullets are replaced by an 8-element
composition checklist (subject anchor, style anchor, continuity anchor,
blocking, camera, performance, physical texture, exit state) in both the
scene-writer PROMPT B (new SCENE COMPOSITION section) and the single-pass
prompt. Chase the elements, never a number; padding is as much a failure
as a thin one-liner.

Validator: hard word bands (<10s: 150-200, >=10s: 200-300) removed from
plan and fragment checks. Replaced by a thin-scene floor (100/120 words)
that only trips lazy output, plus a new continuity-anchor check — chained
fragments must open inside the previous end_state. No target band, no
upper limit; output lines say so.

SKILL.md/README: goal, Step 2, craft rules, table rows, and example
outputs updated to match. Suite, --check, chained fragment checks all
green.
2026-10-29 19:13:27 +00:00
Z User
83cc5145bf Realign: one plan JSON, written one scene at a time
The deliverable is the single merged plan.json — the same shape the
single-pass system prompt emits — and the multi-clip video is what the
node itself produces from it: each shot renders as its own clip, chained
through the H3 context loop into one continuous video. Removed the
--clips per-scene export (external stitching is NOT the design).

Workflow restated everywhere: outline turn -> the LLM writes each scene
one at a time (one focused turn per scene) -> build_plan.py puts it all
together at the end into plan.json -> paste once, queue once.

build_plan.py: --clips option and export block removed; docstring now
describes the node-side chaining. README: intro/example/validating/
wiring rewritten around the single deliverable. SKILL.md: goal, Step 3
(Put it all together at the end), Step 4 (the node makes the multi-clip
video), and the revising loop updated. Suite + --check green.
2026-10-29 19:00:11 +00:00
Z User
54a8271072 Multi-clip videos as the primary deliverable: per-scene clip export
build_plan.py --clips [DIR] (default clips/) now exports one validated
single-shot plan JSON per scene (clip_01.json, ...) alongside the merged
plan. Each clip renders through plan_json_input as its own video at FULL
duration (no chain overlap trim), then the clips are stitched in order;
the mid-motion open/close craft rules make the cuts read as one take.
plan.json stays as the optional single continuous-take render.

SKILL.md Step 3/4 rewritten (merge exports clips + plan; deliver =
render-per-clip then stitch), README intro/example/wiring/validating
updated to multi-clip-first with real clip output shown. Verified from a
simulated project root: export green, every clip re-checks PLAN OK.
2026-10-29 18:40:18 +00:00
Z User
a804088d72 README: end-to-end example from story idea to final output
Walks the shipped greenhouse example through all six steps: the Cline
request, smoke test, outline.json (full JSON), one-file-at-a-time scene
validation, build_plan.py merge with real output (1042 frames = 43.42s),
and rendering via plan_json_input incl. the revise-one-scene loop. All
command blocks aligned to the Windows venv form (.venv\\Scripts\\python.exe)
with one macOS/Linux note, matching SKILL.md.
2026-10-29 18:32:43 +00:00
Z User
b9b0e41469 Add SKILL.md: Agent Skills entry point for the h3-plan-gate folder
The h3-plan-gate directory is now a drop-in skill for Cline (.cline/skills/
or ~/.cline/skills/) and any Agent-Skills-compatible agent. SKILL.md carries
the full agent procedure (outline -> one fragment per turn with per-turn
validation -> build_plan.py merge -> delivery notes) plus the condensed
craft rules; the prompt .md files remain the deep reference and worked
examples stay bundled. README files table updated.
2026-10-29 17:55:52 +00:00
Z User
63a4469315 README: agent usage guide for the h3-plan-gate workflow
3-stage agent workflow (outline -> one scene per turn -> validated merge),
per-turn fragment gate, validation commands, smoke test with the shipped
examples, plan_json_input wiring notes, and requirements.
2026-10-29 17:31:19 +00:00
bc774c68cd Initial commit 2026-10-29 10:13:40 -07:00