@deimoscloud/coreai 0.1.9 → 0.1.10

package/commands/optional/worktree-cleanup.md

@@ -1,167 +0,0 @@
----
-description: Use when a PR has been merged, a ticket is complete, or development work is finished. Cleans up the git worktree created for parallel agent work. Typically used by the Engineering Manager after merge.
-argument-hint: TICKET-XX or worktree path
----
-
-# Worktree Cleanup
-
-You are cleaning up the worktree for: **$ARGUMENTS**
-
-## When to Use
-
-- PR has been merged to main
-- Ticket is marked as Done
-- Development work is complete and no longer needed
-
-## Cleanup Steps
-
-### 1. Identify Worktree to Remove
-
-List all active worktrees:
-```bash
-cd {{PROJECT_ROOT}}
-git worktree list
-```
-
-**Expected output:**
-```
-{{PROJECT_ROOT}}                                              abc1234 [main]
-{{PROJECT_ROOT}}/../{{PROJECT_NAME}}-agent1-{{JIRA_PROJECT}}-123  def5678 [feature/{{JIRA_PROJECT}}-123-description]
-{{PROJECT_ROOT}}/../{{PROJECT_NAME}}-agent2-{{JIRA_PROJECT}}-456  ghi9012 [feature/{{JIRA_PROJECT}}-456-description]
-```
-
-### 2. Verify PR is Merged
-
-Before removing, confirm the PR is merged:
-```bash
-gh pr list --state merged --search "{{JIRA_PROJECT}}-XX"
-```
-
-Or check if the branch exists on remote:
-```bash
-git ls-remote --heads origin feature/{{JIRA_PROJECT}}-XX-description
-# Empty output = branch deleted (PR merged)
-```
-
-### 3. Remove Worktree
-
-```bash
-# From the main repository
-cd {{PROJECT_ROOT}}
-
-# Remove the worktree
-git worktree remove ../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX
-```
-
-### 4. Delete Local Branch (if exists)
-
-```bash
-git branch -d feature/{{JIRA_PROJECT}}-XX-description
-```
-
-If branch wasn't merged (force delete with caution):
-```bash
-git branch -D feature/{{JIRA_PROJECT}}-XX-description
-```
-
-### 5. Prune Stale Worktrees
-
-Clean up any stale worktree references:
-```bash
-git worktree prune
-```
-
-### 6. Verify Cleanup
-
-```bash
-git worktree list
-```
-
-Confirm the worktree no longer appears.
-
-## Batch Cleanup
-
-To clean up multiple worktrees at once:
-
-```bash
-# List all worktrees
-git worktree list
-
-# Remove each one
-git worktree remove ../{{PROJECT_NAME}}-agent1-{{JIRA_PROJECT}}-XXX
-git worktree remove ../{{PROJECT_NAME}}-agent2-{{JIRA_PROJECT}}-YYY
-
-# Prune all stale references
-git worktree prune
-```
-
-## Error Handling
-
-**If worktree has uncommitted changes:**
-```
-error: '<path>' contains modified or untracked files, use --force to delete it
-```
-
-Options:
-1. **If changes are needed:** Commit and push first, then remove
-2. **If changes can be discarded:** `git worktree remove --force ../path`
-
-**If worktree directory doesn't exist but git tracks it:**
-```bash
-git worktree prune
-```
-
-**If branch is not fully merged:**
-```bash
-# Check if branch was merged
-git branch --merged main | grep feature/{{JIRA_PROJECT}}-XX
-
-# If not merged but PR is closed/merged on GitHub, force delete
-git branch -D feature/{{JIRA_PROJECT}}-XX-description
-```
-
-## Update Jira (Optional)
-
-If the ticket isn't already Done, transition it:
-- Use `/jira-transition` to move to "Done"
-- Or use Atlassian MCP directly
-
-## Completion
-
-After cleanup, report:
-```
-Worktree Cleanup Complete
-
-Removed:
-- Worktree: {{PROJECT_ROOT}}/../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX
-- Branch: feature/{{JIRA_PROJECT}}-XX-description
-
-Active Worktrees:
-<output of git worktree list>
-
-Ticket {{JIRA_PROJECT}}-XX is ready to be marked as Done (if not already).
-```
-
-## Bulk Cleanup After Sprint
-
-To clean up all worktrees from a completed sprint:
-
-```bash
-# List all worktrees
-git worktree list
-
-# Remove all agent worktrees (keep main)
-for dir in ../{{PROJECT_NAME}}-*-{{JIRA_PROJECT}}-*; do
-  if [ -d "$dir" ]; then
-    git worktree remove "$dir" --force
-  fi
-done
-
-# Prune
-git worktree prune
-
-# Clean up merged branches
-git branch --merged main | grep -E "feature/{{JIRA_PROJECT}}-" | xargs -r git branch -d
-```
-
-Now proceed with the worktree cleanup.

