Codex/recursive workflow skill tree

AGENTS.md

@@ -53,8 +53,11 @@ Author or user request
 
 - An Omniskills bundle is a deployable skills set with a `workflow.json`,
   optional `workflow.lock.json`, README, and optional local skills. Omitted
-  `kind` means workflow; first-class teams declare `kind: "team"` plus a local
-  declared `coordinator` and unique local declared `members`.
+  `kind` means workflow. A first-class team declares `kind: "team"`; its
+  `coordinator` is one declared local entry skill, and every `members[]` source
+  must be declared in `skills[]` and resolve to a child workflow with exactly
+  one local entry skill. Child dependencies expand recursively, while only the
+  root team install record is written.
 - `startup-team` under `examples/teams/startup-team` is the primary public team.
   Role workflows such as `cto`, `product-manager`, and `founding-engineer`
   remain independently installable public examples.

docs/architecture.md

@@ -52,8 +52,8 @@ Compatibility aliases:
 
 - parse and validate `workflow.json`
 - preserve omitted `kind` as a legacy workflow and validate first-class
-  `kind: "team"` manifests with a local declared `coordinator`, unique local
-  declared `members`, and no coordinator/member overlap
+  `kind: "team"` manifests with one local entry `coordinator`, unique declared
+  `members` that resolve to child workflows, and no coordinator/member overlap
 - parse and validate optional `workflow.lock.json`
 - generate deterministic skill fingerprints for local and external skill
   sources through `omniskill lock <source>`
@@ -64,6 +64,9 @@ Compatibility aliases:
 - resolve local and public git bundle sources; bare `*-team` aliases route to
   `examples/teams/<name>`, while other bare aliases route to
   `examples/workflows/<name>`
+- recursively resolve child workflows before installation, select the highest
+  declared semantic version for duplicate workflow names, deduplicate leaf
+  skills, and reject cycles with the full active workflow path
 - list skill dependency sources plus optional Skills CLI repository metadata
 - prepare looped workflow entry skill installs with copied `workflow.json`,
   generated `loop.mjs`, and generated `loop.metadata.json`
@@ -133,18 +136,34 @@ should stay aligned with `workflow.json`.
 
 A first-class team uses the same file layout under `examples/teams/<name>` and
 declares `kind: "team"`, `coordinator`, and `members` in `workflow.json`.
-`coordinator` and every `members[]` value must match a declared local
-`skills[].source`. For `startup-team`, the coordinator is marked as the callable
-entry skill: startup-goal remains the callable coordinator while the seven
-startup role skills are members. The public bundle installs as `startup-team`;
-users invoke `$startup-goal` after installation.
+The coordinator is one declared local entry skill. Every `members[]` source
+must be declared in `skills[]` and resolve to a child workflow with exactly one
+local entry skill. Member dependencies expand recursively, but only the root
+team install record is written. For `startup-team`, startup-goal remains the
+callable coordinator while seven canonical standalone role workflows provide
+the members. The public bundle installs as `startup-team`; users invoke
+`$startup-goal` after installation.
 
 `workflow.lock.json` is generated by `omniskill lock <source>`. It records
 deterministic hashes for local skill files and stable fingerprints for external
 skill sources so reviewers can see when a workflow's skill tree changed. Missing
 lock files remain valid for compatibility, but checked-in public workflows
 should include them.
 
+Parents declare only direct dependencies. A local dependency directory that
+contains `workflow.json` is a child workflow and is scanned recursively. Direct
+repository URLs, including `#subdirectory` fragments, work the same way.
+`catalog:<alias>` selects a canonical catalog workflow without making ordinary
+bare skill names ambiguous, and `installed:<name>` reopens an installed
+workflow's recorded source. `skill-tree-demo` is the minimal local example.
+
+New locks use schema `0.2`: they store the selected workflow nodes and edges,
+exact git commits, and fingerprints for the fully expanded leaf skill set.
+Locked git children fetch their recorded commit directly on repeat installs.
+Legacy `0.1` locks remain valid for flat workflows; once a child workflow is
+detected, authors must regenerate the lock. Child workflows with the same name
+must declare valid semantic versions, and the highest version's subtree wins.
+
 Loop-enabled workflows declare `loop` in `workflow.json`, mark exactly one local
 skill with `entry: true`, and keep phase instructions in `steps[].instruction`.
 `loop.script` names the generated compatibility runner output path, usually

docs/landing-content.md

@@ -424,7 +424,7 @@ debugging, review, and verification.
 Skills:
 
 - `founding-engineer`: Set the implementation frame
-- `implement`: Implement the planned change
+- `mattpocock:implement`: Implement the planned change
 - `mattpocock:tdd`: Use test-first development
 - `mattpocock:diagnosing-bugs`: Diagnose failures
 - `mattpocock:code-review`: Review behavior and risk
@@ -434,7 +434,7 @@ Ordered skill path:
 
 1. Brief -> `founding-engineer`
    - Read the plan and acceptance criteria.
-2. Implement -> `implement`
+2. Implement -> `mattpocock:implement`
    - Ship the smallest correct slice.
 3. TDD -> `mattpocock:tdd`
    - Keep tests close to changed behavior.

docs/landing-content.zh-Hant.md

@@ -268,9 +268,9 @@ npx omniskill@latest install founding-engineer
 
 Description：Implementation lane，聚焦 smallest correct change：tests、debugging、review、verification。
 
-Skills：`founding-engineer`、`implement`、`mattpocock:tdd`、`mattpocock:diagnosing-bugs`、`mattpocock:code-review`、`superpowers:verification-before-completion`。
+Skills：`founding-engineer`、`mattpocock:implement`、`mattpocock:tdd`、`mattpocock:diagnosing-bugs`、`mattpocock:code-review`、`superpowers:verification-before-completion`。
 
-Ordered skill path：Brief -> `founding-engineer`；Implement -> `implement`；TDD -> `mattpocock:tdd`；Debug -> `mattpocock:diagnosing-bugs`；Review -> `mattpocock:code-review`；Verify -> `superpowers:verification-before-completion`。
+Ordered skill path：Brief -> `founding-engineer`；Implement -> `mattpocock:implement`；TDD -> `mattpocock:tdd`；Debug -> `mattpocock:diagnosing-bugs`；Review -> `mattpocock:code-review`；Verify -> `superpowers:verification-before-completion`。
 
 ### QA Lead