Task Type: Share Idea

Purpose

Convert refined idea summaries to human-readable shareable formats by:

•Selecting the source idea summary file
•Choosing target format(s) (PPTX, DOCX, PDF, etc.)
•Using document conversion tools (MCP or pandoc)
•Generating formatted documents in the idea folder
•Naming output as formal-{source_name}.{extension}

Important Notes

Skill Prerequisite

•If you HAVE NOT learned task-execution-guideline and task-board-management skill, please learn them first before executing this skill.

Important: If Agent DO NOT have skill capability, can directly go to .github/skills/ folder to learn skills. And SKILL.md file is the entry point to understand each skill.

Task Type Default Attributes

Attribute	Value
Task Type	Share Idea
Category	Standalone
Standalone	Yes
Next Task	-
Auto-advance	No
Human Review	Yes

Task Type Required Input Attributes

Attribute	Default Value	Description
Auto Proceed	False	Auto-advance to next task
Ideation Toolbox Meta	`{project_root}/x-ipe-docs/config/tools.json`	Config file for enabled sharing tools
Current Idea Folder	N/A	Required from context - path to current idea folder
Extra Instructions	N/A	Additional context or requirements for document sharing

Extra Instructions Attribute

Purpose: Provides additional context or requirements for the document sharing process.

Source: This value can be obtained from:

•Human input (explicit instructions provided)
•x-ipe-docs/config/tools.json → stages.ideation.sharing._extra_instruction field
•Default: N/A (no extra instructions)

Loading Logic:

code

1. IF human provides explicit Extra Instructions:
   → Use human-provided value

2. ELSE IF x-ipe-docs/config/tools.json exists:
   a. Read stages.ideation.sharing._extra_instruction field
   b. IF field exists AND is not empty:
      → Use value from config
   c. ELSE:
      → Use default: N/A

3. IF Extra Instructions != N/A:
   → Apply these instructions when preparing content structure
   → Consider them when selecting output formats
   → Factor them into document styling/branding
   → Reference them during content conversion

Usage: When Extra Instructions are provided, the agent MUST incorporate them into the sharing workflow, particularly when formatting content and generating output documents.

Ideation Toolbox Meta File

Location: x-ipe-docs/config/tools.json (relative to project root)

Relevant Config Section:

json

{
  "version": "2.0",
  "stages": {
    "ideation": {
      "sharing": {
        "pptx": true,
        "pdf": true,
        "docx": false
      }
    }
  }
}

Tool Loading Rules:

•File exists: Load and parse the JSON configuration
•File missing: Inform user sharing tools not configured, proceed with all formats available
•Tool enabled (true): Offer format as available option
•Tool disabled (false): Skip the format from options
•Empty section: Default to all formats available

Sharing Tool Mapping:

Config Key	Format	What It Creates
`stages.ideation.sharing.pptx`	PowerPoint	.pptx presentation files
`stages.ideation.sharing.pdf`	PDF	.pdf read-only documents
`stages.ideation.sharing.docx`	Word	.docx editable documents
`stages.ideation.sharing.html`	HTML	.html web viewable files

Definition of Ready (DoR)

#	Checkpoint	Required
1	Refined idea summary exists (`idea-summary-vN.md`)	Yes
2	Target format(s) specified by human	Yes
3	Idea folder path provided	Yes

Execution Flow

Execute Share Idea by following these steps in order:

Step	Name	Action	Gate to Next
1	Load Config	Read `x-ipe-docs/config/tools.json` sharing section	Config loaded
2	Identify Source	Locate latest `idea-summary-vN.md` file	Source file found
3	Confirm Format	Ask human for target format(s) from enabled options	Format(s) confirmed
4	Prepare Content	Restructure content for target format	Content ready
5	Convert	Use pandoc/MCP to generate output files	Files generated
6	Verify	Confirm output files exist and have content	Files verified
7	Complete	Report files to human	Human confirms receipt

⛔ BLOCKING RULES:

•Step 3: BLOCKED until human confirms target format(s)
•Step 6: BLOCKED if output files are empty or missing

Supported Output Formats

Format	Extension	Tool	Best For	Config Key
PowerPoint	.pptx	pandoc / MCP	Presentations	`stages.ideation.sharing.pptx`
Word	.docx	pandoc / MCP	Documents, reviews	`stages.ideation.sharing.docx`
PDF	.pdf	pandoc / MCP	Read-only sharing	`stages.ideation.sharing.pdf`
HTML	.html	pandoc / MCP	Web viewing	`stages.ideation.sharing.html`

Execution Procedure

Step 1: Load Sharing Tool Configuration

Action: Read and parse the sharing section from tools config

Default Path: x-ipe-docs/config/tools.json

code

1. Check if x-ipe-docs/config/tools.json exists
2. If exists:
   a. Parse JSON file
   b. Extract stages.ideation.sharing section configuration
   c. Identify enabled formats (value = true)
   d. Extract _extra_instruction from stages.ideation.sharing section (if exists)
3. If NOT exists OR sharing section empty:
   a. Default to all formats available
   b. Log: "No sharing config found, all formats available"
4. Load Extra Instructions:
   a. IF human provided explicit Extra Instructions → Use human value
   b. ELSE IF _extra_instruction field exists and is not empty → Use config value
   c. ELSE → Set Extra Instructions = N/A
5. Log active sharing formats configuration and Extra Instructions (if any)

Output: List of enabled sharing formats

Step 2: Identify Source File

Action: Locate the refined idea summary to convert

code

1. Navigate to x-ipe-docs/ideas/{folder}/
2. List available idea-summary-vN.md files
3. Select the latest version OR human-specified version
4. Read the source content

Output: Source file path and content

