x-ipe 1.0.23__py3-none-any.whl → 1.0.25__py3-none-any.whl

x_ipe/resources/skills/x-ipe-skill-creator/references/workflows.md

@@ -1,110 +0,0 @@
-# Workflow Patterns
-
-## Sequential Workflows
-
-For complex tasks, break operations into clear, sequential steps. It is often helpful to give AI Agent an overview of the process towards the beginning of SKILL.md:
-
-```markdown
-Execute {Task Type Name} by following these steps in order:
-
-| Step | Name | Action | Gate to Next |
-|------|------|--------|--------------|
-| 1 | Analyze | Parse input and understand scope | Understanding complete |
-| 2 | Plan | Create execution plan | Plan approved |
-| 3 | Execute | Perform the main action | Execution complete |
-| 4 | Verify | Check results against criteria | Verification passed |
-| 5 | Complete | Finalize and output results | Done |
-```
-
-## Conditional Workflows
-
-For tasks with branching logic, guide AI Agent through decision points:
-
-```markdown
-1. Determine the modification type:
-   **Creating new content?** → Follow "Creation workflow" below
-   **Editing existing content?** → Follow "Editing workflow" below
-
-2. Creation workflow: [steps]
-3. Editing workflow: [steps]
-```
-
-## X-IPE Specific Workflow Patterns
-
-### Task Type Execution Flow
-
-Every task type skill should include an Execution Flow table:
-
-```markdown
-## Execution Flow
-
-Execute {Task Type Name} by following these steps in order:
-
-| Step | Name | Action | Gate to Next |
-|------|------|--------|--------------|
-| 1 | {Name} | {Brief action} | {Gate condition} |
-| 2 | {Name} | {Brief action} | {Gate condition} |
-| 3 | Complete | Verify DoD, request human review | Human review |
-
-**⛔ BLOCKING RULES:**
-- {Rule 1}: {Description}
-- {Rule 2}: {Description}
-```
-
-### Operation-Based Workflows (Skill Category)
-
-For skills that provide CRUD operations:
-
-```markdown
-## Operations
-
-### Operation 1: {Name}
-
-**When:** {Trigger condition}
-**Then:** {What happens}
-
-```
-1. {Step 1}
-2. {Step 2}
-3. Return {result}
-```
-
-### Operation 2: {Name}
-
-**When:** {Trigger condition}
-**Then:** {What happens}
-
-```
-Input: {Input description}
-
-Process:
-1. {Step 1}
-2. IF {condition}:
-   → {Action A}
-   ELSE:
-   → {Action B}
-3. {Step 3}
-```
-```
-
-### Blocking Rules Pattern
-
-Use for critical checkpoints that must not be skipped:
-
-```markdown
-**⛔ BLOCKING RULES:**
-- Step 3: Continue asking until ALL ambiguities resolved
-- Step 5 → Human Review: Human MUST approve before proceeding
-- Step 2: MUST validate input before processing
-```
-
-### Gate Conditions
-
-Common gate condition patterns:
-
-| Gate Type | Example |
-|-----------|---------|
-| Completion | "Document created", "Analysis complete" |
-| Validation | "All tests pass", "Schema valid" |
-| Approval | "Human review", "Approval received" |
-| Threshold | "Coverage ≥ 80%", "Score > 0.9" |

x_ipe/resources/skills/x-ipe-skill-creator/templates/references/examples.md

