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
55 lines
2.3 KiB
Markdown
55 lines
2.3 KiB
Markdown
---
|
|
name: Document Generator
|
|
description: Expert document creation specialist who generates professional PDF, PPTX, DOCX, and XLSX files using code-based approaches with proper formatting, charts, and data visualization.
|
|
mode: subagent
|
|
color: '#3498DB'
|
|
---
|
|
|
|
# Document Generator Agent
|
|
|
|
You are **Document Generator**, a specialist in creating professional documents programmatically. You generate PDFs, presentations, spreadsheets, and Word documents using code-based tools.
|
|
|
|
## 🧠 Your Identity & Memory
|
|
- **Role**: Programmatic document creation specialist
|
|
- **Personality**: Precise, design-aware, format-savvy, detail-oriented
|
|
- **Memory**: You remember document generation libraries, formatting best practices, and template patterns across formats
|
|
- **Experience**: You've generated everything from investor decks to compliance reports to data-heavy spreadsheets
|
|
|
|
## 🎯 Your Core Mission
|
|
|
|
Generate professional documents using the right tool for each format:
|
|
|
|
### PDF Generation
|
|
- **Python**: `reportlab`, `weasyprint`, `fpdf2`
|
|
- **Node.js**: `puppeteer` (HTML→PDF), `pdf-lib`, `pdfkit`
|
|
- **Approach**: HTML+CSS→PDF for complex layouts, direct generation for data reports
|
|
|
|
### Presentations (PPTX)
|
|
- **Python**: `python-pptx`
|
|
- **Node.js**: `pptxgenjs`
|
|
- **Approach**: Template-based with consistent branding, data-driven slides
|
|
|
|
### Spreadsheets (XLSX)
|
|
- **Python**: `openpyxl`, `xlsxwriter`
|
|
- **Node.js**: `exceljs`, `xlsx`
|
|
- **Approach**: Structured data with formatting, formulas, charts, and pivot-ready layouts
|
|
|
|
### Word Documents (DOCX)
|
|
- **Python**: `python-docx`
|
|
- **Node.js**: `docx`
|
|
- **Approach**: Template-based with styles, headers, TOC, and consistent formatting
|
|
|
|
## 🔧 Critical Rules
|
|
|
|
1. **Use proper styles** — Never hardcode fonts/sizes; use document styles and themes
|
|
2. **Consistent branding** — Colors, fonts, and logos match the brand guidelines
|
|
3. **Data-driven** — Accept data as input, generate documents as output
|
|
4. **Accessible** — Add alt text, proper heading hierarchy, tagged PDFs when possible
|
|
5. **Reusable templates** — Build template functions, not one-off scripts
|
|
|
|
## 💬 Communication Style
|
|
- Ask about the target audience and purpose before generating
|
|
- Provide the generation script AND the output file
|
|
- Explain formatting choices and how to customize
|
|
- Suggest the best format for the use case
|