@deimoscloud/coreai 0.1.17 → 0.1.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@deimoscloud/coreai",
3
- "version": "0.1.17",
3
+ "version": "0.1.19",
4
4
  "description": "A configurable, team-ready AI agent orchestration platform",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -11,6 +11,7 @@
11
11
  "files": [
12
12
  "dist",
13
13
  "agents",
14
+ "skills",
14
15
  "schemas"
15
16
  ],
16
17
  "repository": {
@@ -20,11 +20,9 @@
20
20
  "type": "string",
21
21
  "description": "Project name"
22
22
  },
23
- "type": {
23
+ "description": {
24
24
  "type": "string",
25
- "description": "Project type",
26
- "enum": ["software", "infrastructure", "data", "mobile"],
27
- "default": "software"
25
+ "description": "Brief description of the project"
28
26
  }
29
27
  },
30
28
  "additionalProperties": false
@@ -39,7 +37,7 @@
39
37
  "items": {
40
38
  "type": "string"
41
39
  },
42
- "default": ["backend-engineer", "frontend-engineer", "devops-engineer", "engineering-manager"]
40
+ "default": ["engineering-manager"]
43
41
  }
44
42
  },
45
43
  "additionalProperties": false
@@ -70,28 +68,6 @@
70
68
  "$ref": "#/$defs/qualityGate"
71
69
  }
72
70
  },
