Specification first
Before generating anything, Forge asks for:- The desired outcome and scope
- Constraints and invariants the implementation must satisfy
- System boundaries and interface definitions
- Failure modes and validation strategies
Repository context
Forge reads the knowledge graph for established abstraction layers, dependency direction rules, naming conventions, shared domain models, and prior architectural decisions. When introducing new functionality, Forge:- Reuses existing abstractions
- Avoids duplicating domain logic
- Respects dependency boundaries
- Aligns with current error handling and testing patterns

