# adlc-team-skills

Agent skills that give coding agents your team's context at session start, so they stop working like strangers.

## The problem

Coding agents start every session knowing nothing about your team. They don't know your conventions, which patterns you deprecated, or why service X never calls service Y. Developers compensate with personal CLAUDE.md files, but those live on one machine, drift out of date, and don't transfer between teammates or tools.

## What this does

### #1: The agent doesn't know how your team works

`team-boot` runs at session start and injects an *index* of your team's rules, personas, and decisions — names and one-line descriptors, roughly a hundred tokens. Not the rules themselves. When the active task matches a rule, the agent pulls that rule's full text on demand. A task touching SQL loads the SQL rule; nothing else loads.

``` team-boot → auto-runs at session start (event hook), injects the index team-discover → /team-discover for a structured match table team-constitution → interactively define your team's principles team-repair → re-index, conflict scan, freshness check ```

The index lives in a git repo ([team-ai-directives](https://github.com/tikalk/agentic-sdlc-team-ai-directives)) — versioned, reviewed by PR, shared by the whole team.

### #2: The agent guesses instead of asking

LLMs fill ambiguity with invention. `mission-brief` forces a contract first: goal, constraints, non-goals, success criteria — then runs specify → plan → tasks → implement ↔ converge. When the agent gets something wrong, you fix the spec, not the code.

``` mission-brief "add user profile API with JWT" mission-brief --resume # continue an interrupted mission ```

### #3: The maker grades its own work

The `evals` skills build executable evaluation suites (PromptFoo or DeepEval). Anything that can be checked by code gets a binary grader — plain assertions, Tier 1. LLM judges are Tier 2, reserved for what static checks can't v