cupdate-arch

Solid

Update .correctless/ARCHITECTURE.md after features land. Use after /cdocs or when the codebase structure has changed.

AI & Automation 61 stars 2 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
60
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /cupdate-arch — Maintain Architecture Documentation > **Shared constraints apply.** Before executing, read `_shared/constraints.md` from the parent of this skill's base directory. All constraints there apply to this skill. ## Intensity Gate This skill requires effective intensity `high` or above. Compute effective intensity using the procedure in the shared constraints (`_shared/constraints.md`). **Intensity threshold**: /cupdate-arch requires high minimum intensity to activate. - If the effective intensity is below the required intensity, print an informational message: - Skill name: /cupdate-arch - Required intensity: high - Effective intensity: (computed above) - Override: pass `--force` to override the intensity gate, or set `workflow.intensity` to `high` or above in `.correctless/config/workflow-config.json` - Then **do not proceed** with the skill body. Stop here. - If the effective intensity is at or above the threshold, or if the user passed `--force`, proceed normally — skip the gate entirely, no gate output. You are the architecture documentation agent. Your job is to keep .correctless/ARCHITECTURE.md current after features land. ## Progress Visibility (MANDATORY) Architecture updates take 5-10 minutes. The user must see progress throughout. **Before starting**, create a task list: 1. Read current architecture docs and recent specs 2. Validate existing entries (paths, tests, producers/consumers) 3. Scan codebase for undocumented abstractions 4. ...

Details

Author
joshft
Repository
joshft/correctless
Created
2 months ago
Last Updated
yesterday
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

cdocs

Update project documentation after a feature lands. Updates README, .correctless/AGENT_CONTEXT.md, .correctless/ARCHITECTURE.md, and feature docs. Run before merging.

61 Updated yesterday
joshft
AI & Automation Solid

carchitect

Structured architecture definition. Two modes — reverse-engineer from existing code or greenfield directed discovery. Produces .correctless/ARCHITECTURE.md with machine-referenceable entrypoints YAML and human-readable prose sections.

61 Updated yesterday
joshft
Code & Development Listed

architecture-docs

Generate or refresh `/docs/architecture/` — the current-state source of architectural truth for this codebase, grounded in code and git history (NOT in .designs/). Produces an anchor-dense corpus (`invariants.md`, `idioms.md`, `trust-boundaries.md`, `seams.md`, `subsystems/*.md`, `history.md`, `gaps.md`) plus a high-level overview layer (C4 L1/L2 diagrams, sequence flows, Nygard ADRs). Every claim is anchored to a file:line or commit SHA, or labelled literally `"unknown — needs review"`. A bundled `validate.sh` mechanically enforces citation density and phase-completion gates. Used to ground future design reviews so they cannot silently drift away from established idioms.

0 Updated yesterday
stempeck
AI & Automation Solid

doc-updates

Update documentation after code changes with quality gates, slop detection, consolidation, and accuracy verification.

297 Updated today
athola
Testing & QA Listed

arch-tech-spec

Use when defining technical specifications, non-functional requirements, or architecture decisions. Also triggers on 'tech spec', 'what are the NFRs', 'architecture decisions', 'performance requirements', 'scalability', 'security requirements', or 'ADR'.

1 Updated 2 months ago
etusdigital