adlc-team-skills

In the author's own words, from each skill's SKILL.md — showing the first 30 of 44 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/architect-analyze/SKILL.md on GitHub (opens in a new tab)

• architect-boot

  Use when architecture work starts or a tech-stack or pattern decision emerges — injects the project ADR index (.adlc/memory/adr/) as session context and pairs the decision with capture via /architect-specify; invoked from team-boot's Class Boots catalog.

  skills/architect/architect-boot/SKILL.md on GitHub (opens in a new tab)

• architect-clarify

  Use when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation.

  skills/architect/architect-clarify/SKILL.md on GitHub (opens in a new tab)

• architect-implement

  Use when accepted ADRs exist and AD.md must be produced or updated as unified architecture documentation.

  skills/architect/architect-implement/SKILL.md on GitHub (opens in a new tab)

• architect-init

  Use when bootstrapping architecture documentation for a brownfield project by reverse-engineering ADRs from an existing codebase.

  skills/architect/architect-init/SKILL.md on GitHub (opens in a new tab)

• architect-specify

  Use when you want guided trade-off analysis, multi-option comparison, or structured architectural decision facilitation before documenting. Optional for routine capture — team-boot writes lightweight ADR drafts directly.

  skills/architect/architect-specify/SKILL.md on GitHub (opens in a new tab)

• writing-skills

  Use when creating a new skill, editing an existing skill, or verifying skills work before deployment

  skills/authoring/writing-skills/SKILL.md on GitHub (opens in a new tab)

• 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 (.adlc/memory/chdr.md) as session context; pairs history mining (/change-init) with routine capture (direct-write drafts clarified via /change-clarify); invoked from team-boot's…

  skills/change/change-boot/SKILL.md on GitHub (opens in a new tab)

• 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/change-clarify/SKILL.md on GitHub (opens in a new tab)

• change-init

  Use when you want guided mining of git history, structured change-story clustering, or comprehensive rationale recovery before documenting. Optional for routine capture — team-boot writes lightweight ChDR drafts directly.

  skills/change/change-init/SKILL.md on GitHub (opens in a new tab)

• change-publish

  Use when accepted ChDRs are ready for promotion from drafts to project memory at .adlc/memory/chdr/ and the boot-facing chdr.md index needs regenerating.

  skills/change/change-publish/SKILL.md on GitHub (opens in a new tab)

• 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/evals-analyze/SKILL.md on GitHub (opens in a new tab)

• 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/evals-clarify/SKILL.md on GitHub (opens in a new tab)

• 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/evals-implement/SKILL.md on GitHub (opens in a new tab)

• 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/evals-init/SKILL.md on GitHub (opens in a new tab)

• evals-specify

  Use when you want guided bottom-up error analysis, structured failure taxonomy discovery, or comprehensive trace coding before documenting eval criteria. Optional for routine capture — team-boot writes lightweight eval drafts directly.

  skills/evals/evals-specify/SKILL.md on GitHub (opens in a new tab)

• 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/evals-validate/SKILL.md on GitHub (opens in a new tab)

• factory-architect

  Use when orchestrating an architecture lifecycle (specify/init → clarify → implement → analyze) to generate or maintain AD.md.

  skills/factory/factory-architect/SKILL.md on GitHub (opens in a new tab)

• 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/factory-clean/SKILL.md on GitHub (opens in a new tab)

• 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/factory-init/SKILL.md on GitHub (opens in a new tab)

• factory-learn

  Use when coordinating continuous improvement loops (team-learn + change + evals feedback + cleanup) targeting team-ai-directives — includes build-to-delete pruning and promote-to-check.

  skills/factory/factory-learn/SKILL.md on GitHub (opens in a new tab)

• 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/factory-mission/SKILL.md on GitHub (opens in a new tab)

• factory-product

  Use when orchestrating a product lifecycle (specify/init → clarify → implement → analyze) to generate or verify PRD.md.

  skills/factory/factory-product/SKILL.md on GitHub (opens in a new tab)

• 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/factory-queue/SKILL.md on GitHub (opens in a new tab)

• 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/factory-review/SKILL.md on GitHub (opens in a new tab)

• 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/factory-tickets/SKILL.md on GitHub (opens in a new tab)

• product-analyze

  Use when checking PDR↔PRD consistency after /product-implement or periodically to detect drift, PDR quality issues, cross-PDR conflicts, and staleness.

  skills/product/product-analyze/SKILL.md on GitHub (opens in a new tab)

• product-boot

  Use when product or feature work starts, or a PDR-worthy decision (scope, persona, monetization) emerges — injects the PDR index (.adlc/memory/pdr/) as session context and pairs the decision with capture via /product-specify; invoked from team-boot's Class Boots catalog.

  skills/product/product-boot/SKILL.md on GitHub (opens in a new tab)

• product-clarify

  Use when PDRs need refinement, conflict detection, or approval to Accepted status before /product-implement.

  skills/product/product-clarify/SKILL.md on GitHub (opens in a new tab)

• product-implement

  Use when accepted PDRs exist and PRD.md must be generated or updated.

  skills/product/product-implement/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• agentic-awesome-skillsby sickn33 AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, bac… 47.7k stars · 30 skills
• khazix-skillsby KKKKhazix 数字生命卡兹克开源的 AI Skills 合集 | Agent Skills: leader（帮你定义目标）, neat-freak 洁癖, hv-analysis, khazix-writer & more — Claude Code, Codex & 40+ agents 21.4k stars · 6 skills
• superpowers-zhby jnMetaCode 🦸 AI 编程超能力 · 中文增强版 — superpowers（250k+ ⭐）完整汉化 + 4 个中国原创 skills，让 Claude Code / Copilot CLI / Hermes Agent / Cursor / Windsurf / Kiro / Gemi… 8.3k stars · 20 skills
• skillby anbeime 收录最全、更新最快的技能Skills商店：精选原创技能包（涵盖文档处理、内容创作、编程开发、机器学习、自动化工作流），全部打包好可直接安装使用！同时自动抓取GitHub上万个Skills项目，按分类、更新时间、Star数量整理。The most comprehensive an… 8.1k stars · 29 skills
• gentle-aiby Gentleman-Programming Gentle-AI configures the AI coding agents you already use: Claude Code, Cursor, OpenCode, Codex, Pi, and more. Choose persistent memory, Or… 7.8k stars · 20 skills
• openrigby mvschwarz Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work. 7.5k stars · 30 skills