x-ipe-task-based-ideation

name	x-ipe-task-based-ideation
description	Learn and refine user ideas through brainstorming. Use when user uploads idea files to Workplace. Analyzes content, asks clarifying questions, and produces structured idea summary. Triggers on "ideate", "brainstorm", "refine idea", "analyze my idea".

Task-Based Skill: Ideation

Purpose

Learn and refine user ideas through collaborative brainstorming by:

1. Analyzing uploaded idea files from Workplace
2. Generating an initial understanding summary
3. Asking clarifying questions to brainstorm with user
4. Creating a structured idea summary document with visual infographics
5. Preparing for Idea Mockup, Idea to Architecture, or Requirement Gathering

---

Important Notes

BLOCKING: Learn x-ipe-workflow-task-execution skill before executing this skill.

CRITICAL: Only use tools that are explicitly enabled (true) in x-ipe-docs/config/tools.json under stages.ideation. Only true counts as enabled -- false, absent, or any other value means DISABLED. The tools.json config is the single source of truth for which tools are allowed.

Note: If Agent does not have skill capability, go to .github/skills/ folder to learn skills. SKILL.md is the entry point.

Workflow Mode: When execution_mode == "workflow-mode", the completion step MUST run the workflow update script via bash: python3 .github/skills/x-ipe-tool-x-ipe-app-interactor/scripts/workflow_update_action.py with workflow_name from workflow.name input, action from workflow.action input, status: "done", and a deliverables keyed dict using ONLY the extract tags defined in workflow-template.json for this action (format: {"tag-name": "path/to/file"}). Do NOT pass a flat list of file paths. Verify the script exits with code 0 before marking the task complete.

IMPORTANT: When process_preference.interaction_mode == "dao-represent-human-to-interact", NEVER stop to ask the human. Instead, call x-ipe-assistant-user-representative-Engineer to get the answer. The DAO skill acts as the human representative and will provide the guidance needed to continue.

---

Input Parameters

input:
  task_id: "{TASK-XXX}"
  task_based_skill: "x-ipe-task-based-ideation"
  
  category: ideation-stage
  next_task_based_skill:
    - skill: "x-ipe-task-based-idea-mockup"
      condition: "Create visual mockup of the idea"
    - skill: "x-ipe-task-based-idea-to-architecture"
      condition: "Create architecture diagram for the idea"
    - skill: "x-ipe-task-based-share-idea"
      condition: "Share the refined idea with stakeholders"
    - skill: "x-ipe-task-based-requirement-gathering"
      condition: "Skip to requirements if idea is already clear"
  process_preference:
    interaction_mode: "{from input process_preference.interaction_mode}"
  
  # Execution context (passed by x-ipe-workflow-task-execution)
  execution_mode: "free-mode | workflow-mode"  # default: free-mode
  workflow:
    name: "N/A"  # workflow name from workflow-{name}.json (NOT the idea folder name), default: N/A
    action: "refine_idea"  # hardcoded — this skill ALWAYS updates the refine_idea action
    extra_context_reference:  # optional, default: N/A for all refs
      raw-ideas: 
       
   
   
   

Input Initialization

<input_init>
  <field name="task_id" source="x-ipe+all+task-board-management (auto-generated)" />
  <field name="execution_mode" source="x-ipe-workflow-task-execution (from --workflow-mode@{name})" />
  <field name="workflow.name" source="x-ipe-workflow-task-execution (from --workflow-mode@{name})">
    NOTE: workflow.name is the {name} part from workflow-{name}.json filename — it is NOT the idea folder name.
    The idea folder name is auto-generated as wf-{NNN}-{sanitized-idea-name} under x-ipe-docs/ideas/.
  </field>
  <field name="process_preference.interaction_mode" source="from caller (x-ipe-workflow-task-execution) or default 'interact-with-human'" />

  <field name="idea_folder_path">
    <steps>
      1. IF human specifies folder path → use provided path
      2. ELSE scan x-ipe-docs/ideas/ for most recent folder
    </steps>
  </field>

  <field name="extra_instructions">
    <steps>
      1. IF human provides explicit extra instructions → use human-provided value
      2. ELSE IF x-ipe-docs/config/tools.json exists → read stages.ideation.ideation._extra_instruction field
      3. ELSE → "N/A"
    </steps>
  </>

