Scope action
The scope action performs interactive gap analysis and boundary definition via UzzoScopeAgent (built with UzzoAgentBuilder.ScopeAgentBuilder()). The agent:
- accepts free-text prompts: rough user stories, or a rough description of a feature or goal
- identifies missing requirements, platform assumptions, and architectural gaps
- asks targeted clarifying questions through the
AskToolsinterface (LangChain4j tools) - produces a scope.md document with In-Scope / Out-of-Scope boundaries, updated iteratively as clarification progresses
When the analysis identifies multiple architectural domains (backend, frontend, storage, analysis, infrastructure, …), each domain can be scoped separately. The agent generates a domain-specific scope.md for each, so teams can work in parallel with clear boundaries.
Architecture
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ User Prompt │────▶│ UzzoScopeAgent │────▶│ AskTools │
│ (requirements) │ │ (AI Service) │ │ (interaction) │
└─────────────────┘ └──────────────────┘ └─────────────────┘
│
▼
┌──────────────────┐
│ Scope Document │
│ (Markdown) │
└──────────────────┘
| Component | Description |
|---|---|
UzzoScopeAgent | LangChain4j AI service interface defining the scope analysis contract |
UzzoAgentBuilder | Builders that bind each agent to its skill; the host adds chat model, memory and tools |
AskTools | Interface for user interaction (questions, choices, confirmations) |
Safe | Input validation mixin from lazyjava-core, implemented by the agent interfaces |
Scope document output
# Project Name: E-Commerce Platform
**Version:** 1.0.0
## Overall Description
[High-level breakdown by functional domains]
## In-Scope Capabilities
* **User Management**:
- [ ] JWT authentication
- [ ] Profile management
## Out-of-Scope / Future Enhancements
* Mobile application
* Advanced analytics dashboard
## Technical Context & Infrastructure
* **Development Toolchain**: Maven + Node.js
* **Target Systems/Platforms**: Web, AWS