Manage Execution Manifest Skill

Compose, read, and validate the per-plan execution manifest — a small declarative artifact emitted at the end of phase-4-plan that names the exact Phase 5 verification steps and Phase 6 finalize steps for this plan. Phases 5 and 6 become dumb manifest executors; per-doc skip logic in their standards is removed in favor of this single source of truth.

This skill is script-only: it has no user-invocable command and is not loaded into LLM context via Skill: directives. It is invoked exclusively through the 3-part script notation plan-marshall:manage-execution-manifest:manage-execution-manifest. Per the project memory's plugin.json registration rules, it MUST NOT be registered in plugin.json.

Enforcement

Base contract: See manage-contract.md for shared enforcement rules, TOON output format, and error response patterns.

Skill-specific constraints:

• The manifest file is the single source of truth for Phase 5/6 step selection — every decision MUST be reflected in the manifest, and every reasoning MUST be logged via manage-logging decision.
• The manifest stays lean and diffable. Do not embed reasoning, timestamps, or free-text fields — push those to decision.log.
• compose is idempotent: re-invocation overwrites the previous manifest. Callers responsible for re-entry semantics.
• The seven-row decision matrix is authoritative. See decision-rules.md for the canonical table.

Storage Location

The manifest is stored in the plan directory: