@contextium/cli 1.6.5 → 1.6.7

package/skills/ium/workflow.md

@@ -92,13 +92,13 @@ Workflow loaded. What would you like to do?
 
 The tasks/phases in the session context come from the `load_workflow` response — do NOT call `list_tasks` to fetch them again.
 
-**For project workflows** (`projectConfig.contextLibraryId` is set): tasks are stored as phase files in the Project Library. Surface only the **next pending phase** (first `not_started` task from the loaded data) — do not list all phases.
+**For project workflows** (`projectConfig.contextLibraryId` is set): phases are database records (the `workflow_phases` table), managed with the `add_phase` / `list_phases` / `update_phase_status` MCP tools — NOT files in a library. Surface only the **next pending phase** (first `not_started` phase from the loaded data) — do not list all phases.
 
 5. After outputting the session context block, apply task awareness:
 
 - If there is an **in_progress** task: note it as the active phase and ask if the user wants to resume it.
 - If there is a **not_started** next phase: present it as the suggested next action. Do not auto-start — let the user confirm.
-- If you create new action items during the session: call `add_task` to record them. For project workflows these are stored as phase files in the Project Library — no separate "plan" step needed.
+- If you create new action items during the session: call `add_phase(workflowId, title, ...)` to record them as phases (DB records) — no separate "plan" step and no files needed.
 - When a task/phase is complete: call `update_task_status(taskId, 'done')`.
 - Do not work on multiple tasks simultaneously.
 
@@ -121,16 +121,14 @@ Once the workflow is loaded and the user states what they want to do, apply this
 Assess the scope of the request silently, then act accordingly:
 
 **Simple / single task** (one clear, bounded piece of work — e.g. "fix this bug", "write a readme", "add a button"):
-- Create 1 phase file in the Project Library
-- Call `update_workflow` with `projectConfig: { phaseCount: 1, completedCount: 0, contextLibraryId: "<projectLibraryId>" }`
+- Call `add_phase(workflowId, title)` once to create the phase (a DB record — `add_phase` lazily creates the project plan if none exists)
 - Say: "Added as 1 phase. Starting now." — then proceed immediately as the Builder
 
 **Complex / multi-part ask** (a feature, a new system, multiple steps — e.g. "build an onboarding flow", "add payments", "create the admin panel"):
 - Break the work down into logical phases (DB migrations first, then API, then MCP/CLI, then UI — in dependency order)
 - Aim for 3–10 phases. Each phase = one coherent unit of work that can be built and reviewed independently
-- Create one phase file per phase in the Project Library using `contextium new "<project-library>" -w <workspace> --stdin`
-  Each file must include: phase ID (e.g. `phase-001`), title, layer, status (`pending`), and a brief implementation spec
-- Call `update_workflow` with `projectConfig: { phaseCount: <N>, completedCount: 0, contextLibraryId: "<projectLibraryId>" }`
+- Create one phase per phase by calling `add_phase(workflowId, title, description)` — once per phase. Each phase is a DB record (the `workflow_phases` table); do NOT create files. Put the title and a brief implementation spec (layer, what to build) in the `description`.
+- `phaseCount`/`completedCount` are maintained by the phase tools — you do NOT need to call `update_workflow` to set them
 - Show the user the phase breakdown:
   ```
   Planned X phases:
@@ -143,17 +141,17 @@ Assess the scope of the request silently, then act accordingly:
 
 **If `phaseCount > 0` (phases already exist):**
 - Do NOT re-plan. Go straight to the next pending phase.
-- If the user's request is new work unrelated to existing phases: create a new phase file, increment `phaseCount` via `update_workflow`, and begin it.
+- If the user's request is new work unrelated to existing phases: call `add_phase(workflowId, title)` to add it and begin it.
 
 **Completing phases:**
-- When a phase is done, call `mark_phase_complete` (MCP) or `update_workflow` with `completedCount` incremented
+- When a phase is done, call `update_phase_status(phaseId, 'done')` (or `mark_phase_complete`) — the completed count updates automatically
 - Announce progress: "Phase 2 of 5 complete." then ask if the user wants to continue to the next phase
 - Do not auto-start the next phase without confirmation
 
 **Rules:**
 - Never ask the user "should I plan this?" — just assess and act
-- Never show raw file creation output — only the phase list summary
-- Phase files go in the Project Library (the library whose name contains "Project Library")
+- Phases are DB records — never create files for them; always use `add_phase` / `list_phases` / `update_phase_status`
+- Never show raw tool output — only the phase list summary
 - Keep phase titles short and action-oriented (e.g. "Add payments table migration", "Build checkout API endpoint")
 </auto-planning>