Add Maven dependencies for improved code quality

Add essential Maven dependencies that enhance code quality and safety through a consultative, question-driven approach. This is an interactive SKILL.

What is covered in this Skill?

• JSpecify: (nullness annotations, provided scope)
• Error Prone + NullAway: (enhanced static analysis with compile-time null checking)
• VAVR: (functional programming with Try/Either and immutable collections)
• ArchUnit: (architecture rule enforcement, test scope)

Constraints

Before adding Maven dependencies, ensure the project is in a valid state. Use a consultative, question-driven flow that adds only what the user selects.

• MANDATORY: Run ./mvnw validate or mvn validate before any changes
• SAFETY: If validation fails, stop and ask the user to fix issues—do not proceed until resolved
• BEFORE ASKING QUESTIONS: Read the reference to use the exact wording and options from the template. Ask questions one-by-one in strict order (JSpecify → Enhanced Compiler Analysis (conditional) → VAVR → ArchUnit) and add only what the user selects. Use consultative language, present trade-offs, and wait for user responses before implementing

When to use this skill

• Add Maven dependencies
• Add JSpecify nullness dependencies
• Add Error Prone NullAway dependencies
• Add VAVR functional dependencies
• Add ArchUnit architecture testing dependencies

Reference

For detailed guidance, examples, and constraints, see references/111-java-maven-dependencies.md.