oh-my-customcode 0.35.1 → 0.35.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -165,10 +165,10 @@ Use `context: fork` for skills that orchestrate multi-agent workflows. Cap at **
|
|
|
165
165
|
| Multi-agent coordination patterns | Single-agent reference skills |
|
|
166
166
|
| Task decomposition/planning | External tool integrations |
|
|
167
167
|
|
|
168
|
-
Current skills with `context: fork` (
|
|
168
|
+
Current skills with `context: fork` (8/10 cap):
|
|
169
169
|
- secretary-routing, dev-lead-routing, de-lead-routing, qa-lead-routing
|
|
170
170
|
- dag-orchestration, task-decomposition, worker-reviewer-pipeline
|
|
171
|
-
- pipeline-guards
|
|
171
|
+
- pipeline-guards
|
|
172
172
|
|
|
173
173
|
## Naming
|
|
174
174
|
|
|
@@ -6,6 +6,8 @@
|
|
|
6
6
|
|
|
7
7
|
The main conversation is the **sole orchestrator**. It uses routing skills to delegate tasks to subagents via the Agent tool (formerly Task tool). Subagents CANNOT spawn other subagents.
|
|
8
8
|
|
|
9
|
+
**Agent Teams Exception**: Agent Teams members are peers, not hierarchical subagents. Teams members CAN spawn sub-agents via the Agent tool to execute complex workflows (e.g., research teams, verification teams). This enables Teams-compatible skills like `/research` and `/deep-plan` to run inside Team members. The Teams member acts as a local orchestrator for its own sub-tasks.
|
|
10
|
+
|
|
9
11
|
**The orchestrator MUST NEVER directly write, edit, or create files. ALL file modifications MUST be delegated to appropriate subagents.**
|
|
10
12
|
|
|
11
13
|
## Self-Check (Before File Modification)
|
package/templates/manifest.json
CHANGED