gooseworks-ai / composites-inbound-lead-triage
Inbound Lead Triage
Triage inbound leads for a requested period by collecting configured lead sources, normali
The shape of the run
9 steps · start to finish.
- 1Step 1
Environment Setup
▶- Create
/app/resultsif it does not exist. - Confirm that the requested
time_periodis explicit enough to query each lead source. - Load
config/inbound-triage.jsonwhen present. If it is missing and the user did not provide raw leads, ask for source configuration before collecting leads. - Confirm each configured source can be read. If a source is unavailable, record it in
validation_report.jsonand continue with available sources only when the user approves.
mkdir -p /app/results - Create
- 2Step 2
Configuration (Once Per Client)
▶On first run, ask the user to configure their lead sources and preferences. Save to the current working directory or wherever the user prefers (e.g., `config/inbound-triage.json`).
- 3Step 3
Collect Leads
▶ - 4Step 4
Classify & Rank by Urgency
▶ - 5Step 5
Qualify Against ICP
▶ - 6Step 6
Enrich with Context
▶ - 7Step 7
Route & Recommend Response
▶ - 8Step 8
Write Required Outputs
▶Write `/app/results/inbound_lead_triage.md` with a prioritized action queue grouped by urgency tier. Include lead name, company, source signal, ICP fit, urgency reason, recommended owner, next action, and a response draft where appropriate.
- 9Step 9
Iterate on Errors (max 3 rounds)
▶If output generation or validation fails, perform a targeted correction and retry for max 3 rounds. Do not broaden the task beyond the failed stage.