Does c3-provision write actual source code?

No, c3-provision is strictly for design and documentation; it creates ADRs and provisioned component docs without modifying your application's logic.

Does this skill require an existing setup?

Yes, it requires the .c3/ directory to exist in your repository to store the architectural context and generated documentation.

When should I use c3-provision instead of c3-alter?

Use c3-provision when you want to plan, sketch, or document a design first. Use c3-alter when you are ready to perform actual code changes.

What is 'provisioned' status in C3?

A provisioned status indicates that a component's architecture and behavior have been designed and approved, but the implementation does not yet exist in the codebase.

C3 Provision - Architectural Design

Name: C3 Provision - Architectural Design
Author: lagz0ne

bylagz0ne

•

学習とドキュメンテーション

Documents and plans software architecture through ADRs and component specifications without immediate code implementation.

C3 Provision is a specialized design skill for Claude Code that follows the Context-Container-Component (C3) methodology to document architectural decisions before a single line of code is written. It allows developers to 'provision' new services or components by generating structured Architecture Decision Records (ADRs) and provisioned component documentation. This ensures that system designs are vetted, scoped, and formally documented, providing a clear blueprint for future implementation while maintaining a rigorous source of truth within the repository's metadata.

主な機能

01Provisioned Status Management: Generates documentation for components that are planned but not yet implemented.

027 GitHub stars

03Architectural Impact Scoping: Analyzes the current system state to identify which containers and components are affected by a new design.

04Standardized ADR Generation: Creates formal Architecture Decision Records to capture the rationale behind designs.

05Socratic Intent Clarification: Utilizes a multi-stage workflow to ensure design goals are fully understood before documentation begins.

06Implementation Hand-off: Creates a documented trail that serves as the prerequisite for implementation via implementation-focused skills.

ユースケース

01Designing a new microservice or API container architecture before starting development.

02Capturing architectural trade-offs and decisions for team review and historical record-keeping.

03Planning a major refactor of an existing component's behavior without making code changes.

主な機能

01Provisioned Status Management: Generates documentation for components that are planned but not yet implemented.

027 GitHub stars

03Architectural Impact Scoping: Analyzes the current system state to identify which containers and components are affected by a new design.

04Standardized ADR Generation: Creates formal Architecture Decision Records to capture the rationale behind designs.

05Socratic Intent Clarification: Utilizes a multi-stage workflow to ensure design goals are fully understood before documentation begins.

06Implementation Hand-off: Creates a documented trail that serves as the prerequisite for implementation via implementation-focused skills.

ユースケース

01Designing a new microservice or API container architecture before starting development.

02Capturing architectural trade-offs and decisions for team review and historical record-keeping.

03Planning a major refactor of an existing component's behavior without making code changes.