package/commands/optional/worktree-setup.md

@@ -1,110 +0,0 @@
----
-description: Use when starting work on a ticket, implementing a feature, fixing a bug, or beginning any development task. Sets up an isolated git worktree for parallel agent work, preventing conflicts when multiple agents work simultaneously.
-argument-hint: TICKET-XX [short-description]
----
-
-# Worktree Setup for Parallel Development
-
-You are setting up an isolated git worktree to work on: **$ARGUMENTS**
-
-## Why Worktrees?
-
-Multiple agents can work on different tickets simultaneously without conflicts. Each agent gets its own working directory with its own branch, completely isolated from other agents.
-
-## Setup Steps
-
-### 1. Parse Arguments
-
-Extract from `$ARGUMENTS`:
-- **Ticket ID:** {{JIRA_PROJECT}}-XX (required)
-- **Description:** Short description for branch name (optional, derive from ticket if not provided)
-
-### 2. Determine Your Agent Name
-
-Identify which agent you are (e.g., `backend-engineer`, `frontend-engineer`). This is used in the worktree path.
-
-### 3. Fetch Latest Main
-
-```bash
-cd {{PROJECT_ROOT}}
-git fetch origin main
-```
-
-### 4. Create Worktree
-
-```bash
-# Pattern: ../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX
-git worktree add ../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX -b feature/{{JIRA_PROJECT}}-XX-[description] origin/main
-```
-
-**Example:**
-```bash
-git worktree add ../{{PROJECT_NAME}}-backend-engineer-{{JIRA_PROJECT}}-123 -b feature/{{JIRA_PROJECT}}-123-feature-name origin/main
-```
-
-### 5. Verify Worktree
-
-```bash
-git worktree list
-```
-
-Confirm your new worktree appears in the list.
-
-### 6. Set Working Directory
-
-**CRITICAL:** All subsequent work must happen in the worktree directory:
-
-```
-{{PROJECT_ROOT}}/../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX/
-```
-
-Announce to the user:
-```
-Worktree created. Working directory is now:
-{{PROJECT_ROOT}}/../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX
-
-All code changes will be made in this isolated directory.
-```
-
-### 7. Update Jira (if not already done)
-
-If the ticket is not already "In Progress":
-- Transition ticket to "In Progress"
-- Add comment: "Starting work. Branch: `feature/{{JIRA_PROJECT}}-XX-[description]`"
-
-## Important Notes
-
-- **Never work in the main repository** when a worktree is active for your ticket
-- **One worktree per ticket** - if you already have a worktree for this ticket, use it instead of creating a new one
-- **Worktree cleanup** is handled by the Engineering Manager after PR merge via `/worktree-cleanup`
-
-## Error Handling
-
-**If worktree already exists:**
-```bash
-# Check existing worktrees
-git worktree list
-
-# If your worktree exists, just use it
-cd ../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX
-```
-
-**If branch already exists:**
-```bash
-# Use existing branch in new worktree
-git worktree add ../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX feature/{{JIRA_PROJECT}}-XX-[description]
-```
-
-## Completion
-
-After setup, announce:
-```
-Worktree ready for {{JIRA_PROJECT}}-XX
-
-Directory: {{PROJECT_ROOT}}/../{{PROJECT_NAME}}-[agent-name]-{{JIRA_PROJECT}}-XX
-Branch: feature/{{JIRA_PROJECT}}-XX-[description]
-
-Ready to begin implementation.
-```
-
-Now proceed with the worktree setup.

package/eslint.config.js

