Initiating Coverage

A first-time coverage report: the argument for or against owning a company, built from original research, a full model and a defended valuation. Five tasks, one per request by default, each verifying its inputs before it starts. The deliverables are a 30 to 50 page DOCX and an XLSX model, with typography set by .agents/skills/docx/SKILL.md.

Evidence labels, source tiers, staleness, the readiness posture and the intake limits: .agents/skills/research-conventions/SKILL.md, read before the first deliverable.

One task per request

This skill runs one task per request by default: execute the task, deliver its file, and stop, so the user can review before the next.

That stop is an intake exception and yields under .agents/skills/research-conventions/references/intake.md. When the user asked for the whole pipeline in one request ("do all five tasks", "run the whole initiation") or this skill is running as an input to another workflow, run the tasks in order without stopping between them, naming at each handoff the task just finished.

When the request names no task and does not ask for the whole run ("write an initiation report for X"), reply with the task list and ask which one to begin, in roughly this shape:

An initiation for [Company] runs as five tasks, one per request: