@contextium/cli 1.0.11 → 1.0.12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contextium/cli",
-  "version": "1.0.11",
+  "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,7 +105,7 @@ 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.
 
@@ -221,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