@dotcontext/cli 0.8.0

package/package.json

@@ -0,0 +1,85 @@
+{
+  "name": "@dotcontext/cli",
+  "version": "0.8.0",
+  "description": "MCP-first toolkit for AI context workflow, sync, imports, and orchestration",
+  "main": "dist/index.js",
+  "bin": {
+    "dotcontext": "dist/index.js"
+  },
+  "files": [
+    "dist/**/*",
+    "README.md",
+    "LICENSE",
+    "prompts/**/*"
+  ],
+  "engines": {
+    "node": ">=20.0.0"
+  },
+  "scripts": {
+    "build": "node -e \"require('fs').rmSync('dist', { recursive: true, force: true })\" && tsc",
+    "dev": "tsx src/index.ts",
+    "start": "node dist/index.js",
+    "test": "jest",
+    "prepublishOnly": "npm run build",
+    "version": "npm run build",
+    "release": "npm version patch && npm publish --access public",
+    "release:minor": "npm version minor && npm publish --access public",
+    "release:major": "npm version major && npm publish --access public"
+  },
+  "publishConfig": {
+    "access": "public",
+    "registry": "https://registry.npmjs.org/"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/vinilana/dotcontext.git"
+  },
+  "homepage": "https://github.com/vinilana/dotcontext#readme",
+  "bugs": {
+    "url": "https://github.com/vinilana/dotcontext/issues"
+  },
+  "keywords": [
+    "cli",
+    "documentation",
+    "agents",
+    "scaffold"
+  ],
+  "author": "",
+  "license": "MIT",
+  "dependencies": {
+    "@ai-sdk/anthropic": "^3.0.9",
+    "@ai-sdk/google": "^3.0.6",
+    "@ai-sdk/openai": "^3.0.7",
+    "@modelcontextprotocol/sdk": "^1.25.2",
+    "ai": "^6.0.19",
+    "axios": "^1.12.2",
+    "boxen": "^5.1.2",
+    "chalk": "^4.1.2",
+    "cli-progress": "^3.12.0",
+    "commander": "^14.0.1",
+    "figures": "^3.2.0",
+    "fs-extra": "^11.3.2",
+    "glob": "^10.4.5",
+    "ignore": "^7.0.5",
+    "inquirer": "^12.6.3",
+    "ora": "^5.4.1",
+    "semver": "^7.6.3",
+    "zod": "^4.3.5"
+  },
+  "devDependencies": {
+    "@types/cli-progress": "^3.11.0",
+    "@types/fs-extra": "^11.0.4",
+    "@types/inquirer": "^9.0.8",
+    "@types/jest": "^30.0.0",
+    "@types/node": "^24.5.2",
+    "@types/semver": "^7.5.8",
+    "jest": "^30.1.3",
+    "ts-jest": "^29.4.4",
+    "tsx": "^4.20.6",
+    "typescript": "^5.9.2"
+  },
+  "optionalDependencies": {
+    "tree-sitter": "^0.21.0",
+    "tree-sitter-typescript": "^0.23.2"
+  }
+}

package/prompts/update_plan_prompt.md

@@ -0,0 +1,41 @@
+# Prompt: Update Collaboration Plans
+
+## Purpose
+You are an AI assistant responsible for refining collaboration plans that live in the `.context/plans/` directory. Each plan orchestrates work across documentation guides (`docs/`) and agent playbooks (`agents/`). Your goal is to replace placeholders with actionable guidance that keeps the plan aligned with the referenced docs, agents, and repository context.
+
+## Preparation Checklist
+1. Review the plan’s YAML front matter to understand the stated `ai_update_goal`, `required_inputs`, and `success_criteria`.
+2. Inspect the provided documentation excerpts (from `docs/`) and agent playbooks to ensure the plan reflects their current guidance.
+3. Confirm that the “Agent Lineup” and “Documentation Touchpoints” tables link to real files and reference the correct `agent-update` markers.
+4. Note any TODOs, `agent-fill` placeholders, or missing evidence sections that must be resolved.
+
+## Update Procedure
+1. **Task Snapshot**
+   - Summarize the primary goal and success signal in concrete terms.
+   - List authoritative references (docs, issues, specs) that contributors should consult.
+
+2. **Agent Alignment**
+   - For each agent in the lineup, describe why they are involved and call out the first responsibility they should focus on.
+   - Ensure playbook links and responsibility summaries match the referenced agent files.
+
+3. **Documentation Touchpoints**
+   - Map each plan stage to the docs excerpts provided, highlighting which sections need to be updated during execution.
+   - Keep the table sorted and ensure the listed `agent-update` markers exist.
+
+4. **Working Stages**
+   - Break the work into clear stages with owners, deliverables, and evidence checkpoints.
+   - Reference documentation and agent resources that the team should consult while executing each stage.
+
+5. **Evidence & Follow-up**
+   - Specify the artefacts that must be captured (PR links, test runs, change logs) before the plan is considered complete.
+   - Record any follow-up actions or decisions that require human confirmation.
+
+## Acceptance Criteria
+- Every TODO or placeholder inside the plan’s `agent-update` block is resolved or accompanied by a clear escalation note.
+- Tables reference existing files and stay in sync with the docs/agent indices.
+- Stages provide actionable guidance, owners, and success signals.
+- The plan remains fully self-contained and ready for contributors to execute.
+
+## Deliverables
+- Updated plan Markdown returned verbatim.
+- No additional commentary outside the Markdown output.

package/prompts/update_scaffold_prompt.md

@@ -0,0 +1,27 @@
+# Prompt: Update Repository Documentation and Agent Playbooks
+
+## Purpose
+You are an AI assistant responsible for refreshing the documentation (`docs/`) and agent playbooks (`agents/`). Your goal is to bring every guide up to date with the latest repository state and maintain cross-references between docs and agent instructions.
+
+## Context Gathering
+1. Review the repository structure and recent changes.
+2. Inspect `package.json`, CI configuration, and any release or roadmap notes.
+3. Check `docs/README.md` for the current document map.
+
+## Update Procedure
+1. **Update Documentation**
+   - Replace TODO placeholders with accurate, current information.
+   - Verify that links between docs remain valid.
+   - If you add new guides or sections, update `docs/README.md`.
+
+2. **Agent Playbook Alignment**
+   - For each change in `docs/`, adjust the related `agents/*.md` playbooks.
+   - Update responsibilities, best practices, and documentation touchpoints.
+
+## Acceptance Criteria
+- No unresolved TODO placeholders remain unless they require explicit human input.
+- Agent playbooks list accurate responsibilities and best practices.
+- Changes are self-contained, well-formatted Markdown.
+
+## Deliverables
+- Updated Markdown files.