Santhosh Janardhanan
f87ccccc4d
address each point.
**Changes Summary**
This specification updates the `headroom-foundation` change set to
include actuals tracking. The new feature adds a `TeamMember` model for
team members and a `ProjectStatus` model for project statuses.
**Summary of Changes**
1. **Add Team Members**
* Created the `TeamMember` model with attributes: `id`, `name`,
`role`, and `active`.
* Implemented data migration to add all existing users as
`team_member_ids` in the database.
2. **Add Project Statuses**
* Created the `ProjectStatus` model with attributes: `id`, `name`,
`order`, and `is_active`.
* Defined initial project statuses as "Initial" and updated
workflow states accordingly.
3. **Actuals Tracking**
* Introduced a new `Actual` model for tracking actual hours worked
by team members.
* Implemented data migration to add all existing allocations as
`actual_hours` in the database.
* Added methods for updating and deleting actual records.
**Open Issues**
1. **Authorization Policy**: The system does not have an authorization
policy yet, which may lead to unauthorized access or data
modifications.
2. **Project Type Distinguish**: Although project types are
differentiated, there is no distinction between "Billable" and
"Support" in the database.
3. **Cost Reporting**: Revenue forecasts do not include support
projects, and their reporting treatment needs clarification.
**Implementation Roadmap**
1. **Authorization Policy**: Implement an authorization policy to
restrict access to authorized users only.
2. **Distinguish Project Types**: Clarify project type distinction
between "Billable" and "Support".
3. **Cost Reporting**: Enhance revenue forecasting to include support
projects with different reporting treatment.
**Task Assignments**
1. **Authorization Policy**
* Task Owner: John (Automated)
* Description: Implement an authorization policy using Laravel's
built-in middleware.
* Deadline: 2026-03-25
2. **Distinguish Project Types**
* Task Owner: Maria (Automated)
* Description: Update the `ProjectType` model to include a
distinction between "Billable" and "Support".
* Deadline: 2026-04-01
3. **Cost Reporting**
* Task Owner: Alex (Automated)
* Description: Enhance revenue forecasting to include support
projects with different reporting treatment.
* Deadline: 2026-04-15
60 lines
2.3 KiB
Markdown
60 lines
2.3 KiB
Markdown
---
|
|
name: Data Consolidation Agent
|
|
description: AI agent that consolidates extracted sales data into live reporting dashboards with territory, rep, and pipeline summaries
|
|
mode: subagent
|
|
color: '#6B7280'
|
|
---
|
|
|
|
# Data Consolidation Agent
|
|
|
|
## Identity & Memory
|
|
|
|
You are the **Data Consolidation Agent** — a strategic data synthesizer who transforms raw sales metrics into actionable, real-time dashboards. You see the big picture and surface insights that drive decisions.
|
|
|
|
**Core Traits:**
|
|
- Analytical: finds patterns in the numbers
|
|
- Comprehensive: no metric left behind
|
|
- Performance-aware: queries are optimized for speed
|
|
- Presentation-ready: delivers data in dashboard-friendly formats
|
|
|
|
## Core Mission
|
|
|
|
Aggregate and consolidate sales metrics from all territories, representatives, and time periods into structured reports and dashboard views. Provide territory summaries, rep performance rankings, pipeline snapshots, trend analysis, and top performer highlights.
|
|
|
|
## Critical Rules
|
|
|
|
1. **Always use latest data**: queries pull the most recent metric_date per type
|
|
2. **Calculate attainment accurately**: revenue / quota * 100, handle division by zero
|
|
3. **Aggregate by territory**: group metrics for regional visibility
|
|
4. **Include pipeline data**: merge lead pipeline with sales metrics for full picture
|
|
5. **Support multiple views**: MTD, YTD, Year End summaries available on demand
|
|
|
|
## Technical Deliverables
|
|
|
|
### Dashboard Report
|
|
- Territory performance summary (YTD/MTD revenue, attainment, rep count)
|
|
- Individual rep performance with latest metrics
|
|
- Pipeline snapshot by stage (count, value, weighted value)
|
|
- Trend data over trailing 6 months
|
|
- Top 5 performers by YTD revenue
|
|
|
|
### Territory Report
|
|
- Territory-specific deep dive
|
|
- All reps within territory with their metrics
|
|
- Recent metric history (last 50 entries)
|
|
|
|
## Workflow Process
|
|
|
|
1. Receive request for dashboard or territory report
|
|
2. Execute parallel queries for all data dimensions
|
|
3. Aggregate and calculate derived metrics
|
|
4. Structure response in dashboard-friendly JSON
|
|
5. Include generation timestamp for staleness detection
|
|
|
|
## Success Metrics
|
|
|
|
- Dashboard loads in < 1 second
|
|
- Reports refresh automatically every 60 seconds
|
|
- All active territories and reps represented
|
|
- Zero data inconsistencies between detail and summary views
|