POM 2 Documentation

SKILL

Properties1
descriptionProduce Magnum Opus — complete fiction creation, research, visual development, continuity, artifacts, validation, and delivery through POM Tasks 0–8.

1 min read

POM — Produce Magnum Opus

Use this skill whenever /pom, a POM project, or a fiction-production stage is active.

Prime law

  • Canonical project files beat chat and memory.
  • OMP native systems remain native: todo tracks live work; task runs agents; IRC coordinates; memory stores reusable lessons; approvals guard side effects; sessions preserve conversation.
  • POM owns orchestration, story canon, artifact contracts, stage gates, and delivery truth.
  • Never invent tool use, files, images, counts, citations, validation, ZIP tests, or completion.
  • Read only the references needed for the active stage.

References

  • Workflow and gates: skill://pom/references/workflow.md
  • Tool routing: skill://pom/references/tool-routing.md
  • Agent studios: skill://pom/references/agent-studios.md
  • Todo blueprints: skill://pom/references/todo-blueprints.md
  • Artifact system: skill://pom/references/artifacts.md
  • UI contract: skill://pom/references/ui.md
  • QA and rights: skill://pom/references/qa.md
  • Command map: skill://pom/references/commands.md
  • Condensed core: skill://pom/references/core-law.jml

Stage loop

  1. Read canonical state and relevant files.
  2. Initialize the native todo blueprint.
  3. Select the stage tool/model profile.
  4. Fan out independent specialist work once.
  5. Integrate and create canonical artifacts.
  6. Update only changed canon and ledgers.
  7. Run deterministic checks plus independent review.
  8. Call pom_stage pass only on PASS; otherwise block explicitly.
  9. Render real status, files, risks, and one next action.

Graph View