List of actors identified during the requirements analysis process.
Contains the various user actors, personas, or stakeholder types that were identified and analyzed during the requirements gathering phase. These actors help define different user perspectives, access levels, and functional requirements needed for the system being developed.
Aggregated token usage and function calling metrics by operation type.
Maps each event type within the phase to its complete aggregate metrics, including detailed token consumption breakdown with cache statistics and comprehensive function calling metrics data. This comprehensive aggregation enables deep analysis of resource utilization patterns and operation quality across the entire phase.
The partial record structure reflects that not all possible event types may occur during phase execution. Only operations that were actually performed will have entries in this mapping.
The aggregate data supports cost analysis (via token usage), reliability assessment (via function calling metrics), and optimization opportunities (via cache hit rates and failure patterns).
Timestamp when the event was created.
ISO 8601 formatted date-time string indicating when this event was emitted by the system. This timestamp is crucial for event ordering, performance analysis, and debugging the agent workflow execution timeline.
Format: "YYYY-MM-DDTHH:mm:ss.sssZ" (e.g., "2024-01-15T14:30:45.123Z")
Total elapsed time for the phase execution in milliseconds.
Measures the wall-clock duration from phase start to completion, encompassing all agent operations, self-healing spiral loops, compiler validations, and any retry attempts. This metric provides visibility into phase-level performance and enables identification of bottlenecks in the waterfall pipeline.
The elapsed time includes both active LLM processing and any overhead from compilation, validation, and orchestration logic. For detailed breakdown of time spent in specific operations, consult the individual operation events within the phase.
Generated requirements analysis report files as key-value pairs.
Contains the complete set of markdown documents that comprise the finalized requirements analysis report. Each key represents the filename and each value contains the actual markdown content. The report typically includes business context, functional requirements, technical specifications, architectural decisions, and implementation guidelines.
These documents serve as the authoritative source for understanding project requirements and guide all subsequent development phases in the vibe coding pipeline including database design, API specification, and implementation.
A unique identifier for the event.
Project alias prefix that will be applied to all generated artifacts.
A short project identifier that will be consistently used as a prefix for database table names, API function names, and DTO type names throughout the entire codebase. This ensures consistent naming conventions and helps avoid naming conflicts in larger systems.
For example, if the prefix is "shopping", generated artifacts might include tables like "shopping_customers" and DTOs like "ShoppingCustomerDto".
Final state machine step counter value for the phase.
Records the terminal step number from the phase's state machine, which increments monotonically during execution and invalidates cached state when operations need to be redone. This step counter enables the frontend to detect when previously completed operations have been invalidated by spiral loop corrections, ensuring UI consistency with the actual generation state.
The step value provides a temporal marker for the phase completion, allowing correlation with intermediate operation events that share the same step number.
Unique identifier for the event type.
A literal string that discriminates between different event types in the AutoBE system. This field enables TypeScript's discriminated union feature, allowing type-safe event handling through switch statements or conditional checks.
Examples: "analyzeWrite", "prismaSchema", "interfaceOperation", "testScenario"
Event fired when the Analyze agent completes the requirements analysis process and finalizes the comprehensive analysis report.
This event represents the successful completion of the requirements analysis workflow, which includes drafting, reviewing, amending, and finalizing the analysis documentation. The event indicates that all discussions regarding requirements have been completed and a comprehensive report has been issued that will serve as the foundation for subsequent development phases.
The completion of requirements analysis marks a critical milestone in the vibe coding pipeline, as the generated report guides all subsequent development activities including database design, API specification, and implementation.
Author
Kakasoo