Agent skills that bring team coding standards to Claude Code and Codex Tikal released ADLC Team Skills, an open-source team layer for the Twelve-Factor Agentic SDLC, designed to bring team coding standards to AI coding agents such as Claude Code, Codex, OpenCode, Cursor, and GitHub Copilot. The toolkit includes slash commands, session-start event hooks, and a companion repository for version-controlled team directives, aiming to replace chaotic 'vibe coding' with compliant, accountable AI-assisted development. Stop Vibe Coding in Silos. Build a Shared Cognitive Layer for Your Engineering Team. Individual prompt hacks create quick wins for solo developers, but when scaled across a team, "vibe coding" leads to chaotic technical debt, context rot, unreviewable PRs, and lost code ownership. Speed is solved; Trust and Verification is the new bottleneck in AI engineering. ADLC Team Skills tikalk/adlc-team-skills is the open-source Team Layer of the Twelve-Factor Agentic SDLC . It turns AI agents from isolated guessers into compliant, accountable team members that share your team's constitution, product strategy, architectural standards, and evaluation benchmarks. Team AI Directives tikalk/agentic-sdlc-team-ai-directives https://github.com/tikalk/agentic-sdlc-team-ai-directives is the companion repository that holds your team's version-controlled context modules constitution, rules, personas, examples , CDR index, and skills manifest. Install skills + generate slash commands + wire session start events npx adlc-skills-cli add tikalk/adlc-team-skills -a opencode Or with npx skills only skills without commands/events npx skills add tikalk/adlc-team-skills -a claude -g Works out of the box with any agent supporting the Agent Skills standard https://agentskills.io — Claude Code, Codex, OpenCode, Cursor, GitHub Copilot, and others. Slash commands + events: adlc-skills-cli https://github.com/tikalk/adlc-skills-cli wraps npx skills add and additionally generates /name slash commands and wires session start event hooks via .events.json for 9 coding agents. Skills repos without .events.json get commands only. Universal orchestration: mission-brief auto-discovers skills from any source mattpocock/skills, addy osmani/agent-skills, superpowers, spec-kit, or your own and dynamically wires them into the mission pipeline. No vendor lock-in. team-boot auto-runs at session start via the event hook. On an unconfigured project it outputs a warning telling the user to run /team-setup . team-setup is also available on demand: npx adlc-skills-cli add tikalk/adlc-team-skills -a opencode install skills + commands + events Then choose Mode 3 — Scaffold new empty team-ai-directives , or Mode 1 — Clone from GitHub to fork tikalk/agentic-sdlc-team-ai-directives https://github.com/tikalk/agentic-sdlc-team-ai-directives : team-setup → pick destination default ./team-ai-directives + team name → scaffolds README / AGENTS.md / CDR.md / .skills.json / constitution placeholder / OKF index files + git init team-constitution → interactively replace the placeholder with your real principles team-boot auto → assembles constitution + CDR index + PDR/ADR indexes + skills registry into the system prompt at session start Already have a directives repo? team-setup offers three other modes: Mode 1 — Clone from GitHub e.g. fork tikalk/agentic-sdlc-team-ai-directives Mode 2 — Point to existing local path wire a repo you already have Mode 4 — Already configured verify an existing setup | Without ADLC Vibe Coding | With ADLC Team Skills | |---|---| Session starts from zero: Agent knows nothing about your architecture, team rules, or deprecated patterns. | Auto-bootstrapped context: team-boot auto-loads your Team Constitution & active decisions on session start. | Prompt wall bloat: Dumping a 10,000-token prompt wall wastes tokens and causes model instruction drift. | Progressive disclosure: team-boot injects a ~100-token index; team-discover fetches only the 1–2 rules relevant to the task. | Ambiguity leads to guessing: Agent invents functions or database schema instead of asking questions. | Contract-first specs: mission-brief defines Goal, Constraints, Non-Goals, and Success Criteria before writing code. | Learnings evaporate: Debugging fixes and newly discovered edge cases disappear when the chat ends. | Closed feedback loop: levelup-specify extracts session execution traces and commits new rules directly to Git. | Silent regressions: Prompt edits or base model updates silently degrade agent output. | Verification-first evals: Automated LLM judges and binary graders test code against business risks before human review. | THE GREAT FILTER Human Team Lead Macro-Review ▲ │ ┌──────────────────┴──────────────────┐ │ Pillar 4: Governance & Evals │ │ Tier 1 Fast Checks + LLM Judges │ └──────────────────▲──────────────────┘ │ ┌──────────────────┴──────────────────┐ │ Pillar 3: Spec-Driven Workflow │ │ Contract-First Mission Pipeline │ └──────────────────▲──────────────────┘ │ ┌──────────────────┴──────────────────┐ │ Pillar 2: Product & Architecture │ │ Product PDRs + Architecture ADRs │ └──────────────────▲──────────────────┘ │ ┌───────────────────┴───────────────────┐ │ Pillar 1: Strategy & Team Directives│ │ team-boot / levelup / CDR repository │ └───────────────────────────────────────┘ Put the team at the center of your AI strategy. Instead of individual developers hoarding prompt shortcuts on local machines, team standards live in a version-controlled Git repository team-ai-directives https://github.com/tikalk/agentic-sdlc-team-ai-directives . : Auto-runs at session start via the event hook, assembling the team constitution, CDR index, PDR/ADR indexes, and skill registry into the system prompt. team-boot Progressive Disclosure No Token Waste : Instead of dumping massive prompt walls into every session, team-boot injects a compact ~100-token index. team-discover loads full rule bodies only when relevant to the active task.: Interactively define, review, or amend your engineering team's core principles. team-constitution : Re-index CDR.md, scan for rule conflicts, and verify directive freshness. team-repair team-boot → assembles constitution + CDR index + PDR/ADR + skills into system prompt team-discover → manual re-scan for structured discovery tables /team-discover team-constitution → create or amend the team constitution interactively team-repair → re-index CDR.md, scan for conflicts, verify freshness Without documented decisions, every implementation session re-derives or misinterprets product intent and architectural rules. Product Decision Records : Capture product decisions as individual PDR files, resolve ambiguities through an interactive clarification workflow, and compile them into a self-contained product- PRD.md . Architectural Decision Records : Reverse-engineer or define architectural decisions using Rozanski & Woods viewpoints Functional, Security, Deployment, Performance and compose them into a unified architect- AD.md .: Track milestone progress across four layers of truth — decisions PDRs , execution live issues via MCP , code evidence, and milestone gates. product-roadmap Product: product-init → product-clarify → product-implement → product-analyze Architecture: architect-init → architect-clarify → architect-implement → architect-analyze Roadmap: product-roadmap tracks PDRs + issues + code + gates AI is an obsessive guesser — when faced with ambiguity, it invents solutions instead of asking questions. Move from a Conversational model to a Contract model. : The team's autonomous pipeline runner. Takes a feature prompt, derives a formal contract Goal, Constraints, Non-Goals, Success Criteria , generates an ordered step list, and walks a mission-brief specify → plan → tasks → implement ↺ converge loop to completion. Mantra: "Debug the Spec, Not the Code" : When an agent makes a mistake, don't just patch the code — add the missing constraint to the specification so the mistake is never repeated. mission-brief "add user profile API with JWT" ├── Phase 2: Brief Goal, Constraints, Non-Goals, Success Criteria ├── Phase 3: Route Classification spec | change | quick ├── Phase 4: Discovery auto-wires local installed skills & SDD frameworks └── Phase 5: Execute specify → plan → tasks → implement ↺ converge Never let the agent that wrote the code decide if the code is good. "Separate the Maker from the Checker." : Build application-level evaluation suites PromptFoo or DeepEval using Eval-Driven Development EDD . Runs Tier 1 fast checks + Tier 2 LLM judge subagents to test code against defined business risks evals skills before human macro-review in The Great Filter .: Capture session wins into permanent team memory. levelup levelup-specify extracts session execution traces and commits them to Git as reusable rules Context Directive Records — CDRs . "Build to Delete" : Prune outdated rules and prompt scaffolding as underlying foundation models improve using team-repair --build-to-delete . LevelUp: levelup-init → levelup-specify → levelup-clarify → levelup-publish Evals: evals-init → evals-specify → evals-clarify → evals-implement → evals-validate → evals-analyze Factor XII — Build to Delete. Factor XIII — Loop Engineering. mission-brief acts as an open, vendor-agnostic orchestrator across all popular agent skill repositories and Spec-Driven Development SDD frameworks: | SDD Framework / Skill Source | Supported Workflows | |---|---| Agentic SDLC Spec-Kit tikalk/agentic-sdlc-spec-kit | Twelve-Factor SDD pipeline, native specify CLI discovery, contract verification | Spec-Kit specify cli | Native command discovery and specification templates | OpenSpec | Structured edge-case contracts and verification schemas | | /tdd , /grill-me , /grill-with-docs , /code-review , /prototype | | Exit criteria checklists, quality gate skills | | Developer tooling & workflow skills | ADLC Team Skills this repo | product-specify , architect-specify , evals-validate , levelup-specify | Your Custom Skills | Any skill following the SKILL.md standard | Discovery — At mission start, mission-brief scans all skills directories .claude/skills , .agents/skills , etc. and reads every SKILL.md frontmatter to build a vendor-agnostic inventory of installed skills with their names and descriptions. LLM-decided routing — Each step's delegation prompt includes the full skills inventory. The subagent decides which skill if any fits the current phase — the LLM matches, not a brittle lookup table. Graceful fallback — If no skill matches, the subagent executes directly. If a skill matches, it's invoked. Either way, the mission pipeline continues. Install skills from multiple team or community sources npx skills add mattpocock/skills npx skills add tikalk/adlc-team-skills mission-brief discovers and routes them automatically mission-brief "add user profile API with JWT" Skills are organized under the four pillars of the Twelve-Factor Agentic SDLC, flattened directly under the skills/ directory: skills/ ├── architect/ architect- 5 skills ├── product/ product- 6 skills + product-templates/ ├── levelup/ levelup- 4 skills + levelup-helpers.{sh,ps1} ├── mission-brief/ core SDD orchestrator 1 skill ├── evals/ evals- 6 skills + evals-templates/ ├── tech-radar/ tech-radar- 1 skill + resources/radar.json ├── workspace/ workspace 1 skill — multi-repo coordination └── team/ team- 6 skills + team-helpers.{sh,ps1} This places every single skill exactly 2 levels deep, fully resolving the default depth limit of the skills CLI and ensuring all skills install out of the box. — Bootstrap session: assembles constitution, CDR index, PDR/ADR indexes, and skill registry into the system prompt at session start. Outputs a warning to run team-boot /team-setup on unconfigured projects.— Manually re-scan team context modules and produce a structured discovery table. Available via team-discover /team-discover .— Clone, scaffold, or configure a team AI directives repository. Model-invoked by team-setup team-boot self-install and available on demand. Say "Set up team directives for this project." — Create or amend the team constitution interactively. Say "Create our team constitution" or "Amend our team principles." team-constitution — Re-index CDR.md, .skills.json, AGENTS.md; health check; conflict scan; freshness verification. Say "Check our team directives health" team-repair --health-only , "Repair our CDR index," or "Scan for rule conflicts" --conflicts .— Browse and install team skills from the team AI directives. Say "Show me available team skills." team-skills All user-invoked. Capture and publish reusable patterns to team-ai-directives, including paired directive compliance evals. — Brownfield CDR discovery from existing codebase, including paired eval CDRs from code patterns. Say "Discover directives from this codebase." levelup-init — Extract CDRs and paired eval CDRs from the current session. Say "Extract lessons from this session." levelup-specify — Review, accept, reject, or defer pending CDRs. Evals regression gate runs by default. Say "Review pending CDRs." levelup-clarify — Compile accepted CDRs into team directives artifacts, evals goldensets, and draft PR. Say "Publish accepted CDRs" or "Build one skill from a CDR" levelup-publish --skill CDR-NNN . All user-invoked. Document product decisions as individual PDRs and compile into a self-contained PRD.md. — Brownfield PDR discovery from existing codebase and documentation. Say "Discover product decisions from this codebase." product-init — Greenfield PDR creation through interactive product exploration. Say "Let's define our product strategy." product-specify — Refine, validate, and approve PDRs before PRD generation. Say "Review our product decisions." product-clarify — Generate PRD.md from accepted PDRs multi-agent DAG orchestration . Say "Generate our PRD." product-implement — Read-only PDR↔PRD consistency and quality analysis. Say "Analyze our product docs." product-analyze — Track milestone progress: decision status, live issues via MCP, code evidence, and gates. Say "Show roadmap progress." product-roadmap All user-invoked. Create and manage Architecture Decision Records using the Rozanski & Woods methodology. — Reverse-engineer ADRs from an existing codebase brownfield . Say "Reverse-engineer architecture from this codebase." architect-init — Create ADRs from a PRD or feature description greenfield . Say "Create ADRs from this PRD." architect-specify — Refine and validate existing ADRs. Say "Refine and validate my ADRs." architect-clarify — Generate an Architecture Description AD.md from accepted ADRs. Say "Generate AD.md from my ADRs." architect-implement — Check ADR↔AD consistency and architecture quality. Say "Analyze architecture consistency." architect-analyze All user-invoked. Build and maintain application-level evaluation suites following EDD Eval-Driven Development principles PromptFoo or DeepEval . — Initialize evaluation directory structure evals-init evals/{system}/ with security baseline. Say "Initialize my evaluation harness."— Extract eval criteria from specs and production failure traces bottom-up open coding . Say "Specify evaluation criteria from this failure log." evals-specify — Cluster related patterns, refine criteria, isolate 20% holdout split, and publish goldset. Say "Clarify and accept my draft evaluations." evals-clarify — Generate executable graders and test configs, automatically running unit tests to verify evaluator correctness. Say "Generate graders from the goldset." evals-implement — Run the evaluation pyramid Tier 1 fast checks + Tier 2 LLM judges and compute quality metrics TPR/TNR, SLA headroom . Say "Validate my evaluation suite." evals-validate — Deep-analyze trajectory failure traces, routing spec-level failures to evals-analyze levelup-specify rules and generalization failures to backlog. Say "Analyze evaluation failures." User-invoked. Structure a feature description into a Mission Brief and run it end-to-end with any installed SDD skill set. — Takes a description, structures it into a Mission Brief goal, constraints, success criteria , generates an ordered step list with prompts that trigger installed SDD skills, and walks those steps to converged implementation. Sync gated or mission-brief --async ungated, checkpoint across sessions . Say "Build this feature end to end" or mission-brief "add dark mode" . Resume with mission-brief --resume . Model-invoked. Grounds tech stack choices in Tikal's Israeli Tech Radar. — Discovers technologies implied by the prompt, matches them against the Tikal Tech Radar tech-radar-context radar.json , and injects a context table with each technology's adoption ring Keep / Start / Try / Stop , quadrant, and Tikal's "Why?" opinion — plus Tikal-aligned alternatives for anything on Stop . Auto-triggered whenever a technology, framework, database, library, or cloud tool is being chosen or evaluated. Fetches the live radar best-effort and falls back to a bundled snapshot at resources/radar.json . User-invoked. Multi-repo workspace coordination for shared team context. — Discover child repos at depth 1 and optionally link them as Git submodules, creating a multi-repo workspace analogous to VS Code's workspace .code-workspace . The parent repo holds shared PDRs, ADRs, and CDRs under .adlc/ created by product-specify , architect-specify , levelup-specify ; child implementation repos are linked for unified context. Commands: /workspace discover , /workspace --link register submodules , /workspace --status audit: branch, dirty, unpushed, SHA drift . No workspace.yml — pure auto-discovery by convention. Say "Set up multi-repo workspace" or /workspace --link . Output File Layout All skills write to .adlc/ project root and the team AI directives repo. Team Directives inside the team AI directives repository : AGENTS.md — agent instructions loading order, rules, skills CDR.md — index of approved context contributions .skills.json — skills manifest schema v2.0.0 .mcp.json.example — MCP servers config example context modules/constitution.md — team constitution OKF frontmatter context modules/{rules,personas,examples}/ / .md — context modules context modules/{type}/index.md — progressive disclosure per concept type context modules/{type}/log.md — chronological change log per concept type skills/{name}/SKILL.md + .skills-entry.json — published team skills evals/{directive-id}/goldset.md + goldset.json — directive compliance goldensets LevelUp inside .adlc/ of the target project : .adlc/drafts/cdr/CDR-{NNN}.md — proposed/discovered CDRs including eval CDRs .adlc/drafts/cdr/cdr.md — auto-generated CDR index .adlc/init-options.json — team AI directives path config Product inside .adlc/ and repo root : .adlc/drafts/pdr/PDR-{NNN}.md — proposed/discovered PDRs .adlc/drafts/pdr/pdr.md — auto-generated PDR index .adlc/memory/pdr/PDR-{NNN}.md — accepted/completed PDRs .adlc/memory/pdr/pdr.md — accepted PDR index .adlc/product/sections/{feature-area}/{section}.md — PRD section build artifacts .adlc/product/state.json — DAG execution state PRD.md — Product Requirements Document repo root Architecture inside .adlc/ and repo root : .adlc/drafts/adr/ADR-{NNN}.md — proposed/discovered ADRs .adlc/drafts/adr/adr.md — auto-generated ADR index .adlc/memory/adr/ADR-{NNN}.md — accepted ADRs .adlc/memory/adr/adr.md — accepted ADR index AD.md — Architecture Description repo root .adlc/architect/ — per-view DAG artifacts Missions inside .adlc/ of the target project : .adlc/workflow/workflow-config.yml — mission execution/supervision/budgets config .adlc/workflow/.mission-state.json — step list, completed steps, brief, discovery results .adlc/workflow/runs/