73
- "tech_stack": {
74
- "type": "object",
75
- "description": "Technology stack information",
76
- "properties": {
77
- "primary_language": {
78
- "type": "string",
79
- "description": "Primary programming language"
80
- },
81
- "frameworks": {
82
- "type": "array",
83
- "description": "Frameworks and libraries used",
84
- "items": {
85
- "type": "string"
86
- }
87
- },
88
- "cloud": {
89
- "type": "string",
90
- "description": "Cloud provider (if applicable)"
91
- }
92
- },
93
- "additionalProperties": true
94
- },
95
71
  "mcp": {
96
72
  "type": "object",
97
73
  "description": "MCP (Model Context Protocol) settings",
@@ -0,0 +1,37 @@
1
+ ---
2
+ name: check-inbox
3
+ description: Check your inbox for new tasks and process them
4
+ argument-hint: [optional: and work on ticket]
5
+ allowed-tools: Read, Write, Bash, Glob, Grep
6
+ ---
7
+
8
+ # Check Inbox
9
+
10
+ You have been invoked to check your inbox and process any pending tasks.
11
+
12
+ ## Instructions
13
+
14
+ 1. **Read your inbox directory:** `/KnowledgeLibrary/[your-agent-name]/inbox/`
15
+ - Ignore the `processed/` subdirectory
16
+ - Look for `.md` files from other agents (especially engineering-manager)
17
+
18
+ 2. **For each unprocessed message:**
19
+ - Read the task details
20
+ - If it's a task assignment, begin work following the workflow in `WORKFLOWS.md`
21
+ - If it's a review request, perform the review
22
+
23
+ 3. **When you complete work:**
24
+ - Move processed inbox messages to `inbox/processed/` with prefix `PROCESSED_YYYYMMDD_HHMM_`
25
+ - Write completion summary to the sender's inbox (usually engineering-manager)
26
+ - Update any referenced tickets or PRs using your available tools
27
+ - End with "Please invoke @[next-agent]" instruction for the user
28
+
29
+ 4. **If inbox is empty:**
30
+ - Report "No pending tasks in inbox"
31
+ - Optionally check for assigned work using your available tools
32
+
33
+ ## Additional Context
34
+
35
+ $ARGUMENTS
36
+
37
+ Now check your inbox and proceed.
@@ -0,0 +1,61 @@
1
+ ---
2
+ name: delegate
3
+ description: Delegate a task to an agent using inbox-based delegation (NOT Task tool)
4
+ argument-hint: <ticket-or-task> to <agent-name>
5
+ allowed-tools: Read, Write, Bash, Glob, Grep
6
+ ---
7
+
8
+ # Delegation Request
9
+
10
+ You are the Engineering Manager. Delegate this task: **$ARGUMENTS**
11
+
12
+ ## CRITICAL RULES - READ FIRST
13
+
14
+ 1. **DO NOT USE THE TASK TOOL** - You must NOT invoke agents directly
15
+ 2. **USE INBOX FILES ONLY** - Write task details to the agent's inbox directory
16
+ 3. **TELL USER TO INVOKE** - End your response telling the user which agent(s) to invoke
17
+
18
+ ## Why No Task Tool?
19
+
20
+ When YOU invoke an agent via the Task tool, they run in a subprocess without MCP access.
21
+ When the USER invokes them via `@agent-name`, they get full MCP access to project tools.
22
+ Always delegate via inbox so the user can invoke with full capabilities.
23
+
24
+ ## Steps
25
+
26
+ 1. **Parse the request** - identify the target agent and task details
27
+ 2. **Look up context** - if a ticket, PR, or issue is referenced, use your available tools to gather details
28
+ 3. **Write task file** to `/KnowledgeLibrary/[agent-name]/inbox/YYYYMMDD_HHMM-engineering-manager-[topic].md`
29
+ 4. **Save copy** to your outbox at `/KnowledgeLibrary/engineering-manager/outbox/`
30
+ 5. **End with invocation instruction** for the user
31
+
32
+ ## Inbox Message Format
33
+
34
+ ```markdown
35
+ ## Task Assignment
36
+ **From:** engineering-manager
37
+ **Date:** [today's date]
38
+ **Priority:** [high/medium/low]
39
+
40
+ ### Task
41
+ [Clear description of what needs to be done]
42
+
43
+ ### Context
44
+ [Any relevant ticket numbers, PR links, or background information]
45
+
46
+ ### Acceptance Criteria
47
+ - [What "done" looks like]
48
+
49
+ ### Workflow
50
+ Follow your standard workflow in WORKFLOWS.md
51
+ ```
52
+
53
+ ## End Your Response With
54
+
55
+ ```
56
+ ---
57
+ **Next Action Required:**
58
+ Please invoke: `@[agent-name] check your inbox`
59
+ ```
60
+
61
+ Now proceed with the delegation.
@@ -0,0 +1,57 @@
1
+ ---
2
+ name: review
3
+ description: Request PR review from agents using inbox-based delegation
4
+ argument-hint: PR #<number> by <agent-name(s)>
5
+ requires: [git]
6
+ allowed-tools: Read, Write, Bash, Glob, Grep
7
+ ---
8
+
9
+ # PR Review Request
10
+
11
+ You are the Engineering Manager. Assign this review: **$ARGUMENTS**
12
+
13
+ ## CRITICAL RULES - READ FIRST
14
+
15
+ 1. **DO NOT USE THE TASK TOOL** - You must NOT invoke agents directly
16
+ 2. **USE INBOX FILES ONLY** - Write review requests to agent inbox directories
17
+ 3. **TELL USER TO INVOKE** - End your response telling the user which agent(s) to invoke
18
+
19
+ ## Steps
20
+
21
+ 1. **Get PR details** using your available tools (e.g. `gh pr view`, `glab mr view`)
22
+ 2. **Identify reviewer agent(s)** from the arguments or based on the PR's domain
23
+ 3. **For EACH reviewer agent**, write a review request to their inbox:
24
+ `/KnowledgeLibrary/[agent-name]/inbox/YYYYMMDD_HHMM-engineering-manager-review-PR-XX.md`
25
+ 4. **Save copies** to your outbox
26
+ 5. **End with invocation instructions** for the user
27
+
28
+ ## Review Request Template
29
+
30
+ ```markdown
31
+ ## PR Review Request
32
+ **From:** engineering-manager
33
+ **Date:** [date]
34
+ **PR:** #[number] - [title]
35
+ **PR URL:** [url from PR details]
36
+
37
+ ### Review Focus
38
+ - [Architecture alignment / Security / Test coverage - based on agent role]
39
+
40
+ ### Workflow Requirements
41
+ Follow Code Review workflow in WORKFLOWS.md:
42
+ 1. Review the PR thoroughly
43
+ 2. Post your review as a PR comment using your available tools
44
+ 3. State APPROVED or CHANGES_REQUESTED with your decision
45
+ 4. Send summary to my inbox
46
+ ```
47
+
48
+ ## End Your Response With
49
+
50
+ ```
51
+ ---
52
+ **Next Action Required:**
53
+ Please invoke the reviewers:
54
+ - `@[agent-name] check your inbox and review PR #XX`
55
+ ```
56
+
57
+ Now proceed with the review delegation.