team-init
Skill145 starsChanged 20 days agoMITView on GitHub
Use when bootstrapping team knowledge from a brownfield codebase — reverse-engineers CDRs for contribution to team-ai-directives adlc branch.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- woossi/agent-project-templatetheir own version, first seen Jun 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- woossi/agent-project-template★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository48 other files it gives its agents.
- architect-analyzeSkill
- architect-bootSkill
- architect-clarifySkill
- architect-implementSkill
- architect-initSkill
- architect-specifySkill
- writing-skillsSkill
- change-bootSkill
- change-clarifySkill
- change-initSkill
- change-publishSkill
- change-specifySkill
- evals-analyzeSkill
- evals-clarifySkill
- evals-implementSkill
- evals-initSkill
- evals-specifySkill
- evals-validateSkill
- factory-cleanSkill
- factory-initSkill
- factory-intentSkill
- factory-learnSkill
- factory-missionSkill
- factory-orchestratorSkill
- factory-queueSkill
- factory-releaseSkill
- factory-reviewSkill
- factory-runbookSkill
- factory-setupSkill
- factory-ticketsSkill
- mission-briefSkill
- product-analyzeSkill
- product-bootSkill
- product-clarifySkill
- product-implementSkill
- product-initSkill
- product-roadmapSkill
- product-specifySkill
- team-bootSkill
- team-constitutionSkill
- team-diagnoseSkill
- team-discoverSkill
- team-levelupSkill
- team-repairSkill
- team-setupSkill
- team-skillsSkill
- workspaceSkill
- tech-radar-bootSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Greenfield (session complete): Use /team-levelup to extract from session
- Very specific: line 30
Mining git history: Use /change-init for past decisions
- Very specific: line 49
Read existing team-ai-directives main branch for comparison (avoid duplicates).
- Very specific: line 59
Write to adlc branch drafts/cdr/ using the shared CDR draft template at skills/team/templates/cdr-draft-template.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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-levelupto extract from session - Mining git history: Use
/change-initfor 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/→ Authenticationservices/payment/→ Payment- etc.
Phase 2: Load Team Directives
Read existing team-ai-directives main branch for comparison (avoid duplicates).
Phase 3: Multi-Agent Analysis
- Discovery Agent: Scan each sub-system for raw patterns
- Pattern Agent: Classify and score patterns for reusability
- 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
adlcbranchdrafts/cdr/ - No CDRs in
.adlc/drafts/(old location) cdr.mdindex regenerated inadlcbranch
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.