Distribute your AI standards with confidence
Publish skills, prompts, and rules once — then distribute them to every team and tool with built-in approval, versioning, and drift detection.
GOVERNANCE MODEL
Four roles that make distribution trustworthy
ADLC Forge maps to how teams actually distribute AI standards — publishers set the bar, consumers pull with confidence.
- Product Domain · Publisher
-
Product Publisher
e.g. Head of Product Ops
Governs org-wide product assets
- Product Domain · Consumer
-
Product Consumer
e.g. Product Manager
Browses catalog, pulls approved assets
- Engineering Domain · Publisher
-
Engineering Publisher
e.g. Staff Engineer
Governs engineering-domain assets
- Engineering Domain · Consumer
-
Engineering Consumer
e.g. Developer
CLI pull, init, CLAUDE.md URI
ASSET TAXONOMY
Seven asset types, purpose-built
Every artifact your team creates for Claude has a type. ADLC Forge governs each one differently.
Skill
A reusable AI capability unit — a CLAUDE.md action that Claude can execute on demand.
Command
A slash command for Claude Code — callable by name during a conversation.
Template
A scaffolding template for new projects or files — consistent starting points.
Prompt
A standalone prompt for a specific task — reusable across teams and products.
Eval Set
A set of test cases for evaluating AI output quality — quality gates for your prompts.
Playbook
A multi-step workflow combining multiple asset types — orchestrated sequences.
Rules File
A .cursorrules or CLAUDE.md configuration — governs how AI behaves in a codebase.
Two views, two audiences
Consumers browse and pull from the catalog. Publishers manage distribution health across products.
• Assets organized by ADLC phase
• Searchable with version and status visible
• One-click pull into any product
• Deployment health across all products
• Drift detection at a glance
• Version pinning per product scope
SCOPE HIERARCHY
Complementary to Anthropic's architecture
Anthropic defines four scope levels for Claude configuration. ADLC Forge governs which assets are approved at each level.
Enterprise (org-wide)
ADLC Forge manages
Project
ADLC Forge manages
User
ADLC Forge distributes to
Conversation
Assets active here
CLI
First-class terminal experience
Engineers pull approved assets directly into their environment. No context-switching, no manual downloads.
ADLC Forge vs. copy-paste distribution
What changes when you stop copy-pasting and start distributing.
| Capability | Copy-Paste Distribution | ADLC Forge |
|---|---|---|
| Approval workflow | PR review (ad hoc) | Structured phase gates |
| Drift detection | None | Automatic per-product |
| Version pinning | Git tags / branches | Semantic per scope level |
| Onboarding time | Manual repo clone + docs | adlc-forge init (one command) |
| Audit trail | Git log (unstructured) | Per-asset event history |
| PM visibility | Requires Git access | Built-in dashboard |
Approval workflow
PR review (ad hoc)
Structured phase gates
Drift detection
None
Automatic per-product
Version pinning
Git tags / branches
Semantic per scope level
Onboarding time
Manual repo clone + docs
adlc-forge init (one command)
Audit trail
Git log (unstructured)
Per-asset event history
PM visibility
Requires Git access
Built-in dashboard