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

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

@@ -0,0 +1,153 @@
+# Skill Meta Template: Meta Skill
+
+Use this template to create skill-meta.md for meta skills. Meta skills create, validate, or manage other skills.
+
+---
+
+## Template
+
+```yaml
+---
+skill_name: x-ipe-meta-{name}
+skill_type: x-ipe-meta
+version: 1.0.0
+last_updated: {YYYY-MM-DD}
+implementation_path: .github/skills/x-ipe-meta-{name}/
+
+purpose: "{Description of what this meta skill does}"
+target_skill_types:
+  - x-ipe-task-based
+  - x-ipe-tool
+  - x-ipe-workflow-orchestration
+  - x-ipe-meta
+
+inputs:
+  - name: skill_name
+    type: string
+    required: true
+    description: Name of skill to create/manage
+    validation: "lowercase, hyphens, 1-64 chars"
+  - name: skill_type
+    type: string
+    required: true
+    description: Type of skill
+    validation: "x-ipe-task-based | x-ipe-tool | x-ipe-workflow-orchestration | x-ipe-meta"
+  - name: user_request
+    type: string
+    required: true
+    description: Description of what the skill should do
+  - name: examples
+    type: array
+    required: false
+    description: Concrete usage examples
+
+outputs:
+  - name: skill_package
+    type: skill_package
+    path: ".github/skills/{skill_name}/"
+    description: Complete skill with SKILL.md and bundled resources
+  - name: skill_meta
+    type: file
+    path: "x-ipe-docs/skill-meta/{skill_name}/skill-meta.md"
+    description: Skill specification with acceptance criteria
+
+acceptance_criteria:
+  must:
+    - id: AC-M01
+      description: SKILL.md exists with valid frontmatter (name, description)
+      test_method: file_exists
+      expected: ".github/skills/{skill_name}/SKILL.md with YAML frontmatter"
+    - id: AC-M02
+      description: SKILL.md body under 500 lines
+      test_method: structure_validation
+      expected: "wc -l < 500"
+    - id: AC-M03
+      description: Section order follows cognitive flow per skill type
+      test_method: content_check
+      expected: "Sections in order: Purpose → DoR → Execution → DoD → Examples"
+    - id: AC-M04
+      description: Importance signals use keywords (BLOCKING, CRITICAL, MANDATORY)
+      test_method: content_check
+      expected: "No emoji importance signals (⛔, ⚠️)"
+    - id: AC-M05
+      description: references/examples.md exists
+      test_method: file_exists
+      expected: "references/examples.md with at least 1 example"
+  should:
+    - id: AC-S01
+      description: DoR/DoD use XML checkpoint format
+      test_method: structure_validation
+      expected: "<definition_of_ready> and <definition_of_done> tags"
+    - id: AC-S02
+      description: Description includes trigger phrases
+      test_method: content_check
+      expected: "Triggers on requests like..."
+    - id: AC-S03
+      description: Cross-references validated
+      test_method: custom
+      expected: "grep -r {skill-name} shows correct registrations"
+  could:
+    - id: AC-C01
+      description: Sub-agent workflow used for complex skills
+      test_method: structure_validation
+      expected: "DAG workflow for 5+ step skills"
+  wont:
+    - id: AC-W01
+      description: Runtime code generation
+      reason: "Skills provide guidance, not executable code"
+
+evaluation:
+  self_check:
+    - "File existence checks"
+    - "Line count validation"
+    - "Section order validation"
+    - "Keyword vs emoji check"
+  judge_agent:
+    - "Quality of execution procedure clarity"
+    - "Completeness of acceptance criteria coverage"
+
+workflow:
+  sub_agent_dag: true
+  test_driven: true
+  supports_iteration: true
+
+dependencies:
+  skills:
+    - lesson-learned
+  artifacts:
+    - path: "x-ipe-docs/skill-meta/.templates/"
+      description: "Skill meta templates for different skill types"
+  templates:
+    - task-type-skill/skill-meta-task-type.md
+    - task-category-skill/skill-meta-task-category.md
+    - tool-skill/skill-meta-tool.md
+    - workflow-orchestration-skill/skill-meta-workflow-orchestration.md
+    - meta-skill/skill-meta-meta.md
+---
+```
+
+---
+
+## Field Reference
+
+| Section | Field | Required | Description |
+|---------|-------|----------|-------------|
+| Identity | skill_name | Yes | `x-ipe-meta-{name}` format |
+| Identity | version | Yes | Semver format |
+| Purpose | purpose | Yes | Single sentence description |
+| Purpose | target_skill_types | Yes | Which skill types this can manage |
+| Interface | inputs | Yes | Required and optional parameters |
+| Interface | outputs | Yes | skill_package and skill_meta |
+| Acceptance | must | Yes | All must pass for merge |
+| Acceptance | should | Yes | 80% must pass |
+| Testing | test_scenarios | Recommended | happy_path, edge_cases, error_cases |
+| Evaluation | self_check | Yes | Automated checks |
+| Evaluation | judge_agent | Optional | Quality assessment |
+
+---
+
+## Test Scenarios
+
+- **Create Task Type:** Given task-type skill request → When create invoked → Then valid x-ipe-task-type-{name} skill produced
+- **Validate Structure:** Given draft skill → When validate invoked → Then section order issues reported
+- **Iterate on Failure:** Given failed acceptance tests → When iterate invoked → Then candidate updated and re-tested

