implementation-aligned-planning

Converts planning documents into implementation-aligned guides with code, config, and execution order.

Updated Mar 17, 2026

Search Tags:#planning #debugging #codebase #implementation #navigation #docs #contracts

Ready to run

npx skills add https://github.com/balandongiv/agent-skillbook --skill implementation-aligned-planning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-aligned-planning
Source: https://github.com/balandongiv/agent-skillbook/tree/main/skills/implementation-aligned-planning/exports/claude
Command: npx skills add https://github.com/balandongiv/agent-skillbook --skill implementation-aligned-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguous or stale planning documents are hard to implement and verify. This skill converts them into living, implementation-aligned guides that map to code, config, and execution order.

Core Features & Use Cases

Converts planning docs into explicit contracts (guarantees, reads, writes) and navigation aids.
Documents naming rules and source-of-truth vs caches to improve reproducibility.
Use Case: When a repo's upfront plan is out of date, generate an aligned doc that guides implementation and review.

Quick Start

Turn the repository's planning docs into an implementation-aligned guide.

Frequently Asked Questions about implementation-aligned-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert outdated planning docs into implementation-aligned contracts tied to my codebase?▼

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.

What is the best way to document source-of-truth relationships and naming rules in a codebase with ambiguous planning?▼

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.

How do I generate navigation-focused stage documents from vague project planning materials?▼

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.

Can I use implementation-aligned planning for repositories with misaligned naming and stale documentation?▼

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.

When do I need to create explicit contracts for reads, writes, and execution order in my repository?▼

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.

Why does implementation-aligned planning improve reproducibility in repositories with ambiguous planning?▼

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.