agentleFS
JackJanoianJackJanoian/deal-desk/skills/dealdesk-converting-plans-to-tasks/SKILL.md

deal-desk-converting-plans-to-tasks

Skill1 starsChanged 6 months agoMITView on GitHub

Convert a DealDesk sourcing, diligence, or coverage plan into executable private-equity workstreams. Use when breaking an investment thesis, pipeline cleanup effort, intermediary coverage campaign, or diligence plan into assigned DealDesk tasks with clear dependencies and success criteria.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to turn a DealDesk plan into work that agents can execute without re-asking what to do.

    line 15
  2. Distinctive:

    Before creating tasks, identify:

    line 21
  3. Distinctive:

    If the plan lacks enough detail for an assignee to act, add a first task to clarify the missing input rather than creating vague research …

    line 30
  4. Distinctive:

    Use these task categories:

    line 34
  5. Distinctive:

    Use dependencies for real ordering constraints.

    line 48
  6. Distinctive:

    Call out missing employees or skills as a staffing gap instead of assigning mismatched work.

    line 50
  7. Distinctive:

    Create sourcing slices by sector and geography.

    line 81
  8. Distinctive:

    After initial targets exist, assign contact enrichment.

    line 84
  9. Distinctive:

    Add missing citations and score rationales.

    line 90
  10. Distinctive:

    Add missing intermediary profiles.

    line 99
  11. Distinctive:

    Every task has an owner or explicitly states a staffing gap.

    line 106
  12. Distinctive:

    No task asks an agent to fabricate data, send outreach without approval, or bypass DealDesk records.

    line 110

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DealDesk — Converting Plans To Tasks

Use this skill to turn a DealDesk plan into work that agents can execute without re-asking what to do.

The goal is not to create a beautiful plan. The goal is to create a clean operating graph: each task has an owner, a concrete deliverable, the right DealDesk records to update, and real blockers.

Inputs To Gather

Before creating tasks, identify:

  • Active thesis or mandate.
  • Target sectors, geography, revenue range, and ownership signals.
  • Current pipeline gaps.
  • Intermediary coverage gaps.
  • Diligence questions or partner decisions.
  • Available DealDesk employees and their specialties.

If the plan lacks enough detail for an assignee to act, add a first task to clarify the missing input rather than creating vague research tickets.

Task Types

Use these task categories:

  • Sourcing slice: find companies in a defined sector/geography/size band.
  • Pipeline cleanup: dedupe, normalize stages, update stale records, or add missing citations.
  • Contact enrichment: identify owners, CEOs, founders, bankers, brokers, or advisors.
  • Intermediary coverage: map relationships, draft check-ins, and schedule next touches.
  • Diligence question: answer a focused market, customer, financial, or competitive question.
  • Partner review: summarize evidence and ask for a decision.
  • Tooling gap: request or implement missing DealDesk workflow support.

Decomposition Rules

  • One task should produce one inspectable result.
  • Give each task a DealDesk object to update when possible: thesis, target, intermediary, contact, outreach draft, or pipeline summary.
  • Use dependencies for real ordering constraints. Do not serialize work that can run in parallel.
  • Assign by specialty. A sourcer should source; a contact enricher should enrich; Head of BD should orchestrate and summarize.
  • Call out missing employees or skills as a staffing gap instead of assigning mismatched work.

Task Template

Each task should include:

## Goal
What business outcome this task supports.

## Scope
Sector/geography/revenue/stage/contact/intermediary boundaries.

## Inputs
Thesis, existing records, source lists, or partner notes to use.

## Deliverable
Exact DealDesk record updates or summary expected.

## Quality Bar
Citation, dedupe, scoring, confidence, and approval requirements.

## Blockers
Any tasks or partner decisions that must happen first.

Common Workstream Patterns

New Thesis Launch

  1. Normalize the thesis into searchable criteria.
  2. Create sourcing slices by sector and geography.
  3. Assign target sourcing in parallel.
  4. Assign intermediary mapping in parallel.
  5. After initial targets exist, assign contact enrichment.
  6. Head of BD summarizes pipeline coverage and gaps.

Pipeline Quality Sprint

  1. Deduplicate target records.
  2. Add missing citations and score rationales.
  3. Re-score stale or weak targets.
  4. Enrich top-priority contacts.
  5. Summarize which records are partner-ready.

Coverage Campaign

  1. Segment intermediaries by relevance and freshness.
  2. Draft overdue check-ins.
  3. Add missing intermediary profiles.
  4. Surface relationship gaps for partner review.

Done Criteria

A task breakdown is ready when:

  • Every task has an owner or explicitly states a staffing gap.
  • Each task has a concrete DealDesk deliverable.
  • Dependencies are represented as blockers, not buried in prose.
  • Partner approval points are explicit.
  • No task asks an agent to fabricate data, send outreach without approval, or bypass DealDesk records.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.