Initiating Coverage
Create institutional-quality equity research initiation reports through a structured 5-task workflow. Each task must be executed separately with verified inputs.
Overview
This skill produces comprehensive first-time coverage reports following institutional standards (JPMorgan, Goldman Sachs, Morgan Stanley format). Tasks are executed individually, each verifying prerequisites before proceeding.
**Default Font**: Times New Roman throughout all documents (unless user specifies otherwise).
---
⚠️ CRITICAL: One Task at a Time
**THIS SKILL OPERATES IN SINGLE-TASK MODE ONLY.**
If User Requests Full Pipeline
When user requests:
- "Create a coverage initiation report for [Company]"
- "Write an initiation report for [Company]"
- "Do the entire equity research process for [Company]"
- "Complete all 5 tasks for [Company]"
- Any request that implies running multiple tasks or the entire workflow
**REQUIRED RESPONSE:**
- **Ask which specific task to perform:**
I can help you create an equity research initiation report for [Company].
This involves 5 separate tasks that need to be completed individually:
1. Company Research - Research business, management, industry
2. Financial Modeling - Build projection model
3. Valuation Analysis - DCF and comparable companies
4. Chart Generation - Create 25-35 charts
5. Report Assembly - Compile final report
Which task would you like to start with?- **When user explicitly requests all tasks together:**
I understand you'd like to complete the entire initiation report pipeline.
Currently, this skill supports executing one task at a time, which allows
for better quality control and review at each stage.
We're working on a seamless end-to-end workflow that will make this process
more automated, but for now, we'll need to complete each task separately.
Would you like to start with Task 1 (Company Research)?- **Never automatically assume which task to start** - always ask user to confirm.
- **Never execute multiple tasks in sequence** - complete one task, deliver outputs, then wait for next user request.
Task Execution Rules
- ✅ Execute exactly ONE task per user request
- ✅ Always verify prerequisites before starting a task
- ✅ Deliver task outputs and confirm completion
- ✅ Wait for user to explicitly request the next task
- ❌ Never chain multiple tasks together automatically
- ❌ Never assume user wants to proceed to next task
- ❌ Never execute Tasks 3-5 without verifying required inputs exist
⚠️ Deliverables Policy: NO SHORTCUTS
**DELIVER ONLY THE SPECIFIED OUTPUTS. DO NOT CREATE EXTRA DOCUMENTS.**
Each task specifies exact deliverables. Do NOT create:
- ❌ "Completion summaries"
- ❌ "Executive summaries"
- ❌ "Quick reference guides"
- ❌ "Next steps documents"
- ❌ "Task completion reports"
- ❌ Any other "helpful" documentation not explicitly specified
**Why**: These extras waste context and are not part of the professional workflow.
**What TO deliver**:
- ✅ Task 1: Research document (.md) — **NOTHING ELSE**
- ✅ Task 2: Financial model (.xlsx) — **NOTHING ELSE**
- ✅ Task 3: Valuation analysis (.md) + Excel tabs added to Task 2 file — **NOTHING ELSE**
- ✅ Task 4: Charts zip file (.zip) — **NOTHING ELSE**
- ✅ Task 5: Final report (.docx) — **NOTHING ELSE**
**If a deliverable is not listed above, DO NOT CREATE IT.**
---
Task Selection
Select which task to execute:
| Task | Name | Prerequisites | Output | |----
<!-- truncated -->