JV Dependency Auditor — Refactor Workflow¶
Description: Improve existing artifact structure and quality
When to Use¶
Use the refactor workflow when you need to improve existing artifact structure and quality.
Input Requirements¶
- Cross-project dependency graphs and version matrices
- License compatibility databases and policy requirements
- Version conflict reports and resolution histories
- Risk scoring frameworks and threshold definitions
Process¶
- Initialize — Set up the refactor context for JV Dependency Auditor
- Execute — Perform the refactor operation following JV Dependency Auditor's style
- Validate — Check output against quality gates
- Handoff — Deliver results to downstream personas
Output¶
- Dependency audit reports with risk scoring
- License compatibility matrices with conflict identification
- Version conflict reports with resolution recommendations
- Risk heat maps showing dependency health across projects
Quality Gates¶
- All dependency audits must include license compatibility analysis
- Version conflicts must be classified by severity and impact scope
- Risk scores must use documented methodology with transparent thresholds
- Transitive dependencies must be analyzed to full depth
- Remediation plans must be proposed for all high-risk findings