document

Aligns project documentation with code changes through a phase-driven workflow.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/idealic-ai/engine --skill document-idealic-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document
Source: https://github.com/idealic-ai/engine/tree/main/skills/document
Command: npx skills add https://github.com/idealic-ai/engine --skill document-idealic-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Keeps documentation in sync with code changes and project state, preventing drift that wastes developer time and misleads teams.

Core Features & Use Cases

  • Phase-driven documentation workflow (Setup, Interrogation, Diagnosis & Planning, Agent Handoff, Operation, Synthesis) to orchestrate updates.
  • Bootstrapped standards loading, context ingestion, drift diagnosis, and surgical planning to target only the affected docs.
  • In-context debriefs and post-op synthesis to keep TOC and related docs aligned with code changes.

Quick Start

Start a surgical documentation pass that ingests context, diagnoses drift, and applies targeted updates to the docs.

Frequently Asked Questions about document

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

FAQPage Schema
How do I keep documentation in sync with code changes?

To keep documentation in sync with code changes, this Skill applies a phase-driven workflow that ingests context, diagnoses drift, and applies surgical edits to affected docs like architecture updates and release notes.

What is the best way to prevent documentation drift in software projects?

Preventing documentation drift requires auditing project state against existing docs, diagnosing inconsistencies, and generating targeted updates along with debriefs to keep the TOC and related references aligned.

How do I automate release notes generation from code updates?

You can automate release notes generation by running a surgical documentation pass that interrogates code changes, plans targeted edits, and synthesizes post-op updates to align project documentation automatically.

Can I update only specific affected architecture docs without rewriting everything?

Yes, the workflow diagnoses documentation drift and creates a surgical plan to target only the affected docs, ensuring updates are applied precisely without rewriting the entire documentation set.

Does this documentation sync workflow support agent handoffs for writing tasks?

Yes, the workflow includes an Agent Handoff phase that delegates writing and debrief generation tasks, ensuring documentation updates and post-op synthesis are orchestrated efficiently across the project.