cowork-flow 0.0.12 → 0.0.13

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
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "cowork-flow",
3
- "version": "0.0.12",
3
+ "version": "0.0.13",
4
4
  "description": "CLI for installing and maintaining cowork-flow collaboration templates.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -39,8 +39,10 @@ Do not invoke `superpowers:subagent-driven-development` from this skill. Agent-t
39
39
  ### Fresh Worker Per Assignment
40
40
 
41
41
  - Spawn one agent per ready assignment. Use the assignment's `agent_type` as the Codex spawn target; built-in Codex agent types include `default`, `worker`, and `explorer`, and project or personal custom agents may add more.
42
+ - Do not request a full-history fork when you also specify `agent_type`. In Codex hosts that expose real subagent dispatch tools, full-history fork cannot be combined with `agent_type` and the spawn call will be rejected.
42
43
  - Treat `recommended_agent` as the agent-team registry match and prompt source, not as the Codex spawn target unless it also names a real Codex custom agent.
43
44
  - Spawn a fresh worker for each ready assignment. Do not reuse the main agent context as the worker context.
45
+ - When the host offers fork controls, prefer a fresh child thread with explicit prompt context over inherited full history. Put the assignment Markdown, write boundary, and any needed task facts directly in the worker prompt.
44
46
  - Use `agent-team/assignments/<assignment-id>.md` as the worker prompt body.
45
47
  - Add this scene-setting to every worker prompt: it is not alone in the codebase, it must respect the listed write boundary, it must not revert other agents' edits, and it must report changed files plus exact verification commands.
46
48
  - Dispatch multiple ready assignments in parallel only after confirming their write files do not overlap. If they overlap, dispatch them sequentially or repair the dependency graph.
@@ -1 +1 @@
1
- 0.0.12
1
+ 0.0.13