x_ipe/resources/skills/x-ipe-skill-creator-v3/templates/skill-meta-x-ipe-task-based.md

@@ -0,0 +1,324 @@
+# Skill Meta Template: Task Type
+
+Use this template to create skill-meta.md for task-type skills. The skill-meta defines **acceptance criteria** for automated testing.
+
+---
+
+## Template
+
+```yaml
+# ═══════════════════════════════════════════════════════════
+# SKILL META - Task Type
+# ═══════════════════════════════════════════════════════════
+
+# ─────────────────────────────────────────────────────────────
+# IDENTITY
+# ─────────────────────────────────────────────────────────────
+skill_name: x-ipe-task-type-{name}
+skill_type: x-ipe-task-based
+version: "1.0.0"
+status: draft | candidate | production
+created: YYYY-MM-DD
+updated: YYYY-MM-DD
+
+# ─────────────────────────────────────────────────────────────
+# PURPOSE
+# ─────────────────────────────────────────────────────────────
+summary: |
+  {One sentence: What this skill produces and its key value.}
+
+triggers:
+  - "{trigger phrase 1}"
+  - "{trigger phrase 2}"
+
+not_for:
+  - "{alternative skill}: {when to use instead}"
+
+# ─────────────────────────────────────────────────────────────
+# WORKFLOW POSITION
+# ─────────────────────────────────────────────────────────────
+workflow:
+  category: feature-stage | requirement-stage | ideation-stage | code-refactoring-stage | standalone
+  phase: "{phase name if category != standalone}"
+  next_task_type: "{TaskName}" | null
+  human_review: true | false
+
+# ─────────────────────────────────────────────────────────────
+# INTERFACE
+# ─────────────────────────────────────────────────────────────
+inputs:
+  required:
+    - name: auto_proceed
+      type: boolean
+      default: false
+      description: Whether to auto-proceed to next task
+
+    - name: {input_name}
+      type: string | number | boolean | array | object
+      default: {value}
+      description: "{what this controls}"
+      validation: "{constraint, e.g., 'must match FEATURE-\\d+'}"
+
+  optional:
+    - name: {input_name}
+      type: string
+      default: null
+      description: "{what this controls}"
+
+outputs:
+  state:
+    - name: category
+      value: "${workflow.category}"
+    - name: status
+      value: completed | blocked
+    - name: next_task_type
+      value: "${workflow.next_task_type}"
+    - name: require_human_review
+      value: "${workflow.human_review}"
+    - name: auto_proceed
+      value: "${inputs.auto_proceed}"
+
+  artifacts:
+    - name: {artifact_name}
+      type: file | directory
+      path: "{relative path from project root}"
+      description: "{what this contains}"
+
+  data:
+    - name: {output_name}
+      type: string | object
+      description: "{what this represents}"
+
+# ─────────────────────────────────────────────────────────────
+# ACCEPTANCE CRITERIA (MoSCoW)
+# ─────────────────────────────────────────────────────────────
+acceptance_criteria:
+  must:
+    # STRUCTURE - Skill file organization
+    - id: AC-S01
+      category: structure
+      criterion: SKILL.md exists with valid frontmatter
+      test: file_exists + yaml_parse
+      expected: name and description fields present
+
+    - id: AC-S02
+      category: structure
+      criterion: references/examples.md exists
+      test: file_exists
+      expected: file contains at least 1 example
+
+    - id: AC-S03
+      category: structure
+      criterion: SKILL.md body < 500 lines
+      test: line_count
+      expected: < 500
+
+    # CONTENT - Required sections and content quality
+    - id: AC-C01
+      category: content
+      criterion: All 10 required sections present in order
+      test: section_parse
+      expected: |
+        [Frontmatter, Purpose, Important Notes, Input Parameters, 
+         Definition of Ready, Execution Flow, Execution Procedure, 
+         Output Result, Definition of Done, Patterns & Anti-Patterns, Examples]
+
+    - id: AC-C02
+      category: content
+      criterion: Frontmatter description includes WHAT + TRIGGERS
+      test: content_check
+      expected: description contains "Use when" and "Trigger"
+
+    - id: AC-C03
+      category: content
+      criterion: DoR has verifiable checkpoints
+      test: table_parse
+      expected: ≥2 rows with specific conditions (not vague terms)
+
+    - id: AC-C04
+      category: content
+      criterion: DoD has verifiable outcomes
+      test: table_parse
+      expected: ≥2 rows with measurable criteria
+
+    # BEHAVIOR - Execution produces correct results
+    - id: AC-B01
+      category: behavior
+      criterion: Skill produces expected outputs
+      test: execution
+      expected: all outputs.artifacts exist after execution
+
+    - id: AC-B02
+      category: behavior
+      criterion: Output YAML has correct structure
+      test: yaml_validate
+      expected: category is first field, all required fields present
+
+  should:
+    - id: AC-S04
+      category: structure
+      criterion: Procedure steps use pseudocode for precise operations
+      test: content_check
+      expected: ≥1 pseudocode block per procedure step
+
+    - id: AC-C05
+      category: content
+      criterion: Patterns cover common scenarios
+      test: section_parse
+      expected: ≥2 patterns with When/Then structure
+
+    - id: AC-C06
+      category: content
+      criterion: Anti-patterns prevent common mistakes
+      test: table_parse
+      expected: ≥2 anti-patterns with consequence + correction
+
+    - id: AC-B03
+      category: behavior
+      criterion: Blocking rules prevent incorrect progression
+      test: execution
+      expected: skill blocks when preconditions not met
+
+  could:
+    - id: AC-C07
+      category: content
+      criterion: Web search guidance included
+      test: content_check
+      expected: Web search terms or references indicated
+
+    - id: AC-C08
+      category: content
+      criterion: Freedom levels documented
+      test: content_check
+      expected: High/Medium/Low freedom indicators present
+
+  wont:
+    - id: AC-W01
+      criterion: Board status updates
+      reason: Handled by category skill, not task-type skill
+
+# ─────────────────────────────────────────────────────────────
+# DEPENDENCIES
+# ─────────────────────────────────────────────────────────────
+dependencies:
+  skills:
+    - name: task-execution-guideline
+      relationship: prerequisite
+      description: Must be learned before executing this skill
+
+    - name: "{category}+{board}-management"
+      relationship: integration
+      description: Called for board updates (if not standalone)
+
+  artifacts:
+    - path: "{required artifact path}"
+      description: "{what must exist before skill can run}"
+
+# ─────────────────────────────────────────────────────────────
+# TESTING
+# ─────────────────────────────────────────────────────────────
+test_scenarios:
+  happy_path:
+    - name: "{scenario name}"
+      given: "{precondition setup}"
+      when: "{action taken}"
+      then: "{expected outcome}"
+
+  edge_cases:
+    - name: "{edge case name}"
+      given: "{edge condition}"
+      when: "{action taken}"
+      then: "{handling behavior}"
+
+  error_cases:
+    - name: "{error scenario name}"
+      given: "{error condition}"
+      when: "{action taken}"
+      then: "{error response/recovery}"
+
+  blocking:
+    - name: "{blocking scenario}"
+      given: "{missing precondition}"
+      when: "{attempt to proceed}"
+      then: "BLOCKED with {message}"
+
+# ─────────────────────────────────────────────────────────────
+# EVALUATION
+# ─────────────────────────────────────────────────────────────
+evaluation:
+  self_check:
+    - "All outputs.artifacts exist"
+    - "Output YAML validates against schema"
+    - "DoD checkpoints all verified"
+
+  judge_agent:
+    - criterion: "Output quality meets production standards"
+      rubric: |
+        5: Excellent - ready for production
+        4: Good - minor improvements needed
+        3: Acceptable - some gaps
+        2: Poor - significant issues
+        1: Fail - does not meet requirements
+```
+
+---
+
+## Field Reference
+
+| Section | Field | Required | Description |
+|---------|-------|----------|-------------|
+| Identity | skill_name | Yes | `x-ipe-task-type-{name}` format |
+| Identity | version | Yes | Semver format |
+| Identity | status | Yes | draft → candidate → production |
+| Purpose | summary | Yes | Single sentence outcome |
+| Purpose | triggers | Yes | Phrases that invoke skill |
+| Purpose | not_for | Yes | What to use instead |
+| Workflow | category | Yes | Where in lifecycle |
+| Workflow | next_task_type | Yes | Chain destination or null |
+| Workflow | human_review | Yes | Pause for approval |
+| Interface | inputs.required | Yes | At minimum auto_proceed |
+| Interface | outputs.state | Yes | Task completion state |
+| Interface | outputs.artifacts | If applicable | Created files |
+| Acceptance | must | Yes | All must pass for merge |
+| Acceptance | should | Yes | 80% must pass |
+| Acceptance | could | Optional | Nice-to-have |
+| Acceptance | wont | Optional | Explicit out-of-scope |
+| Testing | happy_path | Yes | At least 1 scenario |
+| Testing | blocking | Yes | At least 1 scenario |
+| Evaluation | self_check | Yes | Automated checks |
+| Evaluation | judge_agent | Optional | Quality assessment |
+
+---
+
+## Acceptance Criteria Categories
+
+| Category | Focus | Test Methods |
+|----------|-------|--------------|
+| **structure** | File organization, sections | file_exists, line_count, section_parse |
+| **content** | Information quality, completeness | content_check, table_parse, yaml_parse |
+| **behavior** | Execution produces correct results | execution, yaml_validate |
+
+---
+
+## Test Method Reference
+
+| Method | Description | Example Expected |
+|--------|-------------|------------------|
+| file_exists | File present at path | true |
+| line_count | Count lines in file | < 500 |
+| section_parse | Extract markdown sections | [list of section names] |
+| table_parse | Parse markdown table | ≥2 rows |
+| content_check | Search for content patterns | contains "X" |
+| yaml_parse | Parse YAML/frontmatter | field present |
+| yaml_validate | Validate YAML structure | schema compliance |
+| execution | Run skill with inputs | outputs exist |
+
+---
+
+## Usage
+
+1. Copy template YAML block
+2. Fill all required fields
+3. Define acceptance criteria (focus on MUST first)
+4. Add test scenarios for key paths
+5. Save as `x-ipe-docs/skill-meta/{skill-name}/skill-meta.md`

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