@@ -1,29 +0,0 @@
-import eslint from '@eslint/js';
-import tseslint from 'typescript-eslint';
-import prettier from 'eslint-plugin-prettier/recommended';
-
-export default tseslint.config(
-  eslint.configs.recommended,
-  ...tseslint.configs.strict,
-  ...tseslint.configs.stylistic,
-  prettier,
-  {
-    languageOptions: {
-      parserOptions: {
-        project: true,
-        tsconfigRootDir: import.meta.dirname,
-      },
-    },
-    rules: {
-      '@typescript-eslint/no-unused-vars': [
-        'error',
-        { argsIgnorePattern: '^_', varsIgnorePattern: '^_' },
-      ],
-      '@typescript-eslint/consistent-type-imports': 'error',
-      '@typescript-eslint/no-import-type-side-effects': 'error',
-    },
-  },
-  {
-    ignores: ['dist/**', 'node_modules/**', '*.js'],
-  }
-);

package/jest.config.js

@@ -1,22 +0,0 @@
-/** @type {import('ts-jest').JestConfigWithTsJest} */
-export default {
-  preset: 'ts-jest/presets/default-esm',
-  testEnvironment: 'node',
-  roots: ['<rootDir>/src'],
-  testMatch: ['**/*.test.ts'],
-  moduleNameMapper: {
-    '^(\\.{1,2}/.*)\\.js$': '$1',
-  },
-  transform: {
-    '^.+\\.tsx?$': [
-      'ts-jest',
-      {
-        useESM: true,
-      },
-    ],
-  },
-  extensionsToTreatAsEsm: ['.ts'],
-  collectCoverageFrom: ['src/**/*.ts', '!src/**/*.test.ts', '!src/**/*.d.ts'],
-  coverageDirectory: 'coverage',
-  coverageReporters: ['text', 'lcov', 'html'],
-};

package/knowledge-library/README.md

@@ -1,118 +0,0 @@
-# Knowledge Library
-
-Shared context and agent communication hub for the development team.
-
-## Structure
-
-```
-knowledge-library/
-├── README.md              # This file
-├── context.txt            # Overall project state (EM updates)
-├── architecture.txt       # Architecture decisions (EM updates)
-├── prd.txt                # Product requirements (PM/EM updates)
-├── workflows.md           # Symlink or copy of ../WORKFLOWS.md
-│
-├── [agent-name]/          # Per-agent directories
-│   ├── inbox/             # Messages received from other agents
-│   │   └── processed/     # Completed messages (archived)
-│   ├── outbox/            # Copies of sent messages
-│   ├── context/           # Agent's current state
-│   │   └── current.txt    # Current context file
-│   ├── history/           # Archived context files
-│   ├── tech/              # Technical docs, specs, designs
-│   └── control/           # Objectives, decisions, dependencies
-│       ├── objectives.txt
-│       ├── decisions.txt
-│       └── dependencies.txt
-```
-
-## Shared Context Files
-
-### context.txt
-Overall project state updated by Engineering Manager:
-- Current sprint and priorities
-- Active work and blockers
-- Recent decisions
-- Team status
-
-### architecture.txt
-Technical architecture decisions:
-- System design
-- Technology choices
-- Data models
-- Integration patterns
-
-### prd.txt
-Product requirements:
-- Feature specifications
-- User stories
-- Acceptance criteria
-- Priorities
-
-## Agent Directories
-
-Each agent has their own directory for:
-
-| Directory | Purpose | Who Updates |
-|-----------|---------|-------------|
-| `inbox/` | Receive tasks and messages | Other agents write here |
-| `inbox/processed/` | Archive of completed messages | Owner moves here |
-| `outbox/` | Copies of sent messages | Owner writes here |
-| `context/current.txt` | Agent's current state | Owner updates |
-| `history/` | Archived context snapshots | Owner archives |
-| `tech/` | Technical docs, specs | Owner creates |
-| `control/` | Objectives, decisions | Owner maintains |
-
-## Message File Naming
-
-### Inbox (received)
-```
-YYYYMMDD_HHMM-[from-agent]-[topic].md
-Example: 20260105_1430-engineering-manager-SUR-70-assignment.md
-```
-
-### Inbox Processed (archived)
-```
-PROCESSED_YYYYMMDD_HHMM_[original-filename].md
-Example: PROCESSED_20260105_1600_20260105_1430-engineering-manager-SUR-70-assignment.md
-```
-
-### Outbox (sent copies)
-```
-YYYYMMDD_HHMM-to-[recipient]-[topic].md
-Example: 20260105_1430-to-wearos-engineer-SUR-70-assignment.md
-```
-
-## Usage Rules
-
-1. **Root files** (context.txt, architecture.txt, prd.txt) - Only EM updates
-2. **All agents read** root files at startup
-3. **All agents update** their own context before finishing
-4. **All agents send** completion summaries to EM inbox
-5. **Move processed messages** to `inbox/processed/` to prevent duplicate work
-
-## Permissions Matrix
-
-| Agent | Create Tickets | Update Root Files | Own Directory |
-|-------|:--------------:|:-----------------:|:-------------:|
-| engineering-manager | ✅ | ✅ | ✅ |
-| solutions-architect | ✅ | ❌ | ✅ |
-| security-engineer | ✅ | ❌ | ✅ |
-| qa-engineer | ✅ | ❌ | ✅ |
-| product-manager | ✅ | ✅ (prd.txt) | ✅ |
-| backend-engineer | ❌ | ❌ | ✅ |
-| android-engineer | ❌ | ❌ | ✅ |
-| wearos-engineer | ❌ | ❌ | ✅ |
-| devops-engineer | ❌ | ❌ | ✅ |
-
-## External Integration
-
-This Knowledge Library works alongside:
-- **Jira** - Primary ticket tracking (MCP access)
-- **Confluence** - Primary documentation (MCP access)
-- **GitHub** - Code and PRs (gh CLI)
-
-Local files serve as:
-- Async communication between agents
-- Fallback when external services unavailable
-- Context persistence between sessions

