lagz0ne/c3-skill

Overview

This skill routes C3 architecture requests and performs audits of existing C3 documentation for consistency and completeness. It detects intent, forwards tasks to specialized C3 agents, and runs a structured audit flow that outputs pass/fail/warn results and actionable fixes. When no .c3/ directory is present it routes to onboarding to initialize C3 structure.

How this skill works

The skill inspects user intent and repository state, then routes requests to c3-query, c3-alter, c3-ref, or c3-provision as appropriate. For audits it loads audit-checks and runs a phased validation (inventory, categorization, refs, diagrams, ADR lifecycle, content separation, context files) producing a report with findings and remediation steps. It also triggers /c3 apply to generate or refresh CLAUDE.md files when needed.

When to use it

• Ask to audit architecture, validate C3, check C3 docs or verify docs
• You need a full C3 audit: inventory, ADR checks, diagram and reference validation
• You want to initialize C3 when no .c3/ directory exists
• You need to route a question about C3 docs or design to the right agent
• You plan to apply or generate CLAUDE.md files across the codebase

Best practices

• Start audits with the repository loaded and ensure references/ files are readable
• Use clear intent verbs: audit, query, provision, alter, or ref to get precise routing
• Run /c3 audit before /c3 apply to learn what will be created or updated
• Preserve user content outside the c3-generated block when applying CLAUDE.md
• Address WARN items incrementally: fix missing refs and stale CLAUDE.md first

Example use cases

• User: “Check if C3 docs are up to date” → runs audit phases 1–10 and returns PASS/FAIL/WARN with fixes
• User: “Audit container c3-1” → runs container-scoped audit and lists component gaps
• User: “Are ADRs current?” → validates ADR lifecycle, flags stale or missing ADR metadata
• No .c3/ directory found → routes to onboarding to create C3 scaffolding and learning loop
• User: “Generate CLAUDE.md files” → runs /c3 apply (dry-run option) and reports created/updated/skipped counts