@deimoscloud/coreai 0.1.18 → 0.1.20

package/skills/git/worktree-cleanup/SKILL.md

@@ -0,0 +1,168 @@
+---
+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
+requires: [git]
+---
+
+# 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/skills/git/worktree-setup/SKILL.md

@@ -0,0 +1,112 @@
+---
+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]
+requires: [git]
+optional: [jira]
+---
+
+# 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/skills/jira/jira-create/SKILL.md

@@ -0,0 +1,201 @@
+---
+description: Use when creating a Jira ticket, adding a new task to backlog, reporting a bug, or creating a feature request. Ensures tickets have all required fields and follow the standard template.
+argument-hint: <type> <title> [description]
+requires: [jira]
+---
+
+# Create Jira Ticket
+
+You are creating a Jira ticket for: **$ARGUMENTS**
+
+## Ticket Types
+
+| Type | Use For |
+|------|---------|
+| **Story** | New user-facing features |
+| **Task** | Technical work, refactoring, infrastructure |
+| **Bug** | Defects, issues, broken functionality |
+| **Spike** | Research, investigation, prototyping |
+| **Improvement** | Enhancements to existing features |
+
+## Required Fields
+
+Every ticket MUST have:
+
+1. **Summary** - Clear, concise title
+2. **Type** - Story, Task, Bug, Spike, or Improvement
+3. **Description** - What needs to be done and why
+4. **Acceptance Criteria** - Definition of done (checklist)
+5. **Priority** - P0 (Critical), P1 (High), P2 (Medium), P3 (Low)
+6. **Labels** - Relevant labels
+
+## Create Ticket via Atlassian MCP
+
+### Using MCP
+
+```
+mcp__atlassian__createJiraIssue
+
+Project: {{JIRA_PROJECT}}
+Issue Type: <Story|Task|Bug|Spike|Improvement>
+Summary: <Clear title>
+Description: <Detailed description>
+Priority: <P0|P1|P2|P3>
+Labels: <comma-separated labels>
+```
+
+### Description Template
+
+```markdown
+## Overview
+[Brief description of what needs to be done]
+
+## Background
+[Why this is needed, context, related tickets]
+
+## Requirements
+- [Requirement 1]
+- [Requirement 2]
+
+## Acceptance Criteria
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+- [ ] [Criterion 3]
+- [ ] Unit tests written and passing
+- [ ] Code reviewed and approved
+
+## Technical Notes
+[Any technical considerations, constraints, or suggestions]
+
+## References
+- [Links to PRD, design docs, related tickets]
+```
+
+## Ticket Templates by Type
+
+### Story Template
+
+```markdown
+## User Story
+As a [user type], I want [functionality] so that [benefit].
+
+## Background
+[Context and motivation]
+
+## Acceptance Criteria
+- [ ] [User-visible outcome 1]
+- [ ] [User-visible outcome 2]
+- [ ] Unit tests written
+- [ ] Manual testing completed
+
+## Design
+[Link to UI mockups if applicable]
+```
+
+### Bug Template
+
+```markdown
+## Bug Description
+[Clear description of the bug]
+
+## Steps to Reproduce
+1. [Step 1]
+2. [Step 2]
+3. [Step 3]
+
+## Expected Behavior
+[What should happen]
+
+## Actual Behavior
+[What actually happens]
+
+## Environment
+- Device: [e.g., device type]
+- OS Version: [e.g., version]
+- App Version: [e.g., 1.0.0]
+
+## Acceptance Criteria
+- [ ] Bug is fixed
+- [ ] Regression test added
+- [ ] Verified on affected device
+```
+
+### Task Template
+
+```markdown
+## Task Description
+[What needs to be done]
+
+## Background
+[Why this task is needed]
+
+## Scope
+- [Item 1]
+- [Item 2]
+
+## Out of Scope
+- [Item that is NOT part of this task]
+
+## Acceptance Criteria
+- [ ] [Deliverable 1]
+- [ ] [Deliverable 2]
+- [ ] Documentation updated (if applicable)
+```
+
+## Priority Guidelines
+
+| Priority | Criteria | Response |
+|----------|----------|----------|
+| **P0** | Production down, data loss, security issue | Immediate |
+| **P1** | Major feature broken, blocking release | This sprint |
+| **P2** | Important but not blocking | Next sprint |
+| **P3** | Nice to have, minor improvements | Backlog |
+
+## Local Fallback
+
+If Atlassian MCP is unavailable, create a local ticket file:
+
+**Path:** `/KnowledgeLibrary/tickets/backlog/{{JIRA_PROJECT}}-XXX-[short-description].md`
+
+```markdown
+# [{{JIRA_PROJECT}}-XXX] [Title]
+
+## Metadata
+- **Status:** Backlog
+- **Priority:** [P0|P1|P2|P3]
+- **Type:** [Story|Task|Bug|Spike|Improvement]
+- **Created By:** [agent-name]
+- **Created Date:** [YYYY-MM-DD]
+- **Labels:** [comma-separated]
+
+## Description
+[Full description]
+
+## Acceptance Criteria
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+
+## References
+- [Links]
+```
+
+## Completion
+
+After ticket creation, report:
+```
+Jira Ticket Created
+
+Ticket: {{JIRA_PROJECT}}-XXX
+Title: [Summary]
+Type: [Type]
+Priority: [Priority]
+Status: Backlog
+
+URL: {{JIRA_URL}}/browse/{{JIRA_PROJECT}}-XXX
+
+Next Steps:
+- Ticket is in Backlog, ready for sprint planning
+- Use /delegate to assign when ready
+```
+
+Now proceed with ticket creation.

