clickup-task-extractor

name: clickup-task-extractor description: Extract task requirements from meeting transcripts, notes, or conversations and prepare them for ClickUp task creation. Use this skill when you need to convert informal discussions or meeting notes into structured ClickUp tasks. Always calls silver-fern-knowledge for product context.

ClickUp Task Extractor

Overview

This skill extracts structured task information from unstructured content like meeting transcripts, Slack conversations, or notes. It identifies task names, user stories, acceptance criteria, and product context, then calls the silver-fern-knowledge skill for validation.

When to Use This Skill

Use this skill when:

• Processing meeting transcripts that discuss new features or bugs
• Converting Slack conversations into actionable tasks
• Reviewing notes from product discussions or wireframe reviews
• Extracting multiple tasks from a single conversation or document

Workflow

1. Analyze Input Content

Review the provided content to identify:

• Task Names: Clear, action-oriented titles (e.g., "Assign multiple jobs to production locations")
• User Stories: The user's perspective and goal
• Acceptance Criteria: Specific, measurable outcomes expected
• Product Context: Which app/product this affects (Produce, Retail, Finish, etc.)
• Client Information: Is this a Bonnie-specific task?

2. Call silver-fern-knowledge Skill

For each identified task, invoke the silver-fern-knowledge skill to:

• Validate product context (is this Produce, Retail, Finish, or all Mobile Apps?)
• Understand the feature area and related functionality
• Determine if it's a client-specific task (Bonnie)
• Get additional context that may inform acceptance criteria

3. Structure Each Task

Extract and format each task with the following information:

Task Name: [Clear, concise title]

User Story: As a user, I want to [action/capability] so that [benefit/outcome].

Acceptance Criteria:

• Specific requirement 1
• Specific requirement 2
• Specific requirement 3

Product: [Produce/Retail/Finish/Mobile Apps]

Client: [Bonnie if applicable, otherwise blank]

Status: New (always - these need review before Ready for Dev)

Department: Product (always)

4. Handle Incomplete Context

When you don't have complete information:

• Create rough acceptance criteria based on what you know
• Note assumptions clearly
• Highlight areas that need clarification from product team
• Focus on capturing intent even if details are missing

5. Output Format

Present extracted tasks in a clear, organized format:

=== Task 1: [Task Name] ===

User Story:
As a user, I want to [action] so that [benefit].

Acceptance Criteria:
- Requirement 1
- Requirement 2
- Requirement 3

Product: Produce
Client:
Status: New
Department: Product

Notes: [Any assumptions or clarifications needed]

---

=== Task 2: [Task Name] ===
...

Special Rules

Status Always "New"

Tasks extracted from transcripts or informal conversations ALWAYS go into "New" status. They need review by the product team before moving to "Ready for Dev". Never set status to "Ready for Dev" unless explicitly told otherwise.

Product Specificity

• Be specific when possible: If the task clearly relates to Produce, use "Produce" (not "Mobile Apps")
• Use "Finish" for finish app: Tasks specific to the finishing/processing app
• Use "Retail" for retail app: Tasks specific to the retail/sales app
• Use "Mobile Apps" only for generic tasks: When a task applies to all mobile apps generally (e.g., "Move authentication from Fusion to Okta")

Bonnie Tasks (Client Tasks)

If the task:

• Explicitly mentions "Bonnie"
• Is discussed in a Bonnie-specific context
• Is clearly for a specific client

Then mark it with:

• Client: Bonnie
• Log Hours: Yes (always for Bonnie tasks)
• Share with Client: Yes

Department

Always set to "Product" for tasks extracted through this workflow.

Example Extraction

Input (from transcript):

"So really what we need is to let users split up lots across multiple
production locations. Right now they can only put a lot in one place,
but their greenhouse might have the same variety in multiple zones.
This came up in yesterday's review meeting with Bonnie."

Output:

=== Task 1: Split lots across multiple production locations ===

User Story:
As a user, I want to split lots across multiple production locations so that I can accurately represent my greenhouse layout when the same variety is grown in multiple zones.

Acceptance Criteria:
- User can assign a single lot to multiple production locations
- Each location displays its portion of the total lot
- Greenhouse view accurately reflects the split lot distribution
- System maintains accurate inventory across all locations
- Changes to lot distribution update in real-time

Product: Produce
Client: Bonnie
Status: New
Department: Product
Log Hours: Yes
Share with Client: Yes

Notes: Task came from wireframe review meeting. May need to clarify business rules for how lot quantities are divided between locations.

Integration with Other Skills

This skill focuses on extraction only. After extracting tasks:

• Use clickup-task-formatter to format for ClickUp import/API
• Always calls silver-fern-knowledge for product context validation
• May reference ux-principles or figma-mastery if tasks involve UI changes

Common Patterns

Multiple Related Tasks

When extracting multiple related tasks from one discussion, group them together and note their relationships:

=== Related Tasks from Production Location Discussion ===

Task 1: Split lots across multiple locations
[details...]

Task 2: View consolidated lot information across locations
[details...]

Task 3: Report on production by location
[details...]

Note: These tasks are related and may have dependencies.

Figma-Related Tasks

When a transcript discusses wireframes or Figmas:

User Story:
As a user, I want to [functionality] so that [benefit].

Acceptance Criteria:
- Replicate the Figma design for [screen/feature]
- [Specific interaction requirements]
- [Business logic requirements]

Notes: References Figma file [name/URL if mentioned]. May need to use figma-mastery skill for detailed component extraction.

Resources

This skill doesn't require additional scripts or assets - it's a pure extraction and structuring workflow.