submit-plan-artifactlisted

# submit-plan-artifact ## Overview A plan is one native-markdown document. Explanations are prose; structured values use labeled fields. Steps are `### [S-n] Title` blocks with stable IDs that are never renumbered. Validate with `ralph_verify_md_artifact`, submit with `ralph_submit_md_artifact` (`artifact_type: plan`). To revise a submitted plan, stage the complete revised document with `ralph_stage_md_artifact` (`mode="replace_all"`), edit the staged text directly, inspect with `ralph_get_md_draft`, then submit with `ralph_finalize_md_artifact`. ## Document shape Universal anchors: - Frontmatter contains `type: plan`. - At least one complete `### [S-n] Title` step block exists unless the plan explicitly declares `noop: true`. - Step IDs are unique across the whole document. - Dependencies and acceptance-criterion references resolve to existing IDs. - Every verification or acceptance criterion is evaluatable with a concrete command and expected result, or a specific file/artifact to inspect. Everything else is a recommended authoring pattern, not required grammar. `## Summary`, `## Scope`, `## Skills MCP`, `## Steps`, `## Critical Files`, `## Risks`, and `## Verification` are useful conventional sections, but plans with radically different headings, ordering, prose, or nested subplans remain valid when the universal anchors and consumed references parse. Use `## Work Units` for small bounded tasks or verification gates. Use repeatable `## <Name> Subplan` or `## Su