Updated today
by tikalk
adlc-team-skills
Agent skills for the Agentic SDLC: team lifecycle (team-boot, team-learn, team-init, team-repair), software factory, evals, CDR lifecycle with confidence scoring, and ADR/PDR/ChDR decision records. Works with Claude Code, Codex, OpenCode, Cursor, Copilot, and more.
144 GitHub stars (144)
+4 in 30 days
| Period | New stars |
|---|---|
| Oct 1 | 0 |
| Oct 2 | +1 |
| Oct 3 | 0 |
| Oct 4 | 0 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | 0 |
| Oct 8 | +1 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | 0 |
| Oct 14 | 0 |
| Oct 15 | 0 |
| Oct 16 | 0 |
| Oct 17 | 0 |
| Oct 18 | 0 |
| Oct 19 | +1 |
| Oct 20 | 0 |
| Oct 21 | 0 |
| Oct 22 | 0 |
| Oct 23 | +1 |
| Oct 24 | 0 |
| Oct 25 | 0 |
| Oct 26 | 0 |
| Oct 27 | 0 |
| Oct 28 | 0 |
| Oct 29 | 0 |
| Oct 30 | +1 |
| Oct 31 | 0 |
| Nov 1 | 0 |
| Nov 2 | 0 |
| Nov 3 | 0 |
| Nov 4 | +1 |
| Nov 5 | 0 |
| Nov 6 | −1 |
- 30 skills (30 skills found in its SKILL.md files)
- 2 forks (2 forks)
- Today last update (Last updated today)
Install
Skills CLI
npx skills add tikalk/adlc-team-skills
Asks which skills and agents to install. Just one: npx skills add tikalk/adlc-team-skills --skill architect-analyze — add -g for every project.
Claude Code
git clone https://github.com/tikalk/adlc-team-skillscp -r "adlc-team-skills/skills/architect/architect-analyze" ~/.claude/skills/
Copies the architect-analyze skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add tikalk/adlc-team-skills
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md — showing the first 30 of 52 files.
-
architect-analyze
Use when validating generated or refined architecture artifacts, before feature development, during architecture review, or periodically to detect ADR↔AD drift, completeness gaps, and quality issues.
skills/architect/ on GitHub (opens in a new tab)architect-analyze/ SKILL.md -
architect-boot
Use when architecture work starts or a tech-stack or pattern decision emerges — injects the project ADR index (docs/adlc/memory/adr/, legacy .adlc/memory/adr/ fallback) as session context and suggests the decision for capture via /architect-specify (never writes drafts itself); invoked from team-boot's Class Boots catalog.
skills/architect/ on GitHub (opens in a new tab)architect-boot/ SKILL.md -
architect-clarify
Use when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation.
skills/architect/ on GitHub (opens in a new tab)architect-clarify/ SKILL.md -
architect-implement
Use when accepted ADRs exist and AD.md must be produced or updated as unified architecture documentation.
skills/architect/ on GitHub (opens in a new tab)architect-implement/ SKILL.md -
architect-init
Use when bootstrapping architecture documentation for a brownfield project by reverse-engineering ADRs from an existing codebase.
skills/architect/ on GitHub (opens in a new tab)architect-init/ SKILL.md -
architect-specify
Use when you want guided trade-off analysis, multi-option comparison, or structured architectural decision facilitation before documenting. Class boots only suggest capture — they never write drafts; running this skill writes the lightweight ADR draft.
skills/architect/ on GitHub (opens in a new tab)architect-specify/ SKILL.md -
writing-skills
Use when creating a new skill, editing an existing skill, or verifying skills work before deployment
skills/authoring/ on GitHub (opens in a new tab)writing-skills/ SKILL.md -
change-boot
Use when past-change rationale matters (refactoring unfamiliar code, revert or hotfix analysis, issue-linked commit archaeology, session authors git changes with human-authored messages) — injects the published ChDR index (docs/adlc/memory/chdr/chdr.md, legacy .adlc/memory/chdr.md fallback) as session context; pairs history mining (/change-init) with in-session capture suggested via /change-speci…
skills/change/ on GitHub (opens in a new tab)change-boot/ SKILL.md -
change-clarify
Use when reviewing, accepting, rejecting, or deferring ChDRs mined by change-init, validating inferred decisions against their git and issue evidence before promotion to project memory.
skills/change/ on GitHub (opens in a new tab)change-clarify/ SKILL.md -
change-init
Use when you want guided mining of git history, structured change-story clustering, or comprehensive rationale recovery before documenting. Class boots only suggest capture — for in-session change rationale they suggest /change-specify; this skill mines history and writes the lightweight ChDR draft.
skills/change/ on GitHub (opens in a new tab)change-init/ SKILL.md -
change-publish
Use when accepted ChDRs are ready for promotion from drafts to project memory at docs/adlc/memory/chdr/ and the boot-facing chdr/chdr.md index needs regenerating.
skills/change/ on GitHub (opens in a new tab)change-publish/ SKILL.md -
change-specify
Use when a change rationale just emerged — a revert, hotfix, fix chain, workaround, or abandoned approach — and you want guided facilitation (options, consequences, provenance) before it becomes a ChDR. Not for mining git history (/change-init) or reviewing drafts (/change-clarify); class boots only suggest this skill, they never write drafts.
skills/change/ on GitHub (opens in a new tab)change-specify/ SKILL.md -
evals-analyze
Use when evaluation results need triage and loop-closing — spec failures route to deterministic checks or context rules, generalization failures to the evaluator backlog.
skills/evals/ on GitHub (opens in a new tab)evals-analyze/ SKILL.md -
evals-clarify
Use when draft eval criteria need refining, clustering, and acceptance into the published goldset with an isolated holdout split (goldset.md + goldset.json).
skills/evals/ on GitHub (opens in a new tab)evals-clarify/ SKILL.md -
evals-implement
Use when a published goldset is ready to become executable graders and configs — Python graders and metrics with auto-run unit tests verifying grader correctness.
skills/evals/ on GitHub (opens in a new tab)evals-implement/ SKILL.md -
evals-init
Use when standing up evals/{system}/ for the first time — scaffolds the EDD directory structure, picks PromptFoo or DeepEval by tech stack, and generates a security baseline.
skills/evals/ on GitHub (opens in a new tab)evals-init/ SKILL.md -
evals-specify
Use when you want guided bottom-up error analysis, structured failure taxonomy discovery, or comprehensive trace coding before documenting eval criteria. Class boots only suggest capture — they never write drafts; running this skill writes the lightweight eval draft.
skills/evals/ on GitHub (opens in a new tab)evals-specify/ SKILL.md -
evals-validate
Use when a goldset with graders is ready to run — executes the evaluation pyramid and validates evaluator quality (SLA compliance, TPR/TNR, statistical accuracy).
skills/evals/ on GitHub (opens in a new tab)evals-validate/ SKILL.md -
factory-clean
Use when the user asks to reclaim project disk space or clean up leftovers — inventories worktrees, containers, dependencies, and processes, reclaiming only user-approved items; read-only by default.
skills/factory/ on GitHub (opens in a new tab)factory-clean/ SKILL.md -
factory-deploy
Use when an approved PR head must reach production through a gated release — exact-head merge, staged canary rollout with threshold verdicts, and a SemVer-tagged release with notes plus a monitor handoff. Triggers on post-merge rollout work; not for continuous monitoring, review depth, or infra provisioning.
skills/factory/ on GitHub (opens in a new tab)factory-deploy/ SKILL.md -
factory-init
Use when onboarding a brownfield repo onto ADLC end-to-end, or running the recurring PDR↔ADR↔ChDR↔code alignment sweep (--refresh).
skills/factory/ on GitHub (opens in a new tab)factory-init/ SKILL.md -
factory-intent
Use when orchestrating an intent lifecycle (product + architecture lanes, two scope-pinned gates, joint build-and-verify) to generate PRD.md and AD.md from one Mission Brief.
skills/factory/ on GitHub (opens in a new tab)factory-intent/ SKILL.md -
factory-learn
Use when coordinating continuous improvement loops (team-levelup + change + evals feedback + cleanup) targeting team-ai-directives — includes build-to-delete pruning and promote-to-check.
skills/factory/ on GitHub (opens in a new tab)factory-learn/ SKILL.md -
factory-mission
Use when executing a spec-gated mission from the queue — inner loop specify → plan → implement ↔ converge with tracker integration, worktree isolation, and a circuit breaker.
skills/factory/ on GitHub (opens in a new tab)factory-mission/ SKILL.md -
factory-orchestrator
Use when work arrives at the software factory at any lifecycle stage — a new request, an informational question, a CI failure on a delivered PR, review findings, a merge notification, or a reply to a factory question — and must be routed to the right factory skill, human gate, or follow-up context.
skills/factory/ on GitHub (opens in a new tab)factory-orchestrator/ SKILL.md -
factory-queue
Use when managing mission brief intake — triage, AI-assisted advisory scoring, gating label stamping, and milestones or epics generation (plan mode).
skills/factory/ on GitHub (opens in a new tab)factory-queue/ SKILL.md -
factory-review
Use when reviewing PRs for severity-ranked policy compliance against REVIEW.md, babysitting agent PRs to merge, or self-healing Important findings before a human sees them.
skills/factory/ on GitHub (opens in a new tab)factory-review/ SKILL.md -
factory-runbook
Use when a factory run must post its changes — check out the run branch, commit a step's allowlisted paths, push only that branch, and open or reuse one draft MR/PR with milestone/assignee ownership. Also the shared home for factory run contracts (executor, tracker integration, lanes, brief and provider templates).
skills/factory/ on GitHub (opens in a new tab)factory-runbook/ SKILL.md -
factory-setup
Use when configuring the factory tracker provider for a repo (first factory run, missing .adlc/issues-provider.yml), verifying provider wiring, or switching trackers.
skills/factory/ on GitHub (opens in a new tab)factory-setup/ SKILL.md -
factory-tickets
Use when the user asks for their active worklist — open PRs with next actionable move, merged work not yet closed, takable tickets, and blocked work, classified by next move.
skills/factory/ on GitHub (opens in a new tab)factory-tickets/ SKILL.md
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.