Adlc Team Skills — Development skill for Claude Code

adlc-team-skills

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

Table of contents

• How it works
• The developer journey
• The problems these skills solve
• Install
• The software factory
• Universal orchestration
• What's inside
• Philosophy
• When something goes wrong
• Security
• Contributing
• Reference details
• Release process
• License

How it works

It starts the moment you open a session. `team-boot` fires via the `session_start` event hook and injects a lean index of your team's rules — roughly a hundred tokens of names and one-line descriptors. 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 does.

The index lives in a git repo — your [team-ai-directives](https://github.com/tikalk/agentic-sdlc-team-ai-directives) — versioned, reviewed by PR, shared by the whole team. No more personal CLAUDE.md files that live on one machine, drift out of date, and don't transfer between teammates or tools.

When you ask the agent to build something, it doesn't jump to code. `factory-mission` forces a contract first — goal, constraints, non-goals, success criteria (the mission-brief format) — then walks `specify → plan → implement ↔ converge`, with gates, a circuit breaker, resume, and an audit trail. When a session surfaces a hard-won fix, `team-levelup` extracts it as a Context Directive Record (CDR), scores it by confidence, and publishes accepted CDRs back to the team repo. Usage data and confidence scores live in the `adlc` orphan branch — the next session starts smarter and CDRs rank by real u