implementation-aligned-planning

To align planning docs with your codebase, this skill converts vague documents into explicit contracts that map to code, config, and execution order. It generates navigation-focused stage documents and reference mappings for implementation and review.

Documenting source-of-truth relationships and naming rules in ambiguous repositories involves generating implementation-aligned guides. These guides explicitly define modules, inputs, outputs, and checks to improve reproducibility and establish clear debugging paths.

You generate navigation-focused stage documents by converting vague planning materials into explicit read and write artifacts. This establishes verifiable execution order mappings and implementation guarantees that guide development and review.

Yes, implementation-aligned planning applies directly to repositories with misaligned naming and stale docs. It converts outdated plans into living guides that document modules, inputs, outputs, and checks to establish clear debugging paths.

You need explicit contracts for reads, writes, and execution order when a repository's upfront plan is out of date or ambiguous. This ensures verifiable implementation by documenting source-of-truth relationships and clear debugging paths.

Implementation-aligned planning improves reproducibility by documenting naming rules and distinguishing source-of-truth data from caches. It converts vague plans into living contracts that explicitly map modules, inputs, outputs, and checks.