package/knowledge-library/android-engineer/context/current.txt

@@ -1,42 +0,0 @@
-# [Agent Name] - Current Context
-
-> **Last Updated:** [YYYY-MM-DD HH:MM]
-
-## Current Focus
-
-[What you're currently working on]
-
-## Active Tasks
-
-| Ticket | Status | Branch | PR |
-|--------|--------|--------|-----|
-| [KEY-XX] | [in-progress/pr-created/in-review] | [branch] | [#XX or -] |
-
-## Work in Progress
-
-### [KEY-XX] - [Title]
-- **Status:** [status]
-- **Branch:** [branch name]
-- **Progress:**
-  - [x] Completed item
-  - [ ] Pending item
-- **Blockers:** [None or description]
-
-## Pending Reviews
-
-| PR | Ticket | Requested By | Status |
-|----|--------|--------------|--------|
-| #XX | [KEY-XX] | [agent] | [pending/done] |
-
-## Technical Notes
-
-[Any technical context to remember]
-
-## Next Actions
-
-1. [ ] [Action 1]
-2. [ ] [Action 2]
-
-## Questions/Blockers
-
-- [Any questions for EM or other agents]

package/knowledge-library/android-engineer/control/decisions.txt

@@ -1,9 +0,0 @@
-# [Agent Name] - Decision Log
-
-Format: `[YYYY-MM-DD] Decision: [summary] | Rationale: [why]`
-
----
-
-## Decisions
-
-[YYYY-MM-DD] Decision: [example] | Rationale: [example]

package/knowledge-library/android-engineer/control/dependencies.txt

@@ -1,19 +0,0 @@
-# [Agent Name] - Dependencies
-
-## Waiting On
-
-| Dependency | From | Ticket | Status |
-|------------|------|--------|--------|
-| [what you need] | [agent] | [KEY-XX] | [waiting/resolved] |
-
-## Providing To
-
-| Deliverable | To | Ticket | Status |
-|-------------|-----|--------|--------|
-| [what you're providing] | [agent] | [KEY-XX] | [pending/delivered] |
-
-## External Dependencies
-
-| Dependency | Type | Status |
-|------------|------|--------|
-| [e.g., API access] | [service/data/approval] | [status] |

package/knowledge-library/android-engineer/control/objectives.txt

@@ -1,26 +0,0 @@
-# [Agent Name] - Objectives
-
-## Primary Objectives
-
-1. [Primary objective based on role]
-2. [Primary objective based on role]
-
-## Current Sprint Objectives
-
-- [ ] [Objective 1]
-- [ ] [Objective 2]
-
-## Quality Standards
-
-- [ ] All code has tests
-- [ ] Lint checks pass
-- [ ] Static analysis passes
-- [ ] Acceptance criteria met
-
-## Workflow Responsibilities
-
-- Move ticket to "In Progress" when starting
-- Create branch with correct naming
-- Run quality checks before PR
-- Move ticket to "In Review" after PR
-- Send completion report to EM

package/knowledge-library/architecture.txt

@@ -1,61 +0,0 @@
-# Architecture Context
-
-> **Last Updated:** [YYYY-MM-DD HH:MM]
-> **Updated By:** engineering-manager (with solutions-architect input)
-
-## System Overview
-
-[High-level description of the system architecture]
-
-## Components
-
-### [Component 1]
-- **Purpose:** [description]
-- **Technology:** [tech stack]
-- **Owner:** [agent]
-
-### [Component 2]
-- **Purpose:** [description]
-- **Technology:** [tech stack]
-- **Owner:** [agent]
-
-## Technology Stack
-
-| Layer | Technology | Notes |
-|-------|------------|-------|
-| [Layer] | [Tech] | [Notes] |
-
-## Architecture Principles
-
-1. **[Principle 1]** - [description]
-2. **[Principle 2]** - [description]
-3. **[Principle 3]** - [description]
-
-## Key Decisions
-
-| Date | Decision | Status | ADR |
-|------|----------|--------|-----|
-| [YYYY-MM-DD] | [decision] | [Active/Superseded] | [link] |
-
-## Data Model
-
-### Core Entities
-- **[Entity 1]:** [description]
-- **[Entity 2]:** [description]
-
-## Integration Points
-
-| System | Integration Type | Owner |
-|--------|-----------------|-------|
-| [System] | [API/Event/etc] | [agent] |
-
-## Constraints
-
-- [Constraint 1]
-- [Constraint 2]
-
-## References
-
-- [Link to detailed architecture docs]
-- [Link to ADRs]
-- [Link to diagrams]

package/knowledge-library/backend-engineer/context/current.txt

@@ -1,42 +0,0 @@
-# [Agent Name] - Current Context
-
-> **Last Updated:** [YYYY-MM-DD HH:MM]
-
-## Current Focus
-
-[What you're currently working on]
-
-## Active Tasks
-
-| Ticket | Status | Branch | PR |
-|--------|--------|--------|-----|
-| [KEY-XX] | [in-progress/pr-created/in-review] | [branch] | [#XX or -] |
-
-## Work in Progress
-
-### [KEY-XX] - [Title]
-- **Status:** [status]
-- **Branch:** [branch name]
-- **Progress:**
-  - [x] Completed item
-  - [ ] Pending item
-- **Blockers:** [None or description]
-
-## Pending Reviews
-
-| PR | Ticket | Requested By | Status |
-|----|--------|--------------|--------|
-| #XX | [KEY-XX] | [agent] | [pending/done] |
-
-## Technical Notes
-
-[Any technical context to remember]
-
-## Next Actions
-
-1. [ ] [Action 1]
-2. [ ] [Action 2]
-
-## Questions/Blockers
-
-- [Any questions for EM or other agents]

package/knowledge-library/backend-engineer/control/decisions.txt

@@ -1,9 +0,0 @@
-# [Agent Name] - Decision Log
-
-Format: `[YYYY-MM-DD] Decision: [summary] | Rationale: [why]`
-
----
-
-## Decisions
-
-[YYYY-MM-DD] Decision: [example] | Rationale: [example]

package/knowledge-library/backend-engineer/control/dependencies.txt

@@ -1,19 +0,0 @@
-# [Agent Name] - Dependencies
-
-## Waiting On
-
-| Dependency | From | Ticket | Status |
-|------------|------|--------|--------|
-| [what you need] | [agent] | [KEY-XX] | [waiting/resolved] |
-
-## Providing To
-
-| Deliverable | To | Ticket | Status |
-|-------------|-----|--------|--------|
-| [what you're providing] | [agent] | [KEY-XX] | [pending/delivered] |
-
-## External Dependencies
-
-| Dependency | Type | Status |
-|------------|------|--------|
-| [e.g., API access] | [service/data/approval] | [status] |