VC Task & Next-Step Generation

Extract commitments and decisions from VC deal context to generate owner-assigned next steps.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/alludium/alludium-packs --skill vc-task-next-step-generation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: VC Task & Next-Step Generation
Source: https://github.com/alludium/alludium-packs/tree/main/plugins/vc/skills/vc-task-and-next-step-generation
Command: npx skills add https://github.com/alludium/alludium-packs --skill vc-task-next-step-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert VC deal context into owner-assigned next steps, turning deal evidence such as meeting notes, pipeline state, IC decisions, and diligence outputs into concrete actions. It proposes actions, CRM updates, stage-move recommendations, or task-system drafts, and makes clear that changes are not executed without an approved workflow.

Core Features & Use Cases

  • Turn deal evidence into concrete, owner-assigned next steps.
  • Separate internal actions from founder/external requests.
  • Output structured fields: next_actions, external_requests, crm_update_suggestions, task_system_drafts, stage_transition_recommendation, approval_required.

Quick Start

Provide deal context, owner names, deadlines, and connected task/CRM surfaces to generate action-ready next steps.

Frequently Asked Questions about VC Task & Next-Step Generation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate owner-assigned next steps from VC deal context?

Generate owner-assigned next steps by inputting VC deal context like meeting notes and IC decisions to extract commitments and blockers into structured action drafts with explicit owners and due dates.

Can I automatically update my CRM pipeline from meeting notes and diligence outputs?

You cannot automatically update your CRM pipeline from meeting notes; the tool generates CRM update suggestions and stage-move recommendations that require explicit human approval before execution.

How do I separate internal deal actions from external founder follow-up requests?

Separate internal deal actions from external founder follow-up requests by processing deal evidence to output structured fields categorizing next_actions and external_requests distinctly.

What deal evidence do I need to provide for action-draft generation?

Provide deal evidence such as meeting notes, pipeline state, IC decisions, diligence outputs, and closing checklists alongside owner names and deadlines to generate action-ready next steps.

Does the Skill execute task-system updates automatically based on stage transition recommendations?

The Skill does not execute task-system updates automatically; it produces task-system drafts and stage transition recommendations that are strictly proposed actions requiring an approved workflow.

What's the best way to track deal blockers and missing inputs across stakeholders?

Track deal blockers and missing inputs by parsing stakeholder context and diligence outputs to generate structured action drafts that flag dependencies and assign owners for resolution.