Initial commit

commands/c3-audit.md

@@ -0,0 +1,65 @@
+---
+description: Audit C3 documentation against codebase reality
+---
+
+Verify `.c3/` documentation matches actual implementation.
+
+## Flow
+
+1. **Read current state**
+   - `.c3/TOC.md` and all docs
+   - `.c3/settings.yaml`
+
+2. **Explore codebase** (Task Explore, very thorough)
+   - Discover containers (package.json, go.mod, Dockerfile, etc.)
+   - Discover components within each container
+
+3. **Audit categories**
+
+   | Category | Check |
+   |----------|-------|
+   | Config compliance | Docs follow settings.yaml |
+   | Vision vs fact | Documented = actual code |
+   | ADR status | Proposed/accepted/stale/abandoned |
+   | Skill compliance | Frontmatter, anchors, sections |
+
+4. **Generate findings report**
+
+   ```
+   ## Findings
+
+   ### Vision vs Fact
+   - ❌ c3-3-worker documented but not found
+   - ⚠️ /services/notification undocumented
+   - ✅ c3-1-backend matches /api
+
+   ### ADR Status
+   - ⚠️ ADR-001 proposed 30+ days
+   - ✅ ADR-002 implemented
+
+   ### Summary: 1 critical, 2 warnings, 2 passing
+   ```
+
+5. **Handoff**
+
+   Check `settings.yaml` `audit:` section for preference.
+
+   If not set, ask:
+   ```
+   How to handle findings?
+   1. Manual - review report yourself
+   2. Tasks - create vibe-kanban tasks
+   3. Agents - dispatch subagents to fix
+
+   Save preference to settings.yaml?
+   ```
+
+   Execute chosen handoff:
+   - **Manual:** done
+   - **Tasks:** use vibe-kanban MCP to create tasks
+   - **Agents:** use Task tool to dispatch fixes in parallel
+
+## References
+
+- [derivation-guardrails.md](../references/derivation-guardrails.md) - Core principles
+- [v3-structure.md](../references/v3-structure.md) - Expected structure

commands/c3-config.md

@@ -0,0 +1,12 @@
+---
+description: Configure project settings in .c3/settings.yaml
+---
+
+Create or update `.c3/settings.yaml` with project-specific preferences.
+
+Use the `c3-config` skill to configure:
+- Diagram tool preferences (mermaid, PlantUML, etc.)
+- Layer-specific documentation guidance (context, container, component)
+- Team guardrails and constraints
+- Post-ADR handoff steps
+- Audit findings handling

commands/c3-init.md

@@ -0,0 +1,10 @@
+---
+description: Initialize C3 documentation structure from scratch
+---
+
+Create `.c3/` directory structure and begin system design.
+
+Use the `c3-adopt` skill for fresh initialization, which will:
+1. Create `.c3/` directory structure (v3: containers as lowercase folders)
+2. Track version via `c3-version` frontmatter in README.md
+3. Guide through Context, Container, and Component discovery

commands/c3-migrate.md

@@ -0,0 +1,11 @@
+---
+description: Migrate .c3/ documentation to current skill version
+---
+
+Migrate this project's C3 documentation to the current skill version.
+
+Use the `c3-migrate` skill to:
+1. Detect current project version from `.c3/VERSION`
+2. Compare against current skill version
+3. Build and present migration plan
+4. Execute transforms with user confirmation

commands/c3-use.md

@@ -0,0 +1,11 @@
+---
+description: Get started with C3 architecture docs - guides reading if .c3/ exists, offers adoption if not
+---
+
+Entry point for working with C3 architecture documentation.
+
+Use the `c3-use` skill to:
+- Get oriented with existing `.c3/` documentation
+- Understand the C3 structure (Context → Container → Component)
+- Navigate to specific documents
+- Initialize C3 if not yet set up

commands/c3.md

@@ -0,0 +1,5 @@
+---
+description: Design or update system architecture using C3 methodology
+---
+
+Use the `c3-design` skill to guide architecture changes.