---

Definition of Ready

<definition_of_ready>
  <checkpoint required="true">
    <name>Idea Files Uploaded</name>
    <verification>Files exist in x-ipe-docs/ideas/{folder}/</verification>
  </checkpoint>
  <checkpoint required="true">
    <name>Human Available</name>
    <verification>Human available for brainstorming session</verification>
  </checkpoint>
  <checkpoint required="true">
    <name>Idea Folder Path Provided</name>
    <verification>Path to idea folder specified</verification>
  </checkpoint>
</definition_of_ready>

---

Execution Flow

Phase	Step	Name	Action	Gate
1. 博学之 (Study Broadly)	1.1	Load Toolbox	Read tools.json config, output enabled tool list	config loaded
	1.2	Analyze Files	Read all files in idea folder	files analyzed
	1.3	Research	Search for common principles	research complete
2. 审问之 (Inquire Thoroughly)	2.1	Generate Summary	Create understanding summary	summary shared
	2.2	Brainstorm	Ask clarifying questions (3-5 at a time)	idea refined
3. 慎思之 (Think Carefully)	3.1	Critique	Sub-agent provides constructive feedback	feedback received
4. 明辨之 (Discern Clearly)	4.1	Improve Summary	Decide on feedback, incorporate improvements	summary finalized
5. 笃行之 (Practice Earnestly)	5.1	Generate Draft	Create idea draft, prefer enabled tools from step 1.1	draft created
	5.2	Complete	Verify DoD, output summary	Task complete
继续执行	6.1	Decide Next Action	DAO-assisted next task decision	Next action decided
继续执行	6.2	Execute Next Action	Load skill, generate plan, execute	Execution started

BLOCKING: Step 2.2 - Continue brainstorming until idea is well-defined.

BLOCKING (manual/stop_for_question): Step 5.2 - Human MUST confirm idea summary is accurate before proceeding. BLOCKING (auto): Proceed after DoD verification; auto-select next task from next_task_based_skill.

---

Execution Procedure