@@ -1,113 +0,0 @@
-# {Skill Name} - Examples
-
-> This file contains detailed execution examples for the {skill-name} skill.
-> Reference from SKILL.md: `See [references/examples.md](references/examples.md)`
-
----
-
-## Example 1: {Scenario Name}
-
-**Request:** "{Example request from user}"
-
-**Context:**
-- {Relevant context 1}
-- {Relevant context 2}
-
-**Execution:**
-```
-1. Execute Task Flow from task-execution-guideline skill
-
-2. {Step 1 - DoR Check}:
-   - Verify prerequisite 1: ✓
-   - Verify prerequisite 2: ✓
-
-3. {Step 2 - Main Action}:
-   - {Detail 1}
-   - {Detail 2}
-   - {Detail 3}
-
-4. {Step 3 - Verification}:
-   - Check output 1: ✓
-   - Check output 2: ✓
-
-5. Return Task Completion Output:
-   status: completed
-   category: {category}
-   next_task_type: {Next Task Type}
-   require_human_review: {Yes | No}
-   task_output_links:
-     - {output path 1}
-     - {output path 2}
-
-6. Resume Task Flow from task-execution-guideline skill
-```
-
-**Output Files Created:**
-- `{path/to/output1}` - {description}
-- `{path/to/output2}` - {description}
-
----
-
-## Example 2: {Edge Case Scenario}
-
-**Request:** "{Edge case request}"
-
-**Context:**
-- {Special condition 1}
-- {Special condition 2}
-
-**Execution:**
-```
-1. {Handle edge case step 1}
-2. {Handle edge case step 2}
-3. {Return appropriate output}
-```
-
-**Notes:**
-- {Important consideration for this edge case}
-
----
-
-## Example 3: {Error Handling Scenario}
-
-**Request:** "{Request that triggers error path}"
-
-**Context:**
-- {Missing prerequisite or invalid state}
-
-**Execution:**
-```
-1. DoR Check:
-   - Prerequisite 1: ✗ NOT MET
-
-2. BLOCKED - Cannot proceed
-   - Reason: {why blocked}
-   - Action: {what to do}
-
-3. Return to human:
-   "Cannot proceed with {task}. 
-    Missing: {what's missing}
-    Please: {action needed}"
-```
-
----
-
-## Template Notes
-
-When creating examples for a new skill:
-
-1. **Include at minimum:**
-   - One happy path example (Example 1)
-   - One edge case example (Example 2)
-   - One error/blocked scenario (Example 3)
-
-2. **Example structure:**
-   - Request: What the user asked
-   - Context: Relevant state/conditions
-   - Execution: Step-by-step with checkmarks
-   - Output: Files created and completion output
-
-3. **Keep examples realistic:**
-   - Use concrete file paths and values
-   - Show actual output format
-   - Include verification steps

x_ipe/resources/skills/x-ipe-skill-creator/templates/skill-category-skill.md

