expert-team

Invoke the expert-team workflow with a clear module root path. It scans the module, presents a creation plan for confirmation, dispatches parallel sub-agents per aspect, and writes contract and implementation documents into .module-experts/.

The contract layer (C0–C5 files in the expert root) is a black-box usage guide covering capabilities, parameters, and real code examples. The implementation layer (implementation/01–07) is a white-box map of architecture, data flow, and tests used to navigate the source code.

Split into sub-experts when the module has clear functional subdomains and one expert's contract would be too large. Create a topic only for very large modules (e.g., over 500 source files) needing a three-level topic → expert → sub-expert structure; sub-experts cannot nest further.

Skip shared or cross-cutting code such as utility libraries, style conventions, and infrastructure, which belong in project memory instead. Also skip small or simple modules where reading the code directly or a lightweight walkthrough is sufficient.

Each expert records a baseline git commit in agent.md and INDEX.md. A companion lookup skill compares that baseline against HEAD to detect changed files and performs limited incremental updates without refreshing the baseline.

The memory-writing steps are skipped and the omission is noted in the final acceptance report. Expert package creation and disk output are not blocked by the missing knowledge base.