<procedure name="ideation">
  <!-- CRITICAL: Both DoR/DoD check elements below are MANDATORY -->
  <execute_dor_checks_before_starting/>
  <schedule_dod_checks_with_sub_agent_before_starting/>

  <phase_1 name="博学之 — Study Broadly">

    <step_1_1>
      <name>Load Ideation Toolbox Meta</name>
      <action>
        1. Check if x-ipe-docs/config/tools.json exists
        2. If exists: parse JSON, extract tools from stages.ideation
        3. If NOT exists: create default config with all tools disabled
        4. Resolve extra_instructions (see Input Initialization)
        5. Build and output the enabled tool list -- only tools with value `true` count as enabled; `false`, absent, or any other value means DISABLED
        6. BLOCKING: For each enabled tool that has a corresponding skill at .github/skills/{tool-name}/SKILL.md, LOAD that skill now. This ensures correct syntax and grammar are available before any content generation.
        7. If `x-ipe-tool-web-search` is enabled, mark it available for Step 1.3 research calls.
        8. Output format:
           ```
           Enabled tools: [list of enabled tool names]
           Disabled tools: [list of disabled tool names]
           Loaded tool skills: [list of skills loaded in step 6]
           ```
      </action>
      <output>tool_config, enabled_tool_list, extra_instructions, loaded_tool_skills</output>
    </step_1_1>

    <step_1_2>
      <name>Analyze Idea Files</name>
      <action>
        0. Resolve extra_context_reference inputs:
           - FOR EACH ref in [raw-ideas, uiux-reference]:
             IF workflow mode AND extra_context_reference.{ref} is a file path:
               READ the file at that path
             ELIF extra_context_reference.{ref} is "auto-detect":
               Use existing discovery logic below
             ELIF extra_context_reference.{ref} is "N/A":
               Skip this context input
             ELSE (free-mode / absent):
               Use existing behavior
        1. Navigate to x-ipe-docs/ideas/{folder}/files/
        2. Read each file (text, markdown, code, etc.)
        3. Identify key themes, concepts, and goals
        4. Note any gaps or ambiguities
      
      
        - BLOCKING: All files must be analyzed before proceeding
      
      initial_analysis
    

    
      Research Common Principles
      
        1. Identify if topic is common/established (auth, API, UI/UX, security)
        2. IF topic is common AND `x-ipe-tool-web-search` appears in enabled_tool_list:
           - Invoke `x-ipe-tool-web-search` with operation `research_topic`
           - Pass topic, research goal, and 2-3 focused questions
           - Use returned findings to document "Common Principles" and authoritative sources
           ELIF topic is common:
           - Research using existing model knowledge only
           - Note that no external citations were fetched
           ELSE: skip this step
      
      common_principles[], references[], web_research_summary
    

  

  

    
      Generate Understanding Summary
      
        1. Create summary of what you understand from Phase 1 analysis
        2. Include: Core Concept, Key Goals, Identified Components
        3. List Questions and Ambiguities
        4. List enabled tools from step 1.1
        5. Share summary with user for validation
      
      understanding_summary
    

    
      Brainstorming Session
      
        1. Ask yourself two questions, 'which mode interaction_mode is in?'
        2. Ask questions in batches (3-5 at a time) to avoid overwhelming, iterate based on user responses
        3. Wait for response based on interaction_mode condition before proceeding
        4. Build on previous answers
        5. Challenge assumptions constructively
        6. IF extra_instructions is provided and non-empty:
           - Incorporate extra_instructions as additional context/guidance for the refinement
           - Treat as user preference that supplements (not replaces) the idea content
        7. When the user describes something visual (UI layouts, flows, system structure), proactively generate visual artifacts to enrich the brainstorming -- select the most appropriate enabled tool from step 1.1's tool list for the content type

        Response source (based on interaction_mode):
        IF process_preference.interaction_mode == "dao-represent-human-to-interact":
          → Resolve ambiguities via x-ipe-assistant-user-representative-Engineer
          → Build comprehensive brainstorming notes from source material + decisions
        ELSE (interact-with-human/dao-represent-human-to-interact-for-questions-in-skill):
          → Ask human for response
      
      
        - BLOCKING: Continue until idea is well-defined
        - CRITICAL (manual/stop_for_question): Ask human for response
        - CRITICAL (auto): Resolve all ambiguities via x-ipe-assistant-user-representative-Engineer, do not ask human
        - MANDATORY: Only use tools that appear in the enabled tool list from step 1.1
      
      brainstorming_notes, artifacts[]
    

  

  

    
      Critique and Feedback
      
        1. Invoke sub-agent to review the brainstorming results and idea concept
        2. Sub-agent evaluates against quality criteria
        3. Sub-agent provides constructive feedback
      
      
        role: idea-critic
        goal: Provide constructive feedback on idea concept and brainstorming results
        model_hint: sonnet
        evaluation_criteria:
          - Clarity: Is the problem statement clear?
          - Completeness: Are all key aspects covered?
          - Consistency: Do elements align with each other?
          - Feasibility: Are goals realistic?
          - Visualization: Are enabled tools used effectively?
        feedback_format:
          - Strengths: What works well
          - Improvements: Specific actionable suggestions
          - Questions: Clarifications needed
      
      
        - CRITICAL: Feedback must be constructive, not just critical
        - MANDATORY: Include specific improvement suggestions
      
      critique_feedback
    

  

  

    
      Improve and Decide on Feedback
      
        1. Review critique feedback from step 3.1
        2. Decide which improvement suggestions to incorporate
        3. Resolve any questions raised
        4. Document decisions: which feedback accepted, which deferred, and why
        5. Finalize the approach and content direction for drafting
      
      
        - CRITICAL: All feedback items must be addressed (accepted or explicitly deferred with rationale)
      
      improvement_decisions, finalized_approach
    

  

  

    
      Generate Idea Draft
      
        1. Synthesize outputs from all phases: study (1.1-1.3), inquiry (2.1-2.2), critique (3.1), decisions (4.1)
        2. Determine version number (auto-increment)
        3. Output path: {idea_folder}/refined-idea/idea-summary-vN.md
           a. Create {idea_folder}/refined-idea/ folder if it does not exist
           b. IF folder already exists and contains previous output: clear it (overwrite mode)
           c. Write all refined output files to {idea_folder}/refined-idea/
        4. Create draft using template from templates/idea-summary.md
        5. RECOMMENDED: Use enabled tools from step 1.1's tool list to create rich visual content (diagrams, infographics, architecture views) -- select the most appropriate tool for each content type
        6. If no tools are enabled: use standard markdown (bullet lists, tables)
        7. Link to artifacts created during brainstorming
        8. Apply improvement decisions from step 4.1
      
      
        - CRITICAL: Only use tools that appear in the enabled tool list from step 1.1 -- if a tool is not in the enabled list, do NOT use it
        - MANDATORY: Include all sections from template
        - MANDATORY: File links in generated markdown MUST use project-root-relative paths so the UI can intercept them and open a preview modal. **Avoid** relative paths (`../`, `./`, `../../`) and absolute filesystem paths (`/Users/...`). **Correct:** `[spec](x-ipe-docs/requirements/EPIC-001/specification.md)`, `[skill](.github/skills/x-ipe-task-based-bug-fix/SKILL.md)`. **Wrong:** `[spec](../specification.md)`, `[spec](./specification.md)`.
        - RECOMMENDED: Prefer enabled tools over plain markdown for richer idea presentation
      
      idea_summary_path
    

    
      Complete and Request Review
      
        1. IF execution_mode == "workflow-mode":
           a. Run the workflow update script via bash (`python3 .github/skills/x-ipe-tool-x-ipe-app-interactor/scripts/workflow_update_action.py`) with:
              - workflow_name: {from context}
              - action: "refine_idea"  ← HARDCODED: always use "refine_idea", NEVER "compose_idea" or any other action
              - status: "done"
              - deliverables: {"refined-idea": "{path to idea-summary file}", "refined-ideas-folder": "{path to refined-idea/ folder}"}
           b. Log: "Workflow action status updated to done"
        2. Verify all DoD checkpoints are met
        3. Present final idea summary
        4. Ask if any aspects of the idea are missing or unclear
        5. IF human/DAO identifies gaps → revise specific sections

        Response source (based on interaction_mode):
        IF process_preference.interaction_mode == "dao-represent-human-to-interact":
          → Auto-select next task from next_task_based_skill after DoD verification
        ELSE (interact-with-human/dao-represent-human-to-interact-for-questions-in-skill):
          → Ask human if idea is complete before proceeding
      
      
        - BLOCKING (manual/stop_for_question): Human MUST confirm idea is complete before proceeding
        - BLOCKING (auto): Proceed after DoD verification; auto-select next task
      
      next_task_choice, workflow_action_updated
    

  

  
    
      Decide Next Action
      Collect task_completion_output. IF interaction_mode == "dao-represent-human-to-interact": invoke x-ipe-assistant-user-representative-Engineer with type: "routing", completed_skill_output, next_task_based_skill. ELSE: present next task suggestion to human.
      
        - BLOCKING (manual): Human MUST confirm or redirect
        - BLOCKING (auto): Auto-select next task via DAO after DoD verification
      
      Next action decided
    
    
      Execute Next Action
      Load target skill's SKILL.md, generate execution plan, start from first phase.
      MUST load skill before executing — follows target skill's procedure.
      Next task execution started
    
  

