c3

Initialize C3 workspaces and validate architecture documentation against governance rules.

2|1|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/lagz0ne/prev-cli --skill c3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: c3
Source: https://github.com/lagz0ne/prev-cli/tree/main/.opencode/skill/c3
Command: npx skills add https://github.com/lagz0ne/prev-cli --skill c3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the adoption and auditing of C3 architecture documentation, reducing manual setup and governance overhead.

Core Features & Use Cases

  • Adopt: Create and initialize a C3 workspace (.c3) with Context, Containers, and ADR-000.
  • Audit: Validate existing C3 docs and configurations against governance rules.
  • Routing: Directs to c3-query for navigation or c3-alter for changes based on context.
  • Modes: Supports Adopt and Audit workflows, with harness integration.

Quick Start

Run PROJECT="MyApp" C1="backend" C2="frontend" ./scripts/c3-init.sh to initialize the C3 workspace and begin the adoption flow.

Frequently Asked Questions about c3

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

FAQPage Schema
How do I automate C3 architecture documentation setup and onboarding?

Automate C3 architecture adoption by running the c3-init script with project and component variables, generating Context, Containers, and ADR-000 docs via frontmatter-driven templates to eliminate manual setup overhead.

What is C3 architecture governance validation and how does it work?

C3 architecture governance validation audits existing documentation against predefined rules. It checks configurations within the .c3 directory and enforces compliance using harness integration and frontmatter-driven routing to c3-query or c3-alter.

How do I initialize a C3 workspace for a new project?

Initialize a C3 workspace by executing the c3-init.sh script with PROJECT, C1, and C2 environment variables. This creates the .c3 directory structure and triggers the component adoption workflow for Context and Containers.

Can I use this to audit existing C3 architecture docs without reinitializing?

Yes, you can audit existing C3 architecture docs without reinitializing. The Skill detects an existing .c3 directory and routes to the Audit workflow, validating configurations against governance rules without overwriting current templates.

When should I route to c3-query versus c3-alter?

Route to c3-query for navigating and reading existing C3 architecture documentation, and route to c3-alter when you need to modify or change the documented Context, Container, or ADR components during the audit workflow.

What are the limitations of frontmatter-driven templates in C3 architecture automation?

The frontmatter-driven templates enforce strict governance and workflow routing for C3 architecture documentation. A limitation is that component generation relies on the load-harness reference, requiring specific script inputs for Context and Containers without bypassing validation.