oss-forensics/orchestration

Automate OSS investigations by orchestrating specialist agents to collect evidence from GitHub repositories, GitHub Archive, Wayback Machine, and local sources in parallel. Initialize the workflow using the Phase 0 init script, which sets up the working directory and evidence store to begin coordinated evidence collection.

A phase-driven workflow structures investigations into initialization, prompt parsing, parallel evidence collection, hypothesis formation, verification, and final reporting. This approach enforces traceable outputs like evidence.json and forensic-report.md while enabling parallel task execution across multiple agents.

Yes, this orchestration skill spawns multiple analyst agents to collect evidence from GitHub API, GH Archive, Wayback, and local repositories simultaneously. Parallel execution accelerates incident discovery and compiles comprehensive timelines without sequential bottlenecks.

After parallel evidence collection and hypothesis verification, the orchestration workflow generates a forensic-report.md with findings and a structured evidence.json file. This completes the phase-driven process and produces traceable, comprehensive documentation of your investigation.

This skill integrates GitHub API for repository metadata, GH Archive for historical events, Wayback Machine for snapshot history, and local repository data. It coordinates evidence retrieval across these sources to build a complete investigation profile.