@tacuchi/agent-workflow-cli 18.0.0 → 19.0.0

package/skills/w/roles/README.md

@@ -12,12 +12,12 @@ All 6 roles, their built-in defaults, their tier, and which loops/exports compos
 
 | Role | Default built-in | Tier | Composed by |
 |---|---|---|---|
-| `ui-design` | [`ui-spec`](ui-spec/SKILL.md) | must | `spec-refine-loop` (when requirement involves UI) · `plan-new-loop` / `plan-refine-loop` (per-screen design SPECs) |
+| `ui-design` | [`ui-spec`](ui-spec/ROLE.md) | must | `spec-refine-loop` (when requirement involves UI) · `plan-new-loop` / `plan-refine-loop` (per-screen design SPECs) |
 | `sql` | `sql` | must | inline research · `plan-exec-loop` · `quick-loop` · `export-scripts` |
 | `git` | `git` | must | `plan-exec-loop` · `quick-loop` |
-| `research` | [`research`](research/SKILL.md) | should | all loops (on-demand investigation) |
-| `diagrams` | [`diagrams`](diagrams/SKILL.md) | should | `export-diagrams` |
-| `overview` | `workflow` | should | any loop (orientation about the workflow itself) |
+| `research` | [`research`](research/ROLE.md) | should | all loops (on-demand investigation) |
+| `diagrams` | [`diagrams`](diagrams/ROLE.md) | should | `export-diagrams` |
+| `overview` | `w` | should | any loop (orientation about the workflow itself) |
 
 **Tiers:**
 - `must` — core to almost every session; built-in always active unless explicitly `off`.
@@ -61,7 +61,7 @@ built-in default
 # git              = "git"
 # research         = "research"
 # diagrams         = "diagrams"
-# overview         = "workflow"
+# overview         = "w"
 
 # Override examples:
 ui-design        = "acme/figma-spec"    # third-party skill installed via skills.sh
@@ -116,7 +116,7 @@ sql               sql                     built-in
 git               git                     built-in
 research          research                built-in
 diagrams          mermaid-only            global      (~/.workflow/skills.toml)
-overview          workflow                built-in
+overview          w                       built-in
 ```
 
 ---
@@ -124,13 +124,13 @@ overview          workflow                built-in
 ## Adding a new role
 
 1. Define the role in this README (name, default built-in, tier, composed by).
-2. Author the built-in skill under `roles/<name>/SKILL.md` following the schema.
+2. Author the built-in skill under `roles/<name>/ROLE.md` following the schema.
 3. Register it in the CLI resolver so `aw skills` lists it.
 4. Document the binding key in the `skills.toml` reference above.
 
 ## Authoring a built-in skill
 
-Each `SKILL.md` follows this schema:
+Each `ROLE.md` follows this schema:
 
 | Section | Content |
 |---|---|
@@ -143,4 +143,4 @@ Each `SKILL.md` follows this schema:
 | `## Output` | what it produces and where (if any) |
 | `## Source` | recycled from (if applicable) |
 
-See [`research/SKILL.md`](research/SKILL.md) as a reference implementation.
+See [`research/ROLE.md`](research/ROLE.md) as a reference implementation.

package/skills/w/roles/git/{SKILL.md → ROLE.md}

@@ -46,7 +46,7 @@ And **always** forbidden, even when the user asks for a commit: `--no-verify` (r
 
 ### Read-only operations (always allowed, no asking)
 
-`status` · `log` · `diff` · `branch --show-current` · `rev-parse` · `show`. `git checkout` (branch switch) is **not** read-only: it requires *structured-choice* (canonical rule: `../../loops/CHASSIS.md` § *Structured-choice*; per-harness binding: `../../harness/SKILL.md`) even though it is not destructive (see branch verification).
+`status` · `log` · `diff` · `branch --show-current` · `rev-parse` · `show`. `git checkout` (branch switch) is **not** read-only: it requires *structured-choice* (canonical rule: `../../loops/CHASSIS.md` § *Structured-choice*; per-harness binding: `../../harness/HARNESS.md`) even though it is not destructive (see branch verification).
 
 ### Branch verification (before editing)
 

package/skills/w/roles/research/{SKILL.md → ROLE.md}

@@ -25,7 +25,7 @@ The key discriminator:
 | The question... | Action |
 |---|---|
 | can be answered by reading repo / data (objective system facts) | **investigate** |
-| depends on the user's preferences, priorities or decisions | **ask the human** via *structured-choice* (canonical rule: `../../loops/CHASSIS.md` § *Structured-choice*; per-harness binding: `../../harness/SKILL.md`) |
+| depends on the user's preferences, priorities or decisions | **ask the human** via *structured-choice* (canonical rule: `../../loops/CHASSIS.md` § *Structured-choice*; per-harness binding: `../../harness/HARNESS.md`) |
 | is partly in the repo and partly user intent | investigate first, then ask only about the uncertain part |
 
 ## Composed by

package/skills/w/roles/ui-spec/{SKILL.md → ROLE.md}

@@ -27,12 +27,12 @@ Given a UI requirement, author a **structured Markdown description** of the scre
 
 Two levels, same capability:
 
-- **`spec-refine-loop`** (see `../../loops/spec-refine-loop/SKILL.md`) — resolving the **UI unspecified** gap (when the requirement involves UI): authors the spec's `## UI spec` section (the UI's *what*, coarse-grain screens).
-- **`plan-new-loop` · `plan-refine-loop`** (see `../../loops/plan-new-loop/SKILL.md` § *Delta 4*) — resolving the **UI without design SPEC** gap (when the **plan includes UI**): authors per-screen **design SPECs** (`NNN-SPEC-<SLUG>.md`) as **PLAN session artifacts** (see `../../artifacts/artifacts-design/SPEC.md`); they derive from `## UI spec` when it exists.
+- **`spec-refine-loop`** (see `../../loops/spec-refine-loop/LOOP.md`) — resolving the **UI unspecified** gap (when the requirement involves UI): authors the spec's `## UI spec` section (the UI's *what*, coarse-grain screens).
+- **`plan-new-loop` · `plan-refine-loop`** (see `../../loops/plan-new-loop/LOOP.md` § *Delta 4*) — resolving the **UI without design SPEC** gap (when the **plan includes UI**): authors per-screen **design SPECs** (`NNN-SPEC-<SLUG>.md`) as **PLAN session artifacts** (see `../../artifacts/artifacts-design/SPEC.md`); they derive from `## UI spec` when it exists.
 
 In both, the composing loop contributes:
 
-- **Asking the human** (design system, theme, screen ambiguities) via *structured-choice* (canonical rule: `../../loops/CHASSIS.md` § *Structured-choice*; per-harness binding: `../../harness/SKILL.md`).
+- **Asking the human** (design system, theme, screen ambiguities) via *structured-choice* (canonical rule: `../../loops/CHASSIS.md` § *Structured-choice*; per-harness binding: `../../harness/HARNESS.md`).
 - **Gap-driven iteration** until convergence.
 - Offering **variants** and **curating** the result.