intent-normalize

Normalize intent and planning Markdown and YAML files to the IDD standard.

15|5|Updated Jan 20, 2026

Search Tags:#automation #planning #documentation #frontmatter #intent #normalize #idd

Ready to run

npx skills add https://github.com/ArcBlock/idd --skill intent-normalize

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: intent-normalize
Source: https://github.com/ArcBlock/idd/tree/main/skills/intent-normalize
Command: npx skills add https://github.com/ArcBlock/idd --skill intent-normalize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalize and standardize IDD intent and planning docs by injecting missing frontmatter, correcting directory structure, and tagging items for follow-up.

Core Features & Use Cases

Auto-inject missing frontmatter to align with IDD standards.
Normalize directory structure and file naming for intent/ planning docs.
Mark items with status/needs for pickup and generate a standardized normalization report.
Produce idempotent changes so repeated scans do not modify already compliant files.

Quick Start

Run /intent-normalize to scan intent and planning files and apply automatic fixes to meet the IDD standard.

Frequently Asked Questions about intent-normalize

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

FAQPage Schema

How do I normalize intent and planning docs to meet the IDD standard?▼

Auto-inject missing frontmatter and correct directory structure for IDD intent and planning Markdown and YAML files, flagging items with status/needs metadata for pickup to support TeamSwarm workflows.

How do I automatically fix frontmatter in markdown planning documents?▼

Analyze frontmatter in Markdown and YAML files under intent/ and planning/ directories, automatically injecting missing metadata fields and correcting mechanical issues to align with IDD standard requirements.

What happens if I run intent normalization on already compliant files?▼

Idempotent transformations ensure repeated scans do not modify already compliant files, delivering deterministic reporting that safely supports ongoing TeamSwarm workflows without duplicate modifications.

Can I use automation to tag planning docs with status and needs metadata?▼

Flag planning and intent items with status/needs metadata for pickup by scanning Markdown and YAML files, automatically applying tags to satisfy TeamSwarm workflow requirements for normalized documentation.

Why does my IDD planning doc need frontmatter and directory structure normalization?▼

Normalize IDD planning docs to inject missing frontmatter, correct directory structure, and tag items with status/needs metadata, ensuring deterministic reporting and proper pickup tracking for TeamSwarm workflows.