@contextium/cli 1.0.10 → 1.0.12

package/package.json

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

package/skills/ium/new-project.md

@@ -105,13 +105,11 @@ Based on the project description and the analysis, build a setup plan. Think thr
 
 **Libraries:** What distinct knowledge areas did the user mention? Each major topic or type of content that needs to be stored separately should be its own library. If an existing library already covers one of these, mark it for reuse.
 
-**Agents:** What kind of AI assistant roles would serve this project? Think about what tasks the user will perform — research, writing, analysis, Q&A, etc. If an existing agent fits, mark it for reuse.
+**Agents:** Always include a "Project Architect" agent as the first agent — its role is to define the project process, break the work into phases, and track overall progress. Write its system prompt to be specific to this project's domain and goals. Then think about what other AI assistant roles would serve this project based on what the user described. If an existing agent fits one of the additional roles, mark it for reuse.
 
 **Skills:** What reusable knowledge blocks would help agents working on this project? Think about domain-specific guidelines, reference material, or persistent context the agent needs. If an existing skill fits, mark it for reuse.
 
-**Tags:** What topic or category labels would make sense for organising content in this project? Look for existing tag types that match. If none exist, suggest new ones. Think in terms of tag categories (e.g. `topic`, `source`, `status`) and the specific tag values within them (e.g. `topic:space-travel`, `topic:rocket-engineering`).
-
-**Workflow:** Propose one workflow name that bundles everything together for quick loading.
+**Tags:** What topic or category labels would make sense for organising **files within context libraries** for this project? Tags apply to library files only — never suggest tags for agents or skills. Look for existing tag types that match. If none exist, suggest new ones. Think in terms of tag categories (e.g. `topic`, `source`, `status`) and the specific tag values within them (e.g. `topic:space-travel`, `topic:rocket-engineering`).
 
 Present the plan in this format (omit any section that has nothing in it):
 
@@ -119,29 +117,32 @@ Present the plan in this format (omit any section that has nothing in it):
 
 Here's what I'll set up for you:
 
-**New libraries to create**
-- "Library Name" — reason why this is needed
+**Libraries**
 
-**Existing libraries to reuse**
-- "Library Name" — why it's relevant
+| Action | Name | Purpose |
+|--------|------|---------|
+| Create | "Library Name" | reason why this is needed |
+| Reuse  | "Library Name" | why it's relevant |
 
-**New agents to create**
-- "Agent Name" — what it will do for this project
+**Agents**
 
-**Existing agents to reuse**
-- "Agent Name" — why it fits
+| Action | Name | Purpose |
+|--------|------|---------|
+| Create | "Agent Name" | what it will do for this project |
+| Reuse  | "Agent Name" | why it fits |
 
-**New skills to create**
-- "Skill Name" — what knowledge it will hold
+**Skills**
 
-**Existing skills to reuse**
-- "Skill Name" — why it fits
+| Action | Name | Purpose |
+|--------|------|---------|
+| Create | "Skill Name" | what knowledge it will hold |
+| Reuse  | "Skill Name" | why it fits |
 
-**Tags to create**
-- `category:value` — why this label is useful
+**Tags**
 
-**Workflow**
-- "Workflow Name" — bundles everything above for quick loading
+| Tag | Purpose |
+|-----|---------|
+| `category:value` | why this label is useful |
 
 Shall I go ahead and create all of this?
 
@@ -151,7 +152,9 @@ Wait for the user to confirm, adjust, or say skip on any item before proceeding.
 </step>
 
 <step name="create_resources">
-Only create what the user confirmed. Create in this order: tag types → tags → libraries → skills → agents → workflow.
+Only create what the user confirmed. Create in this order: tag types → tags → libraries → skills → agents.
+
+Do NOT create a workflow in this step.
 
 Show `✓ Created "Name"` for each item as it is created. Show `↗ Reusing "Name"` for each existing resource being included.
 
@@ -170,13 +173,26 @@ contextium tag-type create "<name>" --workspace <slug>
 **MCP:** use the corresponding create_* tools for each resource type.
 </step>
 
-<step name="load_workflow">
-After all resources are created, automatically load the workflow without asking the user. Run silently:
+<step name="workflow_prompt">
+After all other resources are created, ask the user:
+
+"Would you like me to create a workflow to bundle everything together for quick loading? If yes, what would you like to call it?"
+
+Use AskUserQuestion with two options:
+- "Yes, create a workflow" (and ask for the name as a follow-up if they say yes)
+- "No, skip workflow"
+
+If they say yes and provide a name, create the workflow:
+
+**CLI:** `contextium workflow create "<name>" --workspace <slug>`
+**MCP:** call mcp__contextium__create_workflow with the name and workspace.
+
+Then automatically load it:
 
-**CLI:** `contextium workflow load "<workflow-name>" --workspace <slug> 2>/dev/null`
+**CLI:** `contextium workflow load "<name>" --workspace <slug> 2>/dev/null`
 **MCP:** call mcp__contextium__load_workflow with the workflow name and workspace.
 
-Do not tell the user to load it themselves — just load it as part of setup.
+If they say no, skip workflow creation and loading entirely.
 </step>
 
 <step name="summary">
@@ -190,7 +206,7 @@ Libraries:   <list — new + reused>
 Agents:      <list — new + reused, or none>
 Skills:      <list — new + reused, or none>
 Tags:        <list, or none>
-Workflow:    <name> — loaded and ready
+Workflow:    <name> — loaded and ready   (or "none" if skipped)
 ```
 
 If anything failed to create, add a single line at the end:
@@ -205,6 +221,7 @@ If anything failed to create, add a single line at the end:
 - Run all checks and fetches silently — only surface progress labels and the final plan
 - Only ask questions when genuinely needed — the description step and the confirmation step
 - Do not ask the user what to create — figure it out from the description, then ask them to confirm
+- Always create a "Project Architect" agent first, regardless of what the user described — tailor its system prompt to the specific project domain and goals
 - If a resource already exists and is relevant, always prefer reuse over creating a duplicate
 - The plan report must explain the reasoning for each item — not just list names
 - Never create anything before the user confirms the plan