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 ownershipdocs/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 handlersdocs/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:
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
- Assess complexity: Simple pattern lookup vs. complex implementation
- If simple: Load relevant section via
Skill(doc-lookup), provide guidance or make small change
- If complex: Escalate with
Task(dipeo-package-maintainer, "task details")
- Generated code problems: First check if it's a generation issue → escalate to dipeo-codegen-pipeline
1---2name: dipeo-package-maintainer3description: 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.4---5
6# DiPeO Package Maintainer Router
7
8**Domain**: Runtime Python in `/dipeo/` (application, domain, infrastructure - EXCLUDING codegen and generated code).
9
10## Quick Decision: Skill or Agent?
11
12### ✅ Handle Directly (This Skill)
13- **Simple changes**: <20 lines, 1-2 files
14- **Read-only tasks**: Understanding patterns, reviewing implementation
15- **Pattern lookup**: Envelope usage, service registration examples
16- **Small fixes**: Typos, minor refactors, simple handler tweaks
17
18### ❌ Escalate to Agent
19- **New node handlers**: Creating handlers with complex logic
20- **Service architecture**: EventBus integration, ServiceRegistry configuration
21- **Domain model changes**: Conversation management, memory strategies
22- **Multi-file refactoring**: Affects >2 files or cross-layer changes
23- **Generated code issues**: If generated APIs don't work, escalate to dipeo-codegen-pipeline first
24
25**Agent**: `Task(dipeo-package-maintainer, "your detailed task description")`
26
27## Documentation Sections (Load On-Demand)
28
29Use `Skill(doc-lookup)` with these anchors when you need detailed context:
30
31**Architecture & Ownership**:
32- `docs/agents/package-maintainer.md#your-domain-of-expertise` - Code layers and ownership
33- `docs/agents/package-maintainer.md#core-architectural-principles` - Service architecture, LLM integration
34
35**Implementation**:
36- `docs/agents/package-maintainer.md#your-responsibilities` - Node handlers, services, GraphQL resolvers
37
38**Patterns & Imports**:
39- `docs/agents/package-maintainer.md#common-patterns` - Envelope, service registry, node handlers
40- `docs/agents/package-maintainer.md#key-import-paths` - Common imports
41
42**Escalation**:
43- `docs/agents/package-maintainer.md#when-you-need-help-escalation-paths` - When to escalate
44
45**Example doc-lookup call**:
46```bash
47python .claude/skills/doc-lookup/scripts/section_search.py \
48 --query "envelope-pattern" \
49 --paths docs/agents/package-maintainer.md \
50 --top 1
51```
52
53## Escalation to Other Agents
54
55**To dipeo-codegen-pipeline**: Generated code issues, TypeScript specs, new node types, GraphQL schema
56**To dipeo-backend**: CLI commands, server config, database schema, MCP server
57
58## Typical Workflow
59
601. **Assess complexity**: Simple pattern lookup vs. complex implementation
612. **If simple**: Load relevant section via `Skill(doc-lookup)`, provide guidance or make small change
623. **If complex**: Escalate with `Task(dipeo-package-maintainer, "task details")`
634. **Generated code problems**: First check if it's a generation issue → escalate to dipeo-codegen-pipeline
majiayu000