360 Secure SkillHub
360 安全技能中心

team-diagnose

面向 adlc-team-skills 装配故障的证据优先诊断流程：按顺序执行五项检查（配置、jq 依赖、team-boot 处理器、安装同步、注入侧），在首个失败处停止、修复后重跑，最终给出失败检查编号、命令原始输出与归属仓库路由，并附报告格式与红旗清单。

分类：开发
tikalk
热度 0.00
最近更新 2026-11-06 00:25:30

安装

发给 Agent
帮我安装这个技能：npx secure-skills-cli add tikalk/adlc-team-skills/team-diagnose
兼容性
通用兼容
联网要求
联网要求未确认
数据出网
数据不出本机
Metadata
name
team-diagnose
description
Use when the team context did not appear at session start, a skill failed to trigger, the install behaves unexpectedly, or someone asks why a session ran without team rules — walks the failure chain with commands and evidence before any conclusion.

team-diagnose

Scope rule: scripts stay skill-local — never source a script from another skill. For another skill's operations, invoke that skill (e.g. architect-clarify, product-clarify, team-boot) via the Skill tool; for its documents, follow the Requires line. scripts/ and references/ below are relative to this skill. {REPO_ROOT} denotes the project root (where .adlc/ lives).

Overview

Evidence-first diagnosis of broken adlc-team-skills wiring. The chain has exactly five links, each checkable with one command — a diagnosis without command output is a guess, and guesses get pasted into bug reports.

Boundary: this repo owns .events.json and the boot scripts' output. The injection side (dispatchers, generated per-agent plugins) is owned by adlc-cli — the docs/event-hook-contract.md file in the adlc-team-skills repo draws the line. Diagnose up to it, then route.

When to Use

  • Team context missing at session start (no Team Context & Decisions section).
  • A rule that should have matched didn't load.
  • Install behaves unexpectedly after an update.

When NOT to use: for application bugs unrelated to the team-context chain, or for skill behavior debates (that's a goldset/eval question).

Core Process

Run the checks in order — stop at the first failure, fix, re-run:

# Symptom area Check (run it) Green means
1 Not configured cat .adlc/init-options.json A team_ai_directives path that exists
2 Missing tool command -v jq jq on PATH (skills registry needs it)
3 Broken handler Invoke the team-boot skill The directives index on stdout, wrapped in EXTREMELY_IMPORTANT
4 Stale install pytest tests/unit/test_generated_artifacts_sync.py -q (in the skills repo) or compare skills/**/SKILL.md vs installed skill names Mirror matches source
5 Injection side Generated plugin present and loaded for the agent? If 1–4 are green and the session still lacks context → adlc-cli's territory — file there with the outputs of checks 1–4 attached

For "a rule didn't load" specifically: confirm the session began with the index (check 3's content), then check the task actually matched the rule's descriptor — on-demand pull is match-driven, not mind-reading.

Whole-loop check: scripts/acceptance-test.sh scratch-installs and asserts the chain end-to-end (add --live for a real agent session).

Report format

For a bug report, include: the failing check number, the command, its verbatim output, agent name/version, and how the repo was installed (npx skills add vs adlc-cli). No scrubbed narrative — raw output.

Red Flags

  • Concluding before running a command — every check is one command.
  • "Reinstall everything" before reading check 3's output.
  • Blaming a skill's content when check 1–3 failed (config, not skills).
  • Filing injection-side bugs in adlc-team-skills (check 5 routes them).

All of these mean: run the checks, then report.

Verification

A diagnosis is done when:

  • Checks 1–4 each ran with output captured (or 5 routed with evidence)
  • The failing link is named with its command output
  • The report routes to the owning repo