Step 2: Confirm Target Format(s)

Action: Ask human for desired output format(s)

Question Template:

code

Which format(s) would you like to generate?

Available options:
- [ ] PowerPoint (.pptx) - For presentations
- [ ] Word (.docx) - For document review
- [ ] PDF (.pdf) - For read-only sharing
- [ ] HTML (.html) - For web viewing

You can select multiple formats.

Output: List of target formats

Step 3: Prepare Content Structure

Action: Organize content for conversion

For PowerPoint (PPTX):

markdown

# Title Slide
- Title: {Idea Name}
- Subtitle: Idea Summary

# Overview
- {Overview content as bullet points}

# Problem Statement
- {Problem as bullet points}

# Proposed Solution
- {Solution as bullet points}

# Key Features
- Feature 1: Description
- Feature 2: Description
- ...

# Success Criteria
- Criterion 1
- Criterion 2

# Next Steps
- {Call to action}

For Word (DOCX):

•Use the markdown content directly
•Preserve headers, tables, and formatting

Step 4: Execute Conversion

Action: Use available conversion tool

Option A: Using Pandoc (if available)

bash

# Convert to PPTX
pandoc -t pptx -o "formal-{source_name}.pptx" "{source_file}"

# Convert to DOCX
pandoc -t docx -o "formal-{source_name}.docx" "{source_file}"

# Convert to PDF
pandoc -t pdf -o "formal-{source_name}.pdf" "{source_file}"

Option B: Using MCP Document Tools (if available)

code

Use MCP server tools for document generation:
- mcp-documents/convert
- mcp-office/create-presentation
- mcp-office/create-document

Option C: Manual Generation If no conversion tools available:

•Inform human that automatic conversion is not available
•Provide structured content for manual copy-paste
•Suggest online conversion tools

Output File Naming:

code

formal-{source_filename}.{extension}

Examples:
- idea-summary-v1.md → formal-idea-summary-v1.pptx
- idea-summary-v2.md → formal-idea-summary-v2.docx

Step 5: Verify Output

Action: Confirm files were created

code

1. Check each output file exists
2. Verify file size > 0
3. List generated files to human

Output: List of created files with paths

Definition of Done (DoD)

#	Checkpoint	Required
1	Source idea summary identified	Yes
2	Target format(s) confirmed with human	Yes
3	Document(s) generated successfully	Yes
4	Output files named correctly (`formal-{source}.{ext}`)	Yes
5	Files saved in idea folder	Yes
6	Human confirmed receipt of files	Yes

Important: After completing this skill, always return to task-execution-guideline skill to continue the task execution flow and validate the DoD defined there.

Skill/Task Completion Output

This skill MUST return these attributes to the Task Data Model upon task completion:

yaml

category: standalone
task_type: Share Idea
auto_proceed: {from input Auto Proceed}
idea_folder: x-ipe-docs/ideas/{folder}
source_file: idea-summary-vN.md
shared_formats:
  - pptx
  - docx
require_human_review: true
task_output_links:
  - x-ipe-docs/ideas/{folder}/formal-idea-summary-vN.pptx
  - x-ipe-docs/ideas/{folder}/formal-idea-summary-vN.docx

Patterns

Pattern: Single Format Export

When: Human requests one specific format Then:

code

1. Confirm the format
2. Generate single output file
3. Provide download link/path

Pattern: Multi-Format Export

When: Human requests multiple formats Then:

code

1. List all requested formats
2. Generate each format sequentially
3. Report success/failure for each
4. Provide summary of all created files

Pattern: No Conversion Tools Available

When: Neither pandoc nor MCP tools are available Then:

code

1. Inform human: "Document conversion tools not available"
2. Provide structured content in clipboard-friendly format
3. Suggest alternatives:
   - Online converters (Google Docs, CloudConvert)
   - Manual copy to PowerPoint/Word
4. Mark task as partially complete

Pattern: Presentation-Optimized Content

When: Human specifically wants a presentation Then:

code

1. Restructure content into slide-sized chunks
2. Convert paragraphs to bullet points
3. Extract key phrases for slide titles
4. Limit content per slide (5-7 bullets max)
5. Add speaker notes with full context

Anti-Patterns

Anti-Pattern	Why Bad	Do Instead
Converting without confirmation	May create unwanted formats	Always confirm format with human
Overwriting existing files	Loses previous versions	Use versioned naming
Ignoring conversion errors	Human doesn't know it failed	Report errors clearly
Skipping verification	May generate empty files	Always verify output

Example

Scenario: User wants to share idea-summary-v1.md as a PowerPoint

Execution:

code

1. Execute Task Flow from task-execution-guideline skill

2. Identify Source:
   - Found: x-ipe-docs/ideas/mobile-app-idea/idea-summary-v1.md
   
3. Confirm Format:
   Human selects: PowerPoint (.pptx)
   
4. Prepare Content:
   - Restructure for slides
   - Create bullet points
   
5. Execute Conversion:
   pandoc -t pptx -o "formal-idea-summary-v1.pptx" "idea-summary-v1.md"
   
6. Verify:
   - File created: formal-idea-summary-v1.pptx (245 KB)
   
7. Report:
   "Created formal-idea-summary-v1.pptx in x-ipe-docs/ideas/mobile-app-idea/"

8. Resume Task Flow from task-execution-guideline skill

Tool Detection

At task start, detect available conversion tools:

python

# Check for pandoc
which pandoc  # or: pandoc --version

# Check for MCP document tools
# Look for MCP servers with document capabilities

# Check for python-pptx (Python library)
pip show python-pptx

# Check for python-docx (Python library)
pip show python-docx

Report available tools to human before proceeding.