/skill-generator

name: skill-generator
disable-model-invocation: true
description: Meta-skill for creating new Claude Code skills with configurable execution modes. Supports sequential (fixed order) and autonomous (stateless) phase patterns. Use for skill scaffolding, skill creation, or building new workflows. Triggers on "create skill", "new skill", "skill generator".
allowed-tools: Agent, AskUserQuestion, Read, Bash, Glob, Grep, Write
session-mode: run

<required_reading> @~/.maestro/workflows/run-mode.md </required_reading>

Skill Generator

Meta-skill for creating new Claude Code skills with configurable execution modes.

Run Lifecycle

Follow `~/.maestro/workflows/run-mode.md`. If an orchestrator injected `run_id` / `run_dir` in the birth packet, use them and do NOT call `maestro run create`. Otherwise self-start before Phase 1:

maestro run create skill-generator --session <YYYYMMDD-skill-generator-{topic}> --intent "<short phrase>"

Session slug is ASCII-only, ≤64 chars. Retain the returned `run_id` and `run_dir`; all `{run_dir}/...` paths below refer to it. Close per Phase 5.

Pre-load (before execution)

1. **Codebase docs**: If `.workflow/codebase/ARCHITECTURE.md` exists, read for project context 2. **Specs**: `maestro load --type spec --category coding` — load coding conventions 3. **Wiki knowledge**: `maestro search "skill design optimization" --json` — top 5 entries as prior context 4. All optional — proceed without if unavailable

Architecture Overview

┌─────────────────────────────────────────────────────────────────┐
│                    Skill Generator                               │
│                                                                  │
│  Input: User Request (skill name, purpose, mode)                │
│                         ↓                                        │
│  ┌─────────────────────────────────────────────────────────┐    │
│  │  Phase 0-5: Sequential Pipeline                          │    │
│  │  ┌────┐ ┌────┐ ┌────┐ ┌────┐ ┌────┐ ┌────┐             │    │
│  │  │ P0 │→│ P1 │→│ P2 │→│ P3 │→│ P4 │→│ P5 │             │    │
│  │  │Spec│ │Req │ │Dir │ │Gen │ │Spec│ │Val │             │    │
│  │  └────┘ └────┘ └────┘ └─┬──┘ └────┘ └────┘             │    │
│  │                         │                                │    │
│  │                    ┌────┴────┐                           │    │
│  │                    ↓         ↓                           │    │
│  │              Sequential  Autonomous                      │    │
│  │              (phases/)   (actions/)                      │    │
│  └─────────────────────────────────────────────────────────┘    │
│                         ↓                                        │
│  Output: .claude/skills/{skill-name}/ (complete package)        │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

Execution Modes

Mode 1: Sequential (Fixed Order)

Traditional linear execution model, phases execute in numeric prefix order.

Phase 01 -> Phase 02 -> Phase 03 -> ... -> Phase N

**Use Cases**:

• Pipeline tasks (collect -> analyze -> generate)
• Strong dependencies between phases
• Fixed output structure

**Examples**: `software-manual`, `copyright-docs`

Mode 2: Autonomous (Stateless Auto-Select)

Intelligent routing model, dynamically selects execution path based on context.

---------------------------------------------------
                Orchestrator Agent
   (Read state -> Select Phase -> Execute -> Update)
---------------------------------------------------
                |
    ---------+----------+----------
    |        |          |
  Phase A   Phase B    Phase C
  (standalone)  (standalone)  (standalone)

**Use Cases**:

• Interactive tasks (chat, Q&A)
• No strong dependencies between phases
• Dynamic user intent response required

**Examples**: `issue-manage`, `workflow-debug`

Key Design Principles

1. **Mode Awareness**: Automatically recommend execution mode based on task characteristics 2. **Skeleton Generation**: Generate complete directory structure and file skeletons 3. **Standards Compliance**: Strictly follow `specs/skill-requirements.md` 4. **Extensibility**: Generated Skills are easy to extend and modify

---

Required Prerequisites

IMPORTANT: Before any generation operation, read the following specification documents. Generating without understanding these standards will result in non-conforming output.

Core Specifications (Mandatory Read)

| Document | Purpose | Priority | |----------|---------|----------| | [specs/skill-requirements.md](specs/skill-requirements.md) | Skill design spec - defines structure, naming, quality standards | **P0 - Critical** | | [specs/reference-docs-spec.md](specs/reference-docs-spec.md) | Reference document generation spec - ensures generated Skills have proper phase-based Reference Documents with usage timing guidance | **P0 - Critical** |

Template Files (Read Before Generation)

| Document | Purpose | |----------|---------| | [templates/skill-md.md](templates/skill-md.md) | SKILL.md entry file template | | [templates/sequential-phase.md](templates/sequential-phase.md) | Sequential Phase template | | [templates/autonomous-orchestrator.md](templates/autonomous-orchestrator.md) | Autonomous Orchestrator template | | [templates/autonomous-action.md](templates/autonomous-action.md) | Autonomous Action template | | [templates/code-analysis-action.md](templates/code-analysis-action.md) | Code Analysis Action template | | [templates/llm-action.md](templates/llm-action.md) | LLM Action template | | [templates/script-template.md](templates/script-template.md) | Unified Script Template (Bash + Python) |

Specification Documents (Read as Needed)

| Document | Purpose | |----------|---------| | [specs/execution-modes.md](specs/execution-modes.md) | Execution Modes Specification | | [specs/skill-requireme