@@ -0,0 +1,109 @@
+# Task Category Skill Template
+
+Task Category skills are orchestration skills called when all related task-based skills in a category finish their work.
+
+> Copy YAML, replace `{placeholders}`, delete comments. `?` = optional field.
+
+```yaml
+---
+# IDENTIFICATION
+skill_name: "x-ipe-{category}-{operation-name}"  # string, required
+skill_type: x-ipe-task-category                   # literal, required
+version: "1.0.0"                                  # semver, required
+last_updated: YYYY-MM-DD                          # date, required
+implementation_path: .github/skills/{skill_name}/
+related_skills: []                                # string[], optional
+
+# CATEGORY INTERFACE
+managed_category: "{category}"                    # string: feature-stage|requirement-stage|ideation-stage
+board_path: "x-ipe-docs/planning/{category}-board.md"
+
+entity_schema:                                    # Define entity fields
+  id:        { type: string, pattern: "{ENTITY}-NNN" }
+  status:    { type: enum, values: [pending, in_progress, completed, blocked, cancelled] }
+  title:     { type: string }
+  assignee?: { type: string }                     # ? = optional
+
+# STATE MACHINE
+states:
+  pending:     { terminal: false, transitions_to: [in_progress, cancelled] }
+  in_progress: { terminal: false, transitions_to: [completed, blocked, pending] }
+  blocked:     { terminal: false, transitions_to: [in_progress, cancelled] }
+  completed:   { terminal: true, transitions_to: [] }
+  cancelled:   { terminal: true, transitions_to: [] }
+
+# OPERATIONS (? = optional input)
+operations:
+  create: { inputs: [title, assignee?], outputs: { entity_id: string } }
+  read:   { inputs: [filter?], outputs: { items: array } }
+  update: { inputs: [entity_id, updates], outputs: { success: boolean } }
+  delete: { inputs: [entity_id], outputs: { success: boolean } }
+
+# BOARD SECTIONS
+sections:
+  - { name: "Active {entity_plural}", type: table, columns: [ID, Title, Status, Assignee, Updated] }
+  - { name: "Completed {entity_plural}", type: table, columns: [ID, Title, Completed, Notes] }
+  - { name: "Quick Stats", type: key-value, fields: [total, in_progress, completed, pending] }
+
+# ACCEPTANCE CRITERIA (MoSCoW)
+acceptance_criteria:
+  must:   [{ id: AC-001, desc: "Operations preserve data integrity" },
+           { id: AC-002, desc: "Markdown format stays valid" },
+           { id: AC-003, desc: "Stats match actual counts" }]
+  should: [{ id: AC-004, desc: "IDs follow {ENTITY}-NNN pattern" }]
+  could:  [{ id: AC-005, desc: "Auto-archive after 30 days" }]
+  wont:   [{ id: AC-006, desc: "{out_of_scope}", reason: "{why}" }]
+
+# QUALITY METRICS
+quality_metrics: { max_active_items: 50, archive_after_days: 30, complexity: medium }
+---
+```
+
+---
+
+## Field Reference
+
+| Section | Field | Required | Description |
+|---------|-------|----------|-------------|
+| Identity | skill_name | Yes | `x-ipe-{category}+{operation-name}` format |
+| Identity | skill_type | Yes | `x-ipe-task-category` |
+| Identity | version | Yes | Semver format |
+| Category | managed_category | Yes | feature-stage, requirement-stage, ideation-stage |
+| Category | board_path | Yes | Path to the board markdown file |
+| Schema | entity_schema | Yes | Define entity fields and types |
+| States | states | Yes | State machine with transitions |
+| Operations | operations | Yes | CRUD operations definition |
+| Sections | sections | Yes | Board markdown sections |
+| Acceptance | must | Yes | All must pass for merge |
+
+---
+
+## Minimal Example: Task Board Management
+
+```yaml
+# Only showing fields that differ from template defaults
+skill_name: "x-ipe-task-board-management"
+managed_category: "task"
+board_path: "x-ipe-docs/planning/task-board.md"
+
+entity_schema:  # Extended fields
+  type:        { type: enum, values: [feature, bug, chore, spike] }
+  feature_ref?: { type: reference, target: "feature-board" }
+
+sections:
+  - { name: "Active Tasks", columns: [ID, Type, Title, Status, Assignee, Updated, Links] }
+```
+
+## Example: Feature Board Management
+
+```yaml
+skill_name: "x-ipe-feature-board-management"
+managed_category: "feature-stage"
+board_path: "x-ipe-docs/planning/feature-board.md"
+
+entity_schema:
+  feature_id: { type: string, pattern: "FEATURE-NNN" }
+  status:     { type: enum, values: [planning, in_progress, review, completed] }
+  title:      { type: string }
+  tasks:      { type: array, items: { type: reference, target: "task-board" } }
+```