sync: agent-ops from agentic-framework v1.1.15

agent-ops/skills/common/code-review/SKILL.md

@@ -29,7 +29,10 @@ Filename rules:
 Multi-plan runtime contract:
 
 - Multi-plan work is represented as multiple task directories. Each directory owns exactly one normal active plan file and one normal active review file.
-- Directory names may encode runtime scheduling metadata. Preserve them verbatim; do not normalize, reinterpret, or choose execution order by agent judgment.
+- Multi-plan task directory names encode runtime scheduling metadata:
+  - `NN_{task_name}` has no runtime dependencies.
+  - `NN+PP[,QQ...]_{task_name}` depends on the listed earlier task indices.
+- Directory names are the runtime dependency source of truth. Preserve them verbatim; do not normalize, reinterpret, infer extra dependencies from numeric order, or choose execution order by agent judgment.
 - If the user/runtime names a task directory, review that directory even when other active review files exist.
 
 Review routing rules:

agent-ops/skills/common/plan/SKILL.md

@@ -31,14 +31,19 @@ Task directory naming rules:
 - A single-plan task uses `agent-task/{task_name}/` with a short snake_case task name.
 - If one plan is not enough, split the work into multiple task directories. Each directory owns exactly one normal active plan file and one normal active review stub.
 - Multi-plan output is a set of independent `PLAN-{build_lane}-GNN.md` + `CODE_REVIEW-{review_lane}-GNN.md` pairs across multiple folders, not multiple plan files inside one folder.
-- Multi-plan task directory names must start with the current task's execution-order index: `01_{task_name}`, `02_{task_name}`, `03_{task_name}`, and so on. The leading number is always the current task index and must increase across sibling task directories.
-- Use `_` after the index for a task that can start independently at that point: `01_{task_name}`, `03_{task_name}`.
-- Use `+` instead of `_` after the index for a task that depends on an earlier task: `02+{task_name}`. Do not put predecessor numbers in the directory name.
-- Record the exact predecessor task directory or directories in the plan's `의존 관계 및 구현 순서` section.
-- Example: split a common core plus two app integrations as `01_core`, `02+edge_integration`, `03+node_integration`. In both `02+...` and `03+...`, write that they depend on `agent-task/01_core`. The `+` marker does not mean `03+...` depends on `02+...`; if `03+...` also depends on `02+...`, say so explicitly in `의존 관계 및 구현 순서`.
-- Example: split three sequential tasks as `01_schema`, `02+migration`, `03+api`. In `02+migration`, list `agent-task/01_schema` as predecessor. In `03+api`, list `agent-task/02+migration` as predecessor.
-- Directory names are runtime scheduling metadata. Preserve them verbatim; do not normalize, reinterpret, or choose execution order by agent judgment.
-- Every split plan must include `의존 관계 및 구현 순서` and list predecessor task directories that must reach `complete.log` before implementation begins.
+- Multi-plan task directory names must start with a stable two-digit task index. The index must increase across sibling task directories for sorting, but it is not a serial execution dependency.
+- Use `NN_{task_name}` for a task with no runtime dependencies, e.g. `01_core`, `04_docs`, `05_ui`.
+- Use `NN+PP[,QQ...]_{task_name}` for a task that depends on earlier task indices, e.g. `02+01_db`, `03+01,02_api`, `06+05_integration`.
+- Valid independent pattern: `^[0-9]{2}_[a-z0-9_]+$`.
+- Valid dependent pattern: `^[0-9]{2}\+[0-9]{2}(,[0-9]{2})*_[a-z0-9_]+$`.
+- `NN`, `PP`, and `QQ` are two-digit indices. Every predecessor index after `+` must be lower than `NN` and must refer to a sibling multi-plan task directory.
+- The first `_` after the index or dependency list starts `{task_name}`. `{task_name}` stays short snake_case and may contain additional underscores.
+- Runtime scheduling reads only the directory name: `_` means `depends_on=[]`; `+` means `depends_on` is the comma-separated index list between `+` and the first `_`.
+- Directory names are the source of truth for runtime dependencies. Do not hide extra dependencies only in the plan body, and do not create a bare `NN+{task_name}` without predecessor indices.
+- Example: split a common core plus two app integrations as `01_core`, `02+01_edge_integration`, `03+01_node_integration`. Both integrations depend only on `01_core` and may run in parallel after `01_core` has `complete.log`.
+- Example: split three sequential tasks as `01_schema`, `02+01_migration`, `03+02_api`.
+- Example: split independent docs/UI plus an integration as `01_core`, `02+01_db`, `03+02_api`, `04_docs`, `05_ui`, `06+05_integration`; `01_core`, `04_docs`, and `05_ui` can start together, and `06+05_integration` waits only for `05_ui`.
+- Preserve task directory names verbatim; do not normalize, reinterpret, or choose execution order by agent judgment.
 
 Routing rules:
 
@@ -154,7 +159,7 @@ Each plan item must include:
 
 Include `의존 관계 및 구현 순서` only when order matters.
 
-For split multi-plan work, `의존 관계 및 구현 순서` is mandatory in every generated plan. If a plan has a `NN+...` directory name, state which predecessor task directory or directories must produce `complete.log` before implementation starts.
+For split multi-plan work, the directory name is the runtime source of truth. If a plan has a `NN+PP[,QQ...]_...` directory name, `의존 관계 및 구현 순서` must echo the decoded predecessor task directories that must produce `complete.log` before implementation starts, and it must not add dependencies that are absent from the directory name.
 
 Quality rules:
 
@@ -312,7 +317,7 @@ Sections and their ownership:
 ## Final Checklist
 
 - `PLAN-{build_lane}-GNN.md` and `CODE_REVIEW-{review_lane}-GNN.md` both exist under `agent-task/{task_name}/`.
-- Split work, if any, uses one task directory per plan/review pair with names like `01_core`, `02+edge_integration`, `03+node_integration`; predecessor details live in `의존 관계 및 구현 순서`, not in the directory name.
+- Split work, if any, uses one task directory per plan/review pair with names like `01_core`, `02+01_edge_integration`, `03+01_node_integration`; dependency details live in the directory name as `NN+PP[,QQ...]_task_name`.
 - Both first lines match `<!-- task={task_name} plan={N} tag={TAG} -->`.
 - Previous active files, if any, were archived with correct numeric suffixes.
 - Every plan item has problem, solution, checklist, test decision, and intermediate verification.