ce:compound

To document solved problems into durable team knowledge, you can run a multi-phase workflow that coordinates subagents to assemble context, decisions, and results into a searchable document under docs/solutions. This prevents future duplicate work and accelerates problem resolution.

Automating knowledge management from session history involves using an orchestration workflow that integrates session history context and cross-session correlation to enrich documentation. It applies a category schema to assemble content into structured artifacts with YAML frontmatter.

To prevent duplicate documentation when capturing team solutions, the workflow performs an overlap check during the assembly phase. It verifies content novelty against existing entries in the solutions directory before writing the final knowledge document to avoid redundant artifacts.

Yes, you can use subagents to generate technical documentation for a solved problem. The workflow orchestrates subagents across research, assembly, and enhancement phases to read problem context, apply a category schema, and produce the final knowledge document.

Yes, the documentation workflow supports cross-session correlation and overlap checks. It integrates optional session history enhancements to enrich content and explicitly runs overlap checks during assembly to avoid creating duplicate documentation artifacts within your knowledge base.