planning-doc-editor

Edit planning documents to remove placeholders and repair template drift.

4|1|Updated Feb 3, 2026

Search Tags:#planning #milestones #normalization #drift #placeholders #document-editing #template-contract

Ready to run

npx skills add https://github.com/danielbaustin/agent-design-language --skill planning-doc-editor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning-doc-editor
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/planning-doc-editor
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill planning-doc-editor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning teams struggle with drifting milestone documents, placeholder content, and inconsistent versions across planning templates. This skill normalizes and repairs ADL milestone or project planning docs to stay aligned with versioned planning contracts, without editing lifecycle cards or other card types.

Core Features & Use Cases

Normalize milestone and project planning docs to remove drift and placeholder residue.
Repair required sections to match the planning-template contract while preserving the distinction between generated, reviewed, and approved documents.
Keep documents aligned with source-backed milestone truth and stop before affecting issue cards or lifecycle artifacts.
Suitable for README, WBS, sprint, vision, design, decisions, demos, release plans, release notes, and handoffs that require planning integrity.

Quick Start

Normalize the planning document at the bounded target against the planning-template contract while preserving generated, reviewed, and approved truth.

Frequently Asked Questions about planning-doc-editor

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

FAQPage Schema

How do I remove placeholders from milestone planning documents?▼

To remove placeholders from milestone planning documents, this skill normalizes README, WBS, and sprint files against a versioned planning-template contract, repairing drift while preserving generated, reviewed, and approved truth.

What is document drift in project planning templates?▼

Document drift occurs when milestone planning files like vision, design, and release docs lose alignment with versioned planning contracts. This skill repairs the drift by applying bounded edits to restore required sections.

Does the planning doc editor modify lifecycle cards?▼

No, the planning doc editor does not modify lifecycle cards or issue cards. It strictly applies bounded edits to planning documents like decisions, demos, and handoffs to ensure template alignment without affecting lifecycle artifacts.

How do I align WBS and sprint docs with a template contract?▼

You align WBS and sprint docs with a template contract by normalizing the bounded target document against the planning template. This preserves source-backed milestone truth and outputs a structured report with references.

Can I use this to repair release notes and handoff documents?▼

Yes, you can repair release notes, release plans, and handoff documents. The skill normalizes these planning files to remove placeholder residue and restore required sections while keeping source-backed milestone truth intact.

What are the limitations of normalizing planning documents?▼

A key limitation is that normalization stops before affecting issue cards or lifecycle artifacts. Additionally, the bounded edits preserve the distinction between generated, reviewed, and approved documents rather than overwriting all content blindly.