dipeo-package-maintainer

Original source / Raw SKILL.md

---
name: dipeo-package-maintainer
description: Router skill for DiPeO runtime Python code (execution handlers, service architecture, domain models, LLM infrastructure). Use when task mentions node handlers, EventBus, ServiceRegistry, Envelope pattern, or domain logic. For simple tasks, handle directly; for complex work, escalate to dipeo-package-maintainer agent.
allowed-tools: Read, Grep, Glob, Bash, Skill
---

# DiPeO Package Maintainer Router

**Domain**: Runtime Python in `/dipeo/` (application, domain, infrastructure - EXCLUDING codegen and generated code).

## Quick Decision: Skill or Agent?

### ✅ Handle Directly (This Skill)
- **Simple changes**: <20 lines, 1-2 files
- **Read-only tasks**: Understanding patterns, reviewing implementation
- **Pattern lookup**: Envelope usage, service registration examples
- **Small fixes**: Typos, minor refactors, simple handler tweaks

### ❌ Escalate to Agent
- **New node handlers**: Creating handlers with complex logic
- **Service architecture**: EventBus integration, ServiceRegistry configuration
- **Domain model changes**: Conversation management, memory strategies
- **Multi-file refactoring**: Affects >2 files or cross-layer changes
- **Generated code issues**: If generated APIs don't work, escalate to dipeo-codegen-pipeline first

**Agent**: `Task(dipeo-package-maintainer, "your detailed task description")`

## Documentation Sections (Load On-Demand)

Use `Skill(doc-lookup)` with these anchors when you need detailed context:

**Architecture & Ownership**:
- `docs/agents/package-maintainer.md#your-domain-of-expertise` - Code layers and ownership
- `docs/agents/package-maintainer.md#core-architectural-principles` - Service architecture, LLM integration

**Implementation**:
- `docs/agents/package-maintainer.md#your-responsibilities` - Node handlers, services, GraphQL resolvers

**Patterns & Imports**:
- `docs/agents/package-maintainer.md#common-patterns` - Envelope, service registry, node handlers
- `docs/agents/package-maintainer.md#key-import-paths` - Common imports

**Escalation**:
- `docs/agents/package-maintainer.md#when-you-need-help-escalation-paths` - When to escalate

**Example doc-lookup call**:
```bash
python .claude/skills/doc-lookup/scripts/section_search.py \
  --query "envelope-pattern" \
  --paths docs/agents/package-maintainer.md \
  --top 1
```

## Escalation to Other Agents

**To dipeo-codegen-pipeline**: Generated code issues, TypeScript specs, new node types, GraphQL schema
**To dipeo-backend**: CLI commands, server config, database schema, MCP server

## Typical Workflow

1. **Assess complexity**: Simple pattern lookup vs. complex implementation
2. **If simple**: Load relevant section via `Skill(doc-lookup)`, provide guidance or make small change
3. **If complex**: Escalate with `Task(dipeo-package-maintainer, "task details")`
4. **Generated code problems**: First check if it's a generation issue → escalate to dipeo-codegen-pipeline