plan-stage4-core

To generate deployment planning artifacts from a frozen Stage 3 context, use this Skill to draft Stage 4 markdown and json outputs. It processes Stage 3 inputs and applies Stage 4 templates to produce paired deliverables for deployment readiness without altering the original context.

Paired markdown and json planning artifacts are structured deployment deliverables generated from Stage 3 templates. They ensure consistent state-management by updating the manifest while preserving the frozen Stage 3 context for accurate deployment readiness tracking.

Yes, you can update the manifest state without mutating the frozen Stage 3 planning context. The Skill specifically isolates Stage 3 inputs, applying state-management updates exclusively to the Stage 4 artifact manifest to preserve original references.

Yes, you need both the frozen Stage 3 context and Stage 4 templates available. The Skill applies when these inputs are present, using them to produce the final markdown and json deliverables required for deployment planning.

The best way to transition planning outputs from Stage 3 to Stage 4 deliverables is using a dedicated artifact-generation process. It maps frozen Stage 3 inputs to Stage 4 markdown and json templates, ensuring paired outputs and automatic manifest updates.

Artifact generation fails when the Stage 3 context is missing or unfrozen because the Skill requires a stable, frozen Stage 3 input to accurately map templates and produce Stage 4 markdown and json outputs without risking data mutation or inconsistent state-management.