Document Creation Skill
Create professional financial documents using Finance Guru templates.
Available Templates
| Template | Path | Purpose |
|----------|------|---------|
| Analysis Report | {project-root}/fin-guru/templates/analysis-report.md | Research and analysis reports |
| Buy Ticket | {project-root}/fin-guru/templates/buy-ticket-template.md | Capital deployment authorization |
| Compliance Memo | {project-root}/fin-guru/templates/compliance-memo.md | Regulatory compliance documentation |
| Excel Model Spec | {project-root}/fin-guru/templates/excel-model-spec.md | Financial model specifications |
| Presentation | {project-root}/fin-guru/templates/presentation-format.md | Stakeholder presentations |
| Onboarding Report | {project-root}/fin-guru/templates/onboarding-report.md | Client onboarding summaries |
Workflow
- Identify the appropriate template for the document type
- Load the template from
{project-root}/fin-guru/templates/ - Gather required inputs (analysis data, recommendations, metrics)
- Generate document with proper YAML frontmatter (date stamp, disclaimer, citations)
- Save under
fin-guru-private/fin-guru/using naming conventions:- Analysis reports:
analysis/{topic}-{YYYY-MM-DD}.md - Buy tickets:
tickets/buy-ticket-{YYYY-MM-DD}-{short-descriptor}.md - Strategy docs:
analysis/{strategy-name}-master-strategy.md
- Analysis reports:
Buy Ticket Contract
Buy tickets use the canonical buy-ticket-template.md contract:
- Builder is not a direct buy-ticket entrypoint; buy-ticket creation should begin from Strategy Advisor or Dividend Specialist
- YAML frontmatter plus a structured
## Execution Summarysection - Portfolio context must already be loaded
- Require deployment amount, allocation table, price snapshot, strategy rationale, risk notes, and sources/assumptions
- Save tickets to
fin-guru-private/fin-guru/tickets/ - Treat ITC risk as advisory-only; include an ITC advisory only when upstream analysis provided it and the signal is materially elevated
Requirements
- All documents MUST include educational-only disclaimer
- All sources MUST be cited with timestamps
- All documents MUST include YAML frontmatter with date stamp
- Follow institutional-grade formatting standards