orchestrate-content-by-stepslisted

Do a content request the RIGHT way, end-to-end, through the frozen development-step process. Use whenever the owner asks for content work — "make me a page about Apple", "add a news section", "add 3 test news", "create a blog". You pass only the INTENT (an action + a topic); this orchestrator DECOMPOSES it by the site's state (does the section exist?) into dependent sub-steps, and runs EACH through the full lifecycle: open a development step → do it → deploy → RECORD the deployment → close the step. The deployment record is a GATE — a step never closes without it (the Vercel invariant). You do NOT chain tools yourself, do NOT decompose by hand, do NOT generate content or code. Prefer this over calling compose / create-page directly for any real owner request.
Fractera/Agent-Engineering-Infrastructure · ★ 37 · AI & Automation · score 76

Install: claude install-skill Fractera/Agent-Engineering-Infrastructure

# orchestrate-content-by-steps The **frozen process** for content operations. You give an **intent**; the orchestrator does the rest **deterministically** — it decomposes the work by the site's state and runs every piece through the real development-step lifecycle, with the deployment record as a hard gate. This skill is **self-sufficient**: it is one tool (or one `.mjs`), no Hermes required. ## Why this exists (read once) Calling `compose` / `create-page` directly, by hand, is what caused the failure: an agent did "create section + 3 pages + rebuild" in one chaotic burst and crashed. The fix is to **freeze the process**, not just the templates. You stop orchestrating; the pipeline does. ## Which scenario is this? (decide FIRST) This skill runs the **FROZEN-ASSEMBLY** scenario only: a FLAT, MCP-only pipeline that stands up **new** structural stubs from frozen templates. It is NOT the coding pipeline. Confirm the vector before using it: - **CREATE-new** stubs (a section that does not exist yet, a new page/stub in a group) → FROZEN — use this. - **MODIFY an existing page** or **author real/custom content** (fill a stub with real prose) → that is **REAL-DEVELOPMENT** (coding agents), NOT this skill. Refuse and route it out (a coding agent, or from Hermes `owner_report_blocker_step`); the stub executors already refuse a real body. The border is the OPERATION, not a time-phase: create-new stub = FROZEN; modify-existing / real content = REAL-DEV. If the owner's vector is