cdocs

Update README, AGENT_CONTEXT.md, ARCHITECTURE.md, and feature docs after feature integration.

65|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/joshft/correctless --skill cdocs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cdocs
Source: https://github.com/joshft/correctless/tree/main/correctless/skills/cdocs
Command: npx skills add https://github.com/joshft/correctless --skill cdocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update project documentation automatically after a feature lands to ensure README, .correctless/AGENT_CONTEXT.md, .correctless/ARCHITECTURE.md, and feature docs stay current across the repository.

Core Features & Use Cases

  • Automatically refresh and align documentation artifacts after feature integration.
  • Ensure critical files such as README, AGENT_CONTEXT.md, ARCHITECTURE.md, and feature docs reflect the latest specs.
  • Provides a repeatable workflow trail by logging changes to docs and artifact history.

Quick Start

After merging a feature, run the documentation update workflow to synchronize project docs.

Frequently Asked Questions about cdocs

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

FAQPage Schema
How do I keep README and architecture docs in sync after merging a feature?▼

To keep README and architecture docs in sync after a feature lands, run a documentation update workflow that automatically refreshes project artifacts to reflect post-merge spec changes and decisions.

What is the best way to automate project documentation updates after a feature lands?▼

Automating project documentation updates involves applying a frontmatter-driven workflow that refreshes README, AGENT_CONTEXT.md, ARCHITECTURE.md, and feature docs to align with the latest repository specs.

How does documentation synchronization work for repository workflows?▼

Documentation synchronization works by integrating with a shared constraint system to produce a consistent pipeline, applying mandatory file updates to ensure docs reflect post-merge decisions accurately.

Do I need specific files in my repository to maintain consistent feature docs?▼

Yes, maintaining consistent feature docs requires specific files like README, AGENT_CONTEXT.md, and ARCHITECTURE.md to exist in your repository so the synchronization workflow can apply mandatory updates.

What's the best way to log changes to project docs and artifact history?▼

To log changes to project docs and artifact history, use a repeatable workflow trail that records documentation updates and artifact modifications after feature integration lands in the repository.

When should I not use an automated documentation update workflow?▼

You should avoid automated documentation update workflows when your repository lacks the required artifact files like AGENT_CONTEXT.md or ARCHITECTURE.md, or when post-merge spec changes are not yet finalized.