@contextium/cli - npm Package Compare versions

Comparing version

1.0.60

1.0.61

+1

-1

package.json

		{
		"name": "@contextium/cli",
		"version": "1.0.60",
		"version": "1.0.61",
		"description": "Command-line tool for managing Contextium documentation, agents, skills, and workflows — pipe context to AI coding assistants",
		@@ -5,0 +5,0 @@ "keywords": [

+46

-0

skills/ium/workflow.md

		@@ -115,2 +115,48 @@ ---

		<auto-planning>
		## Auto-planning — triggered on first user goal after loading

		Once the workflow is loaded and the user states what they want to do, apply this logic before starting any work:

		If `phaseCount === 0` (no phases set up yet):

		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>" }`
		- 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>" }`
		- Show the user the phase breakdown:
		```
		Planned X phases:
		1. <title>
		2. <title>
		...
		Starting phase 1 now.
		```
		- Then immediately start the first phase as the Builder

		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.

		Completing phases:
		- When a phase is done, call `mark_phase_complete` (MCP) or `update_workflow` with `completedCount` incremented
		- 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")
		- Keep phase titles short and action-oriented (e.g. "Add payments table migration", "Build checkout API endpoint")
		</auto-planning>

		<session-rules>
		@@ -117,0 +163,0 @@ Once the session context block has been output, these rules apply for the rest of the conversation:

@contextium/cli - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics