@atollhq/skill-codex 0.4.5 → 0.4.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atollhq/skill-codex",
-  "version": "0.4.5",
+  "version": "0.4.6",
   "description": "Install the Atoll project management integration for Codex CLI",
   "bin": {
     "skill-codex": "bin/install.mjs"

package/skill/SKILL.md

@@ -172,6 +172,7 @@ CLI JSON conventions:
 
 - Use `--json` for machine-readable output.
 - List commands return `{ resource, items, total, limit, offset, nextOffset, truncated, hint }`.
+- Project-scoped `atoll issue list --json` includes `project_context`; `atoll issue get/view --json` includes `status_column` plus `project_context` when available.
 - Diagnostics and errors go to stderr.
 - Interactive CLI update notices also go to stderr and are suppressed for JSON/non-TTY/CI/completion flows.
 - `atoll agent-context` returns a versioned command/flag manifest, available profile context, and structured `cli.update_available` metadata.
@@ -311,6 +312,7 @@ The primary pattern for autonomous agents. Prefer `atoll heartbeat --json` when
 - **KPI pace**: `pace_needed` vs `pace_actual`, trend (`accelerating`/`decelerating`/`flat`), staleness
 - **Initiative progress**: total/completed/stalled/blocked issue counts, expected KPI impacts
 - **Assigned work** for this agent
+- **Project context**: relevant board columns, including optional descriptions that explain stage criteria for agents
 - **Signals** sorted by severity — the agent's prioritized to-do list
 
 Signal types: `kpi_off_pace`, `kpi_stale`, `issue_stale`, `issue_blocked`, `milestone_overdue`, `initiative_stalled`, `webhook_failing`. Severity: `info`, `warning`, `critical`.
@@ -470,6 +472,6 @@ atoll feedback resend fb_123
 - Request bodies accept camelCase; responses use snake_case
 - Descriptions and comments support Markdown
 - All timestamps are ISO 8601 UTC
-- Board statuses are customizable per project -- query `/board-columns` for available values
+- Board statuses are customizable per project -- query `/board-columns` for available values and optional column descriptions
 - API changes appear in real-time on the web board
 - List endpoints support `limit` (default 25, max 100), `offset` pagination, and optional `shape=envelope` / `response_shape=cli` for `{ resource, items, total, limit, offset, nextOffset, truncated, hint }`

package/skill/references/api-endpoints.md

@@ -303,13 +303,14 @@ Filters: `by_me` = your actions; `mine` = activity on issues assigned to you.
 
 ## Board Columns
 
-Custom statuses per project. Each column defines a valid status value.
+Custom statuses per project. Each column defines a valid status value and may include an optional `description` for stage criteria or agent guidance.
 
 | Method | Endpoint | Description |
 |--------|----------|-------------|
 | GET | `/api/orgs/{id}/projects/{projectId}/board-columns` | List columns (ordered by position) |
-| POST | `/api/orgs/{id}/projects/{projectId}/board-columns` | Create column (`{ key, label, color?, position? }`) |
-| PATCH | `/api/orgs/{id}/projects/{projectId}/board-columns/{columnId}` | Update column |
+| GET | `/api/orgs/{id}/projects/{projectId}/board-context` | Get board milestone and initiative focus context |
+| POST | `/api/orgs/{id}/projects/{projectId}/board-columns` | Create column (`{ key, label, description?, color?, position? }`) |
+| PATCH | `/api/orgs/{id}/projects/{projectId}/board-columns/{columnId}` | Update column (`{ label?, description?, color?, position? }`) |
 | DELETE | `/api/orgs/{id}/projects/{projectId}/board-columns/{columnId}` | Delete column (requires `reassignTo` in body) |
 | PUT | `/api/orgs/{id}/projects/{projectId}/board-columns/reorder` | Bulk reorder (`{ columns: [{id, position}] }`) |
 
@@ -319,7 +320,7 @@ Custom statuses per project. Each column defines a valid status value.
 |--------|----------|-------------|
 | GET | `/api/orgs/{id}/projects/{projectId}/board-views` | List views |
 | POST | `/api/orgs/{id}/projects/{projectId}/board-views` | Create view (`{ name, columnIds: [...] }`) |
-| PATCH | `/api/orgs/{id}/projects/{projectId}/board-views/{viewId}` | Update view |
+| PATCH | `/api/orgs/{id}/projects/{projectId}/board-views/{viewId}` | Update view (`{ name?, columnIds? }`; at least one required, `columnIds` must be an array) |
 | DELETE | `/api/orgs/{id}/projects/{projectId}/board-views/{viewId}` | Delete view (cannot delete default) |
 
 ## Custom Views

package/skill/references/api-fields.md

@@ -9,6 +9,7 @@
 - [Initiative Fields](#initiative-fields)
 - [Automation Rule Fields](#automation-rule-fields)
 - [Custom View Fields](#custom-view-fields)
+- [Board Context Response](#board-context-response)
 - [Webhook Fields](#webhook-fields)
 - [Setup Proposal Fields](#setup-proposal-fields)
 - [Heartbeat Response](#heartbeat-response)
@@ -222,6 +223,49 @@ Add/remove projects with `{ "project_id": "uuid" }`.
 
 `display_mode`: `board`, `list`. `filters` and `sort` are freeform JSON.
 
+## Board Context Response
+
+`GET /api/orgs/{id}/projects/{projectId}/board-context` returns the strategy data used by the board context rail:
+
+```json
+{
+  "strategyContext": {
+    "milestones": [{
+      "id": "milestone-uuid",
+      "name": "Public beta",
+      "status": "active",
+      "issueCount": 4,
+      "completedCount": 2,
+      "progress": 50,
+      "linkedInitiatives": [{
+        "id": "initiative-uuid",
+        "title": "Activation launch",
+        "status": "active",
+        "progress": 40,
+        "kpiImpactCount": 1,
+        "linkedMilestoneIds": ["milestone-uuid"]
+      }]
+    }],
+    "initiatives": [{
+      "id": "initiative-uuid",
+      "title": "Activation launch",
+      "status": "active",
+      "issueCount": 5,
+      "completedCount": 2,
+      "progress": 40,
+      "kpiImpactCount": 1,
+      "linkedMilestoneIds": ["milestone-uuid"]
+    }],
+    "issueInitiativeLinks": [{
+      "issueId": "issue-uuid",
+      "initiativeIds": ["initiative-uuid"]
+    }]
+  }
+}
+```
+
+`issueInitiativeLinks` includes direct `initiative_issues` links and links inherited from an issue's milestone.
+
 ## Webhook Fields
 
 ```json
@@ -286,6 +330,15 @@ Proposal JSON currently supports at most one item in each collection: `projects`
   }],
   "standalone_kpis": [...],
   "assigned_issues": [...],
+  "project_context": [{
+    "project_id": "...",
+    "project_name": "Product",
+    "board_columns": [{
+      "key": "approval_gate",
+      "label": "Approval Gate",
+      "description": "Use when implementation is complete but needs approval."
+    }]
+  }],
   "signals": [
     { "type": "kpi_off_pace", "severity": "warning", "message": "..." }
   ]
@@ -338,6 +391,7 @@ Each finding carries whichever entity ids apply: `goal_id`, `kpi_id`, `initiativ
 | Domain | Field | Values |
 |--------|-------|--------|
 | Task | `status` | `backlog`, `todo`, `in_progress`, `done`, `cancelled` (custom per project via board-columns) |
+| Board column | `description` | Optional stage criteria or agent guidance |
 | Task | `priority` | `0` (urgent), `1` (high), `2` (medium), `3` (low) |
 | Task | `recurrenceType` | `daily`, `weekly`, `monthly`, `yearly` |
 | Goal | `status` | `active`, `achieved`, `missed`, `paused`, `cancelled` |
@@ -367,7 +421,7 @@ REST list responses use resource-specific keys by default. Main list endpoints s
 
 - All timestamps are ISO 8601 in UTC
 - Description and comment fields support Markdown
-- Board columns (statuses) are customizable per project -- query `/board-columns` for available statuses
+- Board columns (statuses) are customizable per project -- query `/board-columns` for available statuses and optional descriptions
 - Default statuses for new projects: `backlog`, `todo`, `in_progress`, `done`
 - `cancelled` is always valid but not shown on the board
 - Agent actions appear in the activity feed with the agent's name