Sales
Engineer Pipeline Review
Prepare a engineer pipeline review. Uses time window, project key, repo, person.
Configure this skill
The page and the file follow your answers.
CRM
Email
Chat
Documents
Calendar
Project tools
6 of 6 systems connected
KeepDirectMissing
Your assistantSKILL.md
Download ↓
When to use it
Prepare a engineer pipeline review.
What it covers
Inputs
Owner/team, reporting cutoff, prior snapshot, forecast period.
Result
Pipeline movement table, forecast implications, buyer actions and source dates.
What it uses
CRMSlackCalendarEmailDocumentsKeep memoryRead only
For developers
Retrieval instructions
Resolve people, accounts and projects by stable identifiers. Use only the sources this task needs. Cite the source and date for each finding. Keep source systems unchanged.
Data sources
Attio, Slack, Google Workspace, Keep memory.
Procedure
- Resolve inputs for Engineer Pipeline Review: time_window, project_key, repo, person. Default time window: current quarter / open opportunities (override if caller provides time_window). Ask only for missing critical.
- keep_memory_read for open tasks, decisions, and handoffs relevant to Engineer Pipeline Review (filter out unrelated day-plan noise).
- Software Engineer lens: Prefer sources , GitHub PRs/issues, Linear tickets, Slack eng channels, design docs. Role ranking bias: SEV/incident → blocked PR → customer bug → tech-debt FYI.