tikalk/adlc-team-skills

team-discover

Use when explicit manual re-discovery of team context modules is wanted beyond the injected CDR index (/team-discover) — produces a structured match table with relevance assessments.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/tikalk/adlc-team-skills --skill team-discover

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

team-discover

Overview

The CDR index is injected into the system prompt at session start by team-boot. The LLM natively matches CDR descriptors against the current task and reads full module bodies on demand. This native matching happens per prompt without invoking this skill.

Use /team-discover when you want a structured discovery table with explicit relevance assessments — for example, when starting a complex feature or verifying which directives apply.

Relationship to team-boot

team-boot is the session bootstrap: it injects the CDR index into the system prompt via the session_start event hook. Per-prompt discovery matching is native — the LLM matches the injected CDR index against the current message on its own, so team-boot does not invoke this skill as part of its bootstrap loop.

/team-discover is user-invoked: run it when you want an explicit, structured re-scan with a relevance-rated table (complex features, audits, or verifying which directives apply). It is not required for normal operation.

Process

  1. Extract domain, technology, patterns, and actions from the task.
  2. Scan the CDR index for matching entries.
  3. Assess relevance: High / Medium / Low.
  4. Read full module bodies for High-relevance entries.
  5. Output:
IDModuleTypeDescriptorRelevance
CDR-2026-003context_modules/personas/admin.mdPersonaAdmin personaHigh
  1. Include PDR/ADR/ChDR matches from project indexes if relevant.
  2. Include: _Searched N CDRs, M PDRs, K ADRs, C ChDRs, J matches found._

Absent Context

If no CDR index was injected at session start: report Searched 0 CDRs — index not injected (unconfigured project or hook failure), reading workspace memory directly, proceed against docs/adlc/memory/ on disk, and continue the task. Never present on-disk fallback rows as injected context. Recovery: run /team-diagnose.

Unconfigured projects

If team AI directives are not configured, invoke team-setup.

按任务相关推荐

来自同一仓库

更多 Skills

全部 Skills