---

Output Result

task_completion_output:
  category: ideation-stage
  status: completed | blocked
  next_task_based_skill:
    - skill: "x-ipe-task-based-idea-mockup"
      condition: "Create visual mockup of the idea"
    - skill: "x-ipe-task-based-idea-to-architecture"
      condition: "Create architecture diagram for the idea"
    - skill: "x-ipe-task-based-share-idea"
      condition: "Share the refined idea with stakeholders"
    - skill: "x-ipe-task-based-requirement-gathering"
      condition: "Skip to requirements if idea is already clear"
  process_preference:
    interaction_mode: "{from input process_preference.interaction_mode}"
  task_output_links:
    - "x-ipe-docs/ideas/{folder}/refined-idea/idea-summary-vN.md"
    - "x-ipe-docs/ideas/{folder}/refined-idea/"
  # Dynamic attributes
  execution_mode: "{from input}"
  workflow:
    name: "{from input}"
  workflow_action: "{workflow.action}"   # triggers workflow status update when execution_mode == workflow-mode
  workflow_action_updated: true   
   
   
   
   

---

Definition of Done

CRITICAL: Use a sub-agent to validate DoD checkpoints independently.

<definition_of_done>
  <checkpoint required="true">
    <name>Config Loaded</name>
    <verification>x-ipe-docs/config/tools.json loaded, enabled tool list output, and enabled skill-backed tools loaded</verification>
  </checkpoint>
  <checkpoint required="true">
    <name>Files Analyzed</name>
    <verification>All files in idea folder analyzed</verification>
  </checkpoint>
  <checkpoint required="true">
    <name>Understanding Summary Shared</name>
    <verification>Initial understanding summary shared with user</verification>
  </checkpoint>
  <checkpoint required="true">
    <name>Brainstorming Complete</name>
    <verification>Idea is well-defined with clear goals</verification>
  </>
  
    Draft Created
    Idea draft generated, enabled tools from step 1.1 used where appropriate
  
  
    Critique Received
    Sub-agent provided constructive feedback
  
  
    Feedback Addressed
    All critique items addressed — accepted or explicitly deferred with rationale
  
  
    Summary Created and Complete
    x-ipe-docs/ideas/{folder}/refined-idea/idea-summary-vN.md exists with all sections filled and key decisions documented
  
  
    Principles Researched
    Common principles researched if topic is established; web-search tool used when enabled and needed
  
  
    Workflow Action Status Updated
    If execution_mode == "workflow-mode", ran `workflow_update_action.py` script with status "done" and deliverables keyed dict
  

MANDATORY: After completing this skill, return to x-ipe-workflow-task-execution to continue the task execution flow.

---

Patterns & Anti-Patterns

Pattern	When	Then
Raw Notes Upload	Unstructured notes/braindump	Extract themes → organize → ask per category → structure
Technical Spec	Detailed tech spec uploaded	Validate feasibility → ask about goals → identify missing context
Conflicting Ideas	Files contain conflicts	Surface conflicts → ask to prioritize → evaluate trade-offs

Anti-Pattern	Why Bad	Do Instead
Summarizing without questions	Misses refinement	Engage in brainstorming
Too many questions at once	Overwhelms user	Batch 3-5 questions
Accepting at face value	May miss issues	Challenge constructively
Ignoring tools.json	Uses wrong tools	Always check enabled tool list from step 1.1

---

Examples

See references/examples.md for concrete execution examples:

• Business plan ideation with tools enabled
• Ideation without tools (all disabled)
• Missing config file handling