360 Secure SkillHub
360 安全技能中心

team-init

面向存量代码库（brownfield）的团队知识初始化 Skill：先用环境脚本解析仓库根目录、团队指令路径、下一个 CDR 编号和 adlc 分支，再识别子系统、比对既有团队指令，经发现、模式、合成三个阶段分析，把逆向得到的上下文指令记录（CDR）草稿写入 team-ai-directives 的 adlc 分支 drafts/cdr/ 并重建索引，最后建议用 team-levelup 审核发…

分类：知识
tikalk
热度 0.00
最近更新 2026-11-06 00:25:29

安装

发给 Agent
帮我安装这个技能：npx secure-skills-cli add tikalk/adlc-team-skills/team-init
兼容性
通用兼容
联网要求
需要联网
数据出网
可选出网
Metadata
name
team-init
description
Use when bootstrapping team knowledge from a brownfield codebase — reverse-engineers CDRs for contribution to team-ai-directives adlc branch.
disable-model-invocation
true
scripts
{"sh":"scripts/bash/team-init.sh","ps":"scripts/powershell/team-init.ps1"}

team-init

What this skill does

Reverse-engineer Context Directive Records (CDRs) from an existing codebase (brownfield) to document reusable patterns for contribution to team-ai-directives.

Replaces the former team-init skill. Drafts are written to the adlc orphan branch of team-ai-directives (not project-local .adlc/drafts/).

When to use

  • Brownfield projects: Existing code without team-wide directives
  • Legacy modernization: Extract reusable patterns before refactoring
  • Team onboarding: Turn implicit conventions into explicit directives

When NOT to use

  • Greenfield (session complete): Use /team-levelup to extract from session
  • Mining git history: Use /change-init for past decisions

Process

Phase 0: Environment Setup

Run: scripts/bash/team-init.sh --setup

Resolves REPO_ROOT, TEAM_AI_DIRECTIVES, NEXT_CDR, ADLC_BRANCH.

Phase 1: Sub-System Detection

Analyze codebase for distinct sub-systems (same detection as former team-init):

  • src/auth/ → Authentication
  • services/payment/ → Payment
  • etc.

Phase 2: Load Team Directives

Read existing team-ai-directives main branch for comparison (avoid duplicates).

Phase 3: Multi-Agent Analysis

  1. Discovery Agent: Scan each sub-system for raw patterns
  2. Pattern Agent: Classify and score patterns for reusability
  3. Synthesis Agent: Cross-sub-system analysis and CDR generation

Phase 4: Write CDRs

Write to adlc branch drafts/cdr/ using the shared CDR draft template at skills/team/templates/cdr-draft-template.md.

Phase 5: Handoff

Suggest running /team-levelup to review and publish the discovered CDRs.

Verification

  • CDRs written to adlc branch drafts/cdr/
  • No CDRs in .adlc/drafts/ (old location)
  • cdr.md index regenerated in adlc branch