03_task3

Analyze Slack messages to assess deal feasibility and write a structured report.

1|Updated May 20, 2026
One-click install
npx skills add https://github.com/Wanli-Lee/CUA-Claw-Harness --skill 03-task3-wanli-lee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 03_task3
Source: https://github.com/Wanli-Lee/CUA-Claw-Harness/tree/main/skills/03_task3
Command: npx skills add https://github.com/Wanli-Lee/CUA-Claw-Harness --skill 03-task3-wanli-lee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates scattered Slack updates into an actionable deal or project feasibility assessment for leadership, surfacing commitments, conflicts, and risks.

Core Features & Use Cases

  • Stakeholder synthesis: Reads recent Slack messages, extracts promises, requirements, and blockers across people and rounds.
  • Conflict and risk analysis: Identifies shifting or contradictory requirements and highlights likely failure points.
  • Deliverability-ready reporting: Produces a structured feasibility report separating what can be delivered from what cannot be delivered.

Quick Start

Use the skill to analyze the relevant Slack thread for a deal and generate a feasibility report for leadership.

Frequently Asked Questions about 03_task3

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

FAQPage Schema
How do I assess project feasibility from scattered Slack messages?

Assess project feasibility from Slack messages by consolidating fragmented stakeholder input, extracting cross-message commitments and blockers, and generating a structured report separating deliverable items from undeliverable risks.

Can I extract stakeholder commitments and blockers from a Slack thread for a leadership report?

Yes, you can extract stakeholder commitments and blockers from a Slack thread by synthesizing recent messages to identify shifting requirements and produce a structured feasibility report for leadership decisions.

What is the best way to identify conflicting requirements in Slack discussions?

Identifying conflicting requirements in Slack discussions involves cross-message extraction of contradictory feedback and changing requirements to highlight likely failure points and shifting stakeholder promises.

How do I consolidate fragmented Slack updates into a deal management risk assessment?

Consolidate fragmented Slack updates into a deal management risk assessment by retrieving recent messages, applying message-level content consolidation, and writing structured deliverability and risk conclusions to a markdown file.

Does this feasibility analysis require read-only access to Slack messages?

Yes, this feasibility analysis requires read-only Slack message retrieval to access recent discussions containing commitments and changing requirements without modifying the original conversation threads.

What limitations exist when analyzing Slack threads for project deliverability?

Limitations include relying exclusively on recent Slack messages for context, meaning commitments or blockers discussed outside the analyzed thread are omitted from the final structured feasibility report.