skills.rest
amauryconstant
amauryconstantCOMMUNITY
Explore all skills by this author →
GitHub

osx-maintain-ai-docs

Update CLAUDE.md after implementing an OpenSpec change.

6|1|Updated Feb 12, 2026
Search Tags:#documentation#claude#guidelines#open-spec#quick-reference#documentation-maintenance
One-click install
npx skills add https://github.com/amauryconstant/openspec-extended --skill osx-maintain-ai-docs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: osx-maintain-ai-docs
Source: https://github.com/amauryconstant/openspec-extended/tree/main/resources/claude/skills/osx-maintain-ai-docs
Command: npx skills add https://github.com/amauryconstant/openspec-extended --skill osx-maintain-ai-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CLAUDE.md documentation can drift after implementing an OpenSpec change; this skill ensures consistent, up-to-date documentation that reflects the latest integration details.

Core Features & Use Cases

  • Aligns CLAUDE.md sections with new OpenSpec changes and integration patterns.
  • Generates concise documentation snapshots including rationale, changes, and usage notes.
  • Use cases include documenting new capabilities, archiving decisions, and clarifying Claude Code workflows after changes.

Quick Start

Update CLAUDE.md after implementing an OpenSpec change using this skill to produce a concise, structured entry.

Frequently Asked Questions about osx-maintain-ai-docs

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

FAQPage Schema
How do I keep CLAUDE.md documentation in sync after implementing OpenSpec changes?▼

To keep CLAUDE.md documentation in sync after OpenSpec changes, apply a structured documentation update that captures integration details, rationale, and usage notes. This prevents documentation drift in Claude Code projects.

What is documentation drift in Claude Code projects and when does it happen?▼

Documentation drift in Claude Code projects occurs when CLAUDE.md files become outdated after implementing new OpenSpec changes. It happens when integration details and design decisions are applied without updating the existing documentation structure.

How do I document OpenSpec design decisions and rationale in CLAUDE.md?▼

To document OpenSpec design decisions in CLAUDE.md, generate a concise documentation snapshot that includes the rationale, applied changes, and usage notes. Align CLAUDE.md sections with the new integration patterns for consistency.

Can I use this to archive decisions and clarify workflows in CLAUDE.md?▼

Yes, you can use it to archive decisions and clarify Claude Code workflows in CLAUDE.md. It generates structured documentation entries after OpenSpec changes, ensuring new capabilities and design decisions are consistently recorded.

Do I need a Claude Code project to maintain CLAUDE.md with OpenSpec?▼

Yes, you need a Claude Code project environment that uses OpenSpec for managing changes. This skill specifically targets projects documenting OpenSpec changes and design decisions within their CLAUDE.md files.

Related Skills

Explore More Content & Communication Skills→
bcmcpherbcmcpher

claude-md-audit

Audits CLAUDE.md files in a project and scores them against a defined rubric.

Community
Intermediate
DisbleDisble

dlexa-skill-updater

Automates detection of CLI interface changes and regeneration of skill documentation.

Community
Advanced
1natsu1721natsu172
1

1natsu-document-harness

Automate harness documentation updates across CLAUDE.md, rules, docs, and READMEs.

Community
Intermediate
Mahaboob26Mahaboob26

markdown-documentation

Create structured Markdown documentation with GitHub Flavored Markdown formatting.

Community
Basic