c3-provision_skill

Overview

This skill creates architecture documentation without making code changes. It generates an ADR in proposed state, walks the user through acceptance, and produces component docs marked as provisioned under .c3/provisioned. Use it when you want to design, plan, or document a component or service before implementation.

How this skill works

The skill performs a short, staged design workflow: clarify intent, analyze current state, assess scope, generate a provisioning ADR, obtain user acceptance, then create provisioned component docs. ADRs are created under .c3/adr and component docs under .c3/provisioned; the ADR status is updated to provisioned once docs exist. This is a documentation-only flow — no code changes or execution are produced.

When to use it

• You want to provision a new component or service without implementing it now
• You need an ADR and component docs to capture a design decision before coding
• You want to design or plan an architecture change and track it as provisioned
• You need to document updates to an existing component for future implementation
• You want a structured handoff for later implementation work

Best practices

• Ensure the repository contains a .c3/ directory before starting
• Answer intent and scope questions clearly to avoid rework
• List all affected c3 IDs and containers during scope assessment
• Keep ADR problem, decision, and rationale concise and focused
• Mark created component docs as provisioned and omit code references

Example use cases

• Provision a new API rate limiter design and create ADR + provisioned component doc
• Design OAuth support for an existing auth middleware and document the update (provisioned)
• Plan a new background worker component for a service and capture dependencies and behavior
• Document a proposed change to a data ingestion container before any implementation begins
• Create a provisioned component spec to hand off to engineers for later implementation