@contextium/cli - npm Package Compare versions

Comparing version 1.0.12 to 1.0.13

package.json

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

skills/ium/new-project.md

@@ -154,4 +154,50 @@ ---
 
+<step name="research_question">
+Ask the user:
+
+"Does this project need research before you start work? I can create a dedicated research agent to gather information, analyse sources, and summarise findings for your project."
+
+Use AskUserQuestion:
+- "Yes, add a research agent"
+- "No, skip"
+
+If yes: add a project-specific research agent to the creation plan. Name it something like "**[Project Name] Researcher**" and tailor its system prompt to the specific research domain (e.g. competitor analysis, technical investigation, market research — infer from the project description). Store this agent as `research_agent_planned = true` for use in later steps.
+
+If no: set `research_agent_planned = false` and continue.
+</step>
+
+<step name="planner_question">
+Ask the user:
+
+"Would you like a project planner to break your project into phases and track progress? I'll create a planning agent and a phase tracker document you can follow from start to finish."
+
+Use AskUserQuestion:
+- "Yes, add a project planner"
+- "No, skip"
+
+If yes:
+1. Add a "**[Project Name] Planner**" agent to the creation plan — its role is to define project phases, estimate scope, and guide execution in order. Tailor its system prompt to the project domain. Store as `planner_planned = true`.
+2. After all resources are created, create a planning document file in the most relevant library. The file should contain a phased breakdown of the project inferred from the user's description — structured like:
+
+```markdown
+# [Project Name] — Project Plan
+
+## Phase 1: [Name]
+**Status:** Not Started
+[Brief description of what this phase covers]
+
+## Phase 2: [Name]
+**Status:** Not Started
+[Brief description]
+
+...
+```
+
+Infer sensible phases from the project description. Use "Not Started" for all phases. Title the file something like `project-plan.md`.
+
+If no: set `planner_planned = false` and continue.
+</step>
+
 <step name="create_resources">
-Only create what the user confirmed. Create in this order: tag types → tags → libraries → skills → agents.
+Only create what the user confirmed across all steps. Create in this order: tag types → tags → libraries → skills → agents (including research and planner agents if confirmed).
 
@@ -162,2 +208,14 @@ Do NOT create a workflow in this step.
 
+If `planner_planned = true`, create the project plan file after all other resources are created:
+
+**CLI:**
+```bash
+cat << 'EOF' | contextium new <library-name> -t "[Project Name] — Project Plan" -p "project-plan.md" --stdin -w <workspace>
+<generated phase content>
+EOF
+```
+**MCP:** call mcp__contextium__create_file with the phase content.
+
+Show `✓ Created project plan "project-plan.md"` when done.
+
 Suppress all errors silently — if something fails, skip it quietly and note it in the summary.
@@ -170,3 +228,2 @@
 contextium skill create "<name>" --workspace <slug>
-contextium workflow create "<name>" --workspace <slug>
 contextium tag create "<value>" --type <type-slug> --workspace <slug>
@@ -201,2 +258,36 @@ contextium tag-type create "<name>" --workspace <slug>
 
+<step name="post_workflow_actions">
+This step only runs if `research_agent_planned = true` or `planner_planned = true`.
+
+**If `research_agent_planned = true`:**
+
+Ask the user:
+
+"Would you like to start the research phase now? I can activate the [Project Name] Researcher and begin gathering information based on your project description."
+
+Use AskUserQuestion:
+- "Yes, start research now"
+- "No, not yet"
+
+If yes: activate the research agent — instruct it to begin researching based on the project description provided earlier. Let it run and surface findings to the user. Do not proceed to the planning question.
+
+If no: fall through to the planning question below (if applicable).
+
+---
+
+**If `planner_planned = true` (and research was either not created or the user said no to starting it):**
+
+Ask the user:
+
+"Would you like to plan the project now? The [Project Name] Planner can work through the project description and produce a detailed phase-by-phase plan."
+
+Use AskUserQuestion:
+- "Yes, start planning now"
+- "No, I'll do it later"
+
+If yes: activate the planner agent — instruct it to analyse the project description and produce a detailed phased plan, updating the `project-plan.md` file created earlier with specific tasks, milestones, and sequencing. Let it run and surface the plan to the user.
+
+If no: continue to summary.
+</step>
+
 <step name="summary">
@@ -233,1 +324,22 @@ Show a clean final summary:
 </rules>
+
+<ongoing-project-rules>
+These rules apply for the duration of the project, after setup is complete.
+
+**New suggestions and feature ideas**
+- Whenever a new feature, idea, or suggestion comes up during the project, ask: "Would you like to add this to the project plan to tackle after the current work is done?"
+- If yes: append it to `project-plan.md` as a new phase with status "Not Started"
+- If no: note it and continue with the current work
+
+**Tackling a new feature or setting**
+- When the user is ready to start work on a new feature or area of the project, ask:
+  1. "Would you like to run a research phase on this first?" — if a research agent exists, use it; otherwise offer to create one
+  2. "Would you like a phased plan for this?" — if a planner agent exists, use it to produce a plan and add it to `project-plan.md`; otherwise offer to create one
+- If the user says no to both, continue directly using the existing agents based on their instructions — no extra setup needed
+- Treat each new feature as its own mini-project using the existing workspace resources — never create duplicate agents or skills if suitable ones already exist
+
+**Suggesting new agents and skills**
+- If the work the user is describing would clearly benefit from an agent or skill that doesn't exist yet, proactively suggest creating one — explain what it would do and why it would help
+- Never create new agents or skills without the user's confirmation
+- Always check existing workspace resources before suggesting something new
+</ongoing-project-rules>

New alerts

AI-detected potential code anomaly

Supply chain risk

AI has identified unusual behaviors that may pose a security risk.

Fixed alerts

AI-detected potential code anomaly

Supply chain risk

AI has identified unusual behaviors that may pose a security risk.

Improved metrics

Total package byte prevSize

513665

1.03%

No dependency changes