dev-investigation

Automating repository-level investigation involves reading background context from setup.yaml and analyzing the design-document. This skill systematically inspects these inputs to produce detailed findings and update the design document's investigation section automatically.

Yes, generating UML diagrams during an investigation is supported. The skill produces detailed investigation reports under docs/{target_repo}/dev-investigation, which include UML diagrams to visually document the findings and system architecture.

The best way to update a design-document with findings is to systematically process the investigation results and append them to the document's investigation section. This ensures background context and recommendations are structurally captured for future reference.

Yes, a setup.yaml file is required. The investigation process specifically reads description.background from setup.yaml to acquire the necessary repository-level background context before generating findings and updating the design-document.

Background context from setup.yaml drives the investigation by providing the foundational information needed to systematically analyze the repository. The skill reads this context to ensure generated reports and UML diagrams accurately reflect the development task environment.

This approach is limited to repository-level investigations requiring updates to existing design documents. It depends on ingesting setup.yaml and a design-document, making it unsuitable for investigations lacking these predefined structural inputs.