cupdate-arch

Update ARCHITECTURE.md with TB-xxx, ABS-xxx, and PAT-xxx entries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update and maintain Correctless ARCHITECTURE.md to reflect new features and changed code structure, ensuring the architecture documentation stays in sync with the codebase and specs.

Core Features & Use Cases

  • Scan the codebase, specs, and verification reports to identify undocumented architectural changes and new patterns.
  • Draft and append ARCHITECTURE.md entries (TB-xxx, ABS-xxx, PAT-xxx) to reflect the latest structure and decisions.
  • Enforce a gated workflow with progress visibility, mandatory reviews, and fragmentation checks to keep docs manageable.

Quick Start

Run /cupdate-arch to refresh ARCHITECTURE.md after new features land.

Frequently Asked Questions about cupdate-arch

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

FAQPage Schema
How do I update ARCHITECTURE.md after new features land in my codebase?

To update ARCHITECTURE.md after feature changes, scan the codebase, recent specs, and verification reports to identify undocumented changes, then draft new TB-xxx, ABS-xxx, and PAT-xxx entries for review.

What is the best way to keep architecture documentation in sync with code structure?

Keeping architecture documentation in sync requires a gated workflow that enforces progress visibility, mandatory reviews, and fragmentation checks to ensure docs reflect the latest codebase decisions.

How does architecture documentation handle feature specs and verification reports?

Architecture documentation processes feature specs and verification reports by consulting them to identify new patterns and undocumented changes, then appending draft entries to reflect the latest structural decisions.

Do I need existing architecture docs to use this codebase documentation workflow?

Yes, this workflow applies to codebases that already maintain architecture documentation and require ongoing updates after feature landings, specs, and verification reports to stay current.

What are TB-xxx, ABS-xxx, and PAT-xxx entries in architecture docs?

TB-xxx, ABS-xxx, and PAT-xxx entries are structured architecture documentation records drafted to reflect new features, abstract structures, and patterns, ensuring the architecture file stays manageable.

When should I avoid automated architecture documentation updates?

Avoid automated architecture documentation updates when a codebase lacks existing architecture docs, specs, or verification reports, as the workflow requires these inputs to draft accurate entries and perform fragmentation checks.