package/skills/jira/jira-transition/SKILL.md

@@ -0,0 +1,185 @@
+---
+description: Use when updating a Jira ticket status, moving a ticket to a different state, marking a ticket as done, starting work on a ticket, or putting a ticket in review. Handles status transitions with proper comments.
+argument-hint: TICKET-XX to <status>
+requires: [jira]
+---
+
+# Jira Ticket Transition
+
+You are transitioning: **$ARGUMENTS**
+
+## Valid Status Transitions
+
+```
+Backlog → To Do → In Progress → In Review → Done
+                ↓
+              Blocked
+                ↓
+            In Progress
+```
+
+| From | To | When |
+|------|-----|------|
+| Backlog | To Do | Sprint planning, ticket prioritized |
+| To Do | In Progress | Work begins on ticket |
+| In Progress | In Review | PR created |
+| In Progress | Blocked | Dependency or blocker identified |
+| Blocked | In Progress | Blocker resolved |
+| In Review | In Progress | PR feedback requires changes |
+| In Review | Done | PR merged, work complete |
+
+## Transition via Atlassian MCP
+
+### Get Current Status First
+
+```
+mcp__atlassian__getJiraIssue
+Issue Key: {{JIRA_PROJECT}}-XX
+```
+
+### Transition Ticket
+
+```
+mcp__atlassian__transitionJiraIssue
+Issue Key: {{JIRA_PROJECT}}-XX
+Transition: <target status>
+```
+
+### Add Transition Comment
+
+```
+mcp__atlassian__addCommentToJiraIssue
+Issue Key: {{JIRA_PROJECT}}-XX
+Comment: <transition comment>
+```
+
+## Required Comments by Transition
+
+### To Do → In Progress
+
+```
+Starting work on this ticket.
+Assigned to: @[agent-name]
+Branch: feature/{{JIRA_PROJECT}}-XX-[description]
+```
+
+### In Progress → In Review
+
+```
+PR created: <PR URL>
+
+Changes implemented:
+- [Change 1]
+- [Change 2]
+
+Ready for code review.
+```
+
+### In Progress → Blocked
+
+```
+BLOCKED: [Reason for block]
+
+Blocking issue: [Description or ticket reference]
+Required to unblock: [What needs to happen]
+```
+
+### Blocked → In Progress
+
+```
+Blocker resolved: [How it was resolved]
+Resuming work.
+```
+
+### In Review → In Progress
+
+```
+Addressing review feedback:
+- [Feedback item 1]
+- [Feedback item 2]
+
+Will update PR when changes are complete.
+```
+
+### In Review → Done
+
+```
+PR merged: [Merge commit SHA or PR URL]
+
+Acceptance criteria verified:
+- [x] [Criterion 1]
+- [x] [Criterion 2]
+
+Ticket complete.
+```
+
+## Workflow Integration
+
+This skill integrates with the workflow defined in `WORKFLOWS.md`:
+
+| Workflow State | Jira Status |
+|----------------|-------------|
+| BACKLOG | Backlog |
+| ASSIGNED | In Progress |
+| BRANCH_CREATED | In Progress |
+| IMPLEMENTING | In Progress |
+| PR_CREATED | In Review |
+| IN_REVIEW | In Review |
+| APPROVED | In Review |
+| MERGED | Done |
+| VERIFIED | Done |
+| DONE | Done |
+
+## Validation
+
+Before transitioning, verify:
+
+### To "In Progress"
+- [ ] Ticket has clear acceptance criteria
+- [ ] No blocking dependencies
+- [ ] Agent is ready to begin work
+
+### To "In Review"
+- [ ] PR exists and is linked
+- [ ] All commits pushed
+- [ ] CI checks passing (or will pass)
+
+### To "Done"
+- [ ] PR is merged
+- [ ] Acceptance criteria met
+- [ ] No open review comments
+
+### To "Blocked"
+- [ ] Blocker is clearly documented
+- [ ] Blocking ticket/issue referenced if applicable
+
+## Error Handling
+
+**If transition fails:**
+1. Check current ticket status
+2. Verify the transition is valid from current status
+3. Some transitions may require specific permissions
+
+**If MCP is unavailable:**
+Report to user:
+```
+Unable to transition ticket via MCP.
+Please manually update {{JIRA_PROJECT}}-XX to [status] in Jira.
+Add comment: [suggested comment]
+```
+
+## Completion
+
+After transition, report:
+```
+Jira Ticket Transitioned
+
+Ticket: {{JIRA_PROJECT}}-XX
+Previous Status: [old status]
+New Status: [new status]
+Comment Added: Yes
+
+URL: {{JIRA_URL}}/browse/{{JIRA_PROJECT}}-XX
+```
+
+Now proceed with the ticket transition.