User wants to set up a new Knowledge-as-Code knowledge base from scratch.
Ask the user one question at a time:
- "What domain is this knowledge base for?" (marketing, product, HR, customer success, or a combination)
- "What are the most common outputs you need to generate?" (emails, proposals, job descriptions, etc.)
- "What existing knowledge do you have that we could convert?" (docs, decks, guides — handle via
kac-convertworkflow later)
Create the following structure in the user's working directory or specified location:
knowledge/
├── foundations/
├── techniques/
└── README.md
The README should include:
# [Organization/Project] Knowledge Base
Knowledge-as-Code repository. Structured domain knowledge for AI-assisted output generation.
## How this works
**Foundations** (in `foundations/`) are validated claims about reality: our customers, competitors, product, messaging, voice. They state what is true. They never instruct what to do.
**Techniques** (in `techniques/`) encode how to approach types of situations. They reference foundations and specify reasoning approaches, not templates.
**Outputs** are generated on demand from Foundations + Techniques + Context. They are never stored here.
## Available Modules
### Foundations
[List will grow as modules are added]
### Techniques
[List will grow as techniques are added]
## Review Cadence
| Module Type | Frequency |
|---|---|
| Competitive intelligence | Monthly |
| ICP and messaging | Quarterly |
| Product capabilities | Each significant release |
| Brand voice, culture | Semi-annually |Based on the domain and common outputs, recommend 3-5 foundation files to create first. Prioritize by: which foundations would be referenced by the most outputs?
Typical starters for marketing/sales:
foundation-icp-[primary-segment].mdfoundation-messaging-core.mdfoundation-brand-voice.mdfoundation-competitor-[top-competitor].mdfoundation-product-capabilities.md
Offer to begin authoring the first foundation file immediately (switch to kac-author-foundation workflow).