docs-living-spec

Align CLAUDE.md and AGENTS.md with current implementation decisions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lemessdavi/ia-prev --skill docs-living-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-living-spec
Source: https://github.com/lemessdavi/ia-prev/tree/main/skills/docs-living-spec
Command: npx skills add https://github.com/lemessdavi/ia-prev --skill docs-living-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation often drifts from implementation and runtime decisions, leading to outdated guidance for agents and team members.

Core Features & Use Cases

  • Living documentation that stays in sync with current behavior and decisions.
  • Clear targets for updating CLAUDE.md and AGENTS.md as architectural choices evolve.
  • Easy traceability from decisions to modules and workflows.

Quick Start

Update CLAUDE.md and AGENTS.md to reflect the latest decisions and patterns.

Frequently Asked Questions about docs-living-spec

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

FAQPage Schema
How do I keep CLAUDE.md and AGENTS.md documentation aligned with current implementation decisions?

To keep CLAUDE.md and AGENTS.md aligned with implementation, you enforce living-spec updates whenever architectural choices, workflows, or operational hurdles change, maintaining clear traceability from decisions to modules.

What is a living spec and why does project documentation drift from implementation?

A living spec is documentation that stays in sync with current behavior. Documentation drifts when implementation and runtime decisions occur without enforcing updates to guidance files like CLAUDE.md and AGENTS.md.

When should I update CLAUDE.md to reflect architectural decisions?

You should update CLAUDE.md when new architectural decisions are made, workflows change, or recurring operational hurdles emerge, ensuring living docs stay accurate and maintain clear change traces to modules.

What is the best way to maintain living documentation for team alignment across agents?

The best way to maintain living documentation for team alignment is to enforce updates to CLAUDE.md and AGENTS.md, capturing architectural decisions and workflows while maintaining clear change traces to modules and patterns.

How do I trace documentation changes back to specific modules and workflow patterns?

You trace documentation changes by enforcing living-spec maintenance that records clear change traces linking architectural decisions and recurring operational hurdles directly to their corresponding modules and patterns.