@@ -1,296 +0,0 @@
-# Skill Category Template
-
-Use this template when creating a skill that manages boards or category-level data.
-
----
-
-```markdown
----
-name: {category}+{operation-name}
-description: {Brief description of what this skill manages}. {When to use}. Provides operations for {operation types}.
----
-
-# {Skill Name}
-
-## Purpose
-
-AI Agents follow this skill to {what the skill manages}. This skill {mandatory/optional context}.
-
-**Operations:**
-1. **{Operation 1}** - {Brief description}
-2. **{Operation 2}** - {Brief description}
-3. **{Operation 3}** - {Brief description}
-4. **{Operation 4}** - {Brief description}
-
----
-
-## Important Notes
-
-**Important:** {Any critical notes about skill usage}
-
-**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.
-
----
-
-## Input: {Data Model Name}
-
-This skill receives the {Data Model Name} from {source}:
-
-```yaml
-{DataModel}:
-  # Core fields
-  {field_1}: {type/description}
-  {field_2}: {type/description}
-  {field_3}: {type/description}
-  
-  # Execution fields
-  {field_4}: {type/description}
-  {field_5}: {type/description}
-  
-  # Control fields
-  {field_6}: {type/description}
-```
-
----
-
-## {Entity} States
-
-| State | Terminal? | Description |
-|-------|-----------|-------------|
-| `{state_1}` | No | {Description} |
-| `{state_2}` | No | {Description} |
-| `{state_3}` | No | {Description} |
-| `{state_4}` | Yes | {Description} |
-| `{state_5}` | Yes | {Description} |
-
-### Valid Transitions
-
-```
-{state_1} → {state_2}
-{state_2} → {state_4} | {state_3} | {state_5}
-{state_3} → {state_2}
-```
-
----
-
-## {Board/Entity} Operations
-
-### Operation 1: {Operation Name}
-
-**When:** {Trigger condition}
-**Then:** {What happens}
-
-```
-1. {Step 1}
-2. {Step 2}
-3. {Step 3}
-4. Return {result}
-```
-
-### Operation 2: {Operation Name}
-
-**When:** {Trigger condition}
-**Then:** {What happens}
-
-```
-Input: {Input description}
-
-Process:
-1. {Step 1}
-2. {Step 2}
-3. {Step 3}
-```
-
-### Operation 3: {Operation Name}
-
-**When:** {Trigger condition}
-**Then:** {What happens}
-
-```
-Input: {Input description}
-
-Process:
-1. {Step 1}
-2. IF {condition}:
-   → {Action}
-3. {Step 3}
-4. Update {what}
-```
-
-### Operation 4: {Operation Name}
-
-**When:** {Trigger condition}
-**Then:** {What happens}
-
-```
-Query Types:
-1. By {field_1}: {Description}
-2. By {field_2}: {Description}
-3. By {field_3}: {Description}
-
-Return: {What is returned}
-```
-
-### Operation 5: Validate {Entity} Integrity
-
-**When:** ANY operation is performed
-**Then:** Validate and fix issues
-
-```
-Process:
-1. Scan {section 1}:
-   FOR each {item} in {section}:
-     IF {condition}:
-       → {Fix action}
-       → Log: "{message}"
-
-2. Scan {section 2}:
-   FOR each {item} in {section}:
-     IF {condition}:
-       → {Fix action}
-
-3. Reconcile {stats/counts}:
-   - {Check 1}
-   - {Check 2}
-
-4. Return validation report
-```
-
-**⚠️ MANDATORY:** This operation runs automatically as the final step of ALL other operations.
-
----
-
-## {Board/Data} Sections
-
-The {board/data store} has these sections:
-
-### {Section 1 Name}
-```yaml
-{field}: {default value}
-```
-
-### {Section 2 Name}
-| Column 1 | Column 2 | Column 3 | Column 4 |
-|----------|----------|----------|----------|
-
-Contains: {What goes here}
-⛔ **{Constraint}**
-
-### {Section 3 Name}
-| Column 1 | Column 2 | Column 3 |
-|----------|----------|----------|
-
-Contains: {What goes here}
-✅ **{Requirement}**
-
----
-
-## Status Symbols
-
-| Status | Symbol | Description |
-|--------|--------|-------------|
-| {status_1} | {emoji} | {Description} |
-| {status_2} | {emoji} | {Description} |
-| {status_3} | {emoji} | {Description} |
-| {status_4} | {emoji} | {Description} |
-
----
-
-## Templates
-
-- `templates/{template-1}.md` - {Description}
-- `templates/{template-2}.yaml` - {Description}
-
----
-
-## Examples
-
-### Example 1: {Example Name}
-
-**Request:** "{Example request}"
-
-```
-Step 1: {Action}
-→ {Detail}
-
-Step 2: {Action}
-→ {Detail}
-
-Step 3: {Action}
-→ {Detail}
-
-Result: {Outcome}
-```
-
-### Example 2: {Example Name}
-
-**Request:** "{Example request}"
-
-```
-Step 1: {Action}
-→ {Detail}
-
-Step 2: {Action}
-→ {Detail}
-
-Result: {Outcome}
-```
-
-### Example 3: {Example Name}
-
-**Scenario:** {Scenario description}
-
-```
-Initial State:
-  {Section}:
-    - {Item 1}
-    - {Item 2}
-
-Step 1: {Action}
-→ {Result}
-
-Step 2: {Action}
-→ {Result}
-
-Final State:
-  {Section}:
-    - {Item 1}
-    - {Item 2}
-```
-```
-
----
-
-## Template Usage Notes
-
-### Required Sections (Must Include)
-
-1. **Frontmatter** - name (category+operation format) and description
-2. **Purpose** - what skill manages with operation list
-3. **Important Notes** - critical usage notes
-4. **Input Data Model** - YAML schema of input
-5. **States** - valid states and transitions
-6. **Operations** - all CRUD operations
-7. **Board/Data Sections** - structure of managed data
-8. **Status Symbols** - visual indicators
-9. **Templates** - reference to template files
-10. **Examples** - at least 2-3 concrete examples
-
-### Optional Sections (Add if Needed)
-
-- **Legend** - if categories or types need explanation
-- **Integration** - if other skills call this skill
-- **Notes** - additional guidance
-
-### Naming Convention
-
-Skill category skills use compound names:
-- `{category}+{operation-name}`
-- Examples:
-  - `feature-stage+feature-board-management`
-  - `requirement-stage+requirement-board-management`
-  - `ideation-stage+ideation-board-management`
-
-For standalone board management:
-- `{entity}-board-management`
-- Example: `task-board-management`