Sign In

@contextium/cli

Package Overview
Dependencies
Maintainers
2
Versions
108
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@contextium/cli - npm Package Compare versions

Comparing version
1.0.61
to
1.0.64
+1
-1
package.json
{
"name": "@contextium/cli",
"version": "1.0.61",
"version": "1.0.64",
"description": "Command-line tool for managing Contextium documentation, agents, skills, and workflows — pipe context to AI coding assistants",

@@ -5,0 +5,0 @@ "keywords": [

@@ -107,3 +107,3 @@ ---

- If there are only **not_started** tasks: note the first one as the suggested next action. Do not auto-start — let the user direct the session.
- If you create new action items during the session: call `add_task` to record them for the team.
- If you create new action items during the session: call `add_task` to record them for the team. For project workflows these are stored as phase files in the Project Library — no separate "plan" step needed.
- When a task is complete: call `update_task_status(taskId, 'done')`.

@@ -121,4 +121,9 @@ - Do not work on multiple tasks simultaneously.

**If `phaseCount === 0` (no phases set up yet):**
**First check: does this workflow have a Project Library?**
- Look for `projectConfig.contextLibraryId` in the loaded workflow data.
- If it is missing or null: this is a legacy knowledge workflow with no project tracking. **Skip all auto-planning entirely** — just help the user with their request directly as you normally would.
- Only proceed with auto-planning if `contextLibraryId` is set.
**If `phaseCount === 0` (no phases set up yet) AND `contextLibraryId` exists:**
Assess the scope of the request silently, then act accordingly:

@@ -125,0 +130,0 @@