// End-to-end associate workflow with time-boxed gates: thesis -> sourcing -> meetings -> diligence -> memo, ending with either IC-ready memo or explicit kill decision. Use when you need to run the full pipeline for a sector or a specific deal.
| name | dealflow-sourcing-to-memo |
| description | End-to-end associate workflow with time-boxed gates: thesis -> sourcing -> meetings -> diligence -> memo, ending with either IC-ready memo or explicit kill decision. Use when you need to run the full pipeline for a sector or a specific deal. |
| license | Proprietary |
| compatibility | Requires web access for research + Salesforce logging is mandatory; can be run without scripts. |
| metadata | {"author":"evalops","version":"0.2"} |
Use this compound skill when you need to simulate a full associate workflow:
Every workflow ends with one of two outcomes:
No deals in limbo. No "watching" without a recheck date.
Deliverables:
Gate: Do you have a clear buyer, budget source, and trigger event? If no, iterate or kill the thesis.
Log: create Campaign Thesis: <topic> (YYYY-MM) in Salesforce
Deliverables:
Gate: Did you generate 3 qualified meeting candidates? If no, the thesis is too narrow or your signals are wrong. Iterate or kill.
Log: all Leads/Accounts created with next-step Tasks
For each qualified company:
Gate (per company): Advance to diligence OR pass with reasons.
Pass requirements:
Log: Event + Notes + Opportunity stage update
Deliverables:
Gate: For each risk, did the test produce decision-changing evidence? If a critical risk remains untestable, consider killing the deal.
Log: Tasks per workstream + Activity logs for calls
Deliverables:
Final gate: One of two outcomes only:
Log: attach memo to Opportunity + update stage to "IC Scheduled" or "Passed"
Gate at end of Day 2: Kill or continue? No "need more time."
Gate at end of Day 3: All top 4 risks tested? If not, why?
Gate at each phase transition.
At each gate, you must answer:
No "let's keep watching" without a concrete recheck date and trigger.
Use atomic skills as needed:
Writes, edits, and creates dbt models following best practices. Use when user needs to create new dbt SQL models, update existing models, or convert raw SQL to dbt format. Handles staging, intermediate, and mart models with proper config blocks, CTEs, and documentation.
Apply Domain-Driven Design, Clean Architecture, CQRS, and command/query patterns to code reviews and feature design. Use when analyzing or designing code in Application, Service, Infrastructure, DataAccess, Validation, Domain, or Functions projects, or when addressing architectural concerns, layering, mapping, entities, value objects, repositories, or validators in the Rome Repair Order Service.
Analyzes and refactors code using Domain-Driven Design principles. Use when refactoring domain models, identifying DDD anti-patterns, improving domain clarity, or applying tactical/strategic DDD patterns.
Guide for DDD strategic design - analyzing domains through structured questioning, conducting stakeholder interviews (PM/domain experts/users), and producing Bounded Context analysis, Context Maps, and Ubiquitous Language. Use when user needs help understanding domain boundaries, planning domain interviews, or structuring DDD strategic artifacts.
Win competitive rounds: run a clean process, deliver value previews before asking, coordinate partners, and manage timelines. Use when you're trying to close a 'must win' deal against other funds.
DearTs Framework 开发技能。基于 SDL3 + ImGui 的 C++20 现代应用框架，提供完整的应用生命周期管理、类型安全事件系统、Content Registry 和插件架构。适用于 DearTs Framework 相关的所有开发任务，包括应用程序开发、事件驱动架构、插件系统、多视图应用等。