@deimoscloud/coreai 0.1.9 → 0.1.10

package/commands/core/review.md

@@ -1,56 +0,0 @@
----
-description: Request PR review from agents using inbox-based delegation
-argument-hint: PR #<number> by <agent-name(s)>
----
-
-# PR Review Request
-
-You are the Engineering Manager. Assign this review: **$ARGUMENTS**
-
-## CRITICAL RULES - READ FIRST
-
-1. **DO NOT USE THE TASK TOOL** - You must NOT invoke agents directly
-2. **USE INBOX FILES ONLY** - Write review requests to agent inbox directories
-3. **TELL USER TO INVOKE** - End your response telling the user which agent(s) to invoke
-
-## Review Delegation Steps
-
-1. Get PR details: `gh pr view <number>`
-2. Identify the Jira ticket from PR title/body
-3. For EACH reviewer agent:
-   - Write review request to `/KnowledgeLibrary/[agent-name]/inbox/YYYYMMDD_HHMM-engineering-manager-review-PR-XX.md`
-   - Include: PR number, PR URL, what to review, workflow reference
-4. Save copies to your outbox
-5. End with instructions for the user to invoke each reviewer
-
-## Review Request Template
-
-```markdown
-## PR Review Request
-**From:** engineering-manager
-**Date:** [date]
-**PR:** #[number] - [title]
-**PR URL:** https://github.com/{{GITHUB_REPO}}/pull/[number]
-
-### Review Focus
-- [Architecture alignment / Security / Test coverage - based on agent role]
-
-### Workflow Requirements
-Follow Code Review workflow in WORKFLOWS.md:
-1. Review the PR thoroughly
-2. Post your review as a GitHub PR comment using `gh pr comment`
-3. State APPROVED or CHANGES_REQUESTED with your decision
-4. Send summary to my inbox
-```
-
-## End Your Response With
-
-```
----
-**Next Action Required:**
-Please invoke the reviewers:
-- `@solutions-architect check your inbox and review PR #XX`
-- `@security-engineer check your inbox and review PR #XX`
-```
-
-Now proceed with the review delegation.

package/commands/core/sprint-status.md

@@ -1,65 +0,0 @@
----
-description: Review current sprint progress and status (EM only)
-argument-hint: [optional: sprint number or "current"]
----
-
-# Sprint Status Review
-
-You are the Engineering Manager. Review the current sprint status and provide a summary.
-
-## Steps
-
-1. **Check Jira for current sprint:**
-   ```
-   Search: project = {{JIRA_PROJECT}} AND sprint in openSprints()
-   ```
-
-2. **Gather ticket status:**
-   - Count tickets by status (Backlog, In Progress, In Review, Done)
-   - Identify any blocked tickets
-   - Check for overdue items
-
-3. **Check agent inboxes for pending work:**
-   - `/KnowledgeLibrary/*/inbox/` - any unprocessed tasks?
-   - Are there completion summaries in your inbox you haven't processed?
-
-4. **Review open PRs:**
-   ```
-   gh pr list --state open
-   ```
-
-5. **Provide summary report:**
-
-```markdown
-## Sprint Status Report
-**Date:** [today]
-**Sprint:** [sprint name/number]
-
-### Ticket Summary
-| Status | Count | Tickets |
-|--------|-------|---------|
-| Done | X | {{JIRA_PROJECT}}-XX, {{JIRA_PROJECT}}-YY |
-| In Review | X | {{JIRA_PROJECT}}-XX |
-| In Progress | X | {{JIRA_PROJECT}}-XX |
-| Blocked | X | {{JIRA_PROJECT}}-XX (reason) |
-| Backlog | X | {{JIRA_PROJECT}}-XX |
-
-### Open PRs
-- PR #XX - [title] - [status: awaiting review/changes requested/approved]
-
-### Pending Agent Work
-- [agent]: [pending task or "inbox clear"]
-
-### Blockers & Risks
-- [Any blockers or risks to sprint completion]
-
-### Recommended Actions
-1. [Action item]
-2. [Action item]
-```
-
-## Additional Context
-
-$ARGUMENTS
-
-Now review the sprint status.

package/commands/optional/docs-update.md

@@ -1,200 +0,0 @@
----
-description: Use when updating documentation, adding to Confluence, documenting changes, updating local docs, or keeping documentation in sync. Handles both Confluence pages and local /docs files.
-argument-hint: <what to document> [where]
----
-
-# Documentation Update
-
-You are documenting: **$ARGUMENTS**
-
-## Documentation Locations
-
-| Location | Content Type | When to Update |
-|----------|--------------|----------------|
-| **Confluence** | Architecture, PRD, standards, guides | Major decisions, feature specs, process changes |
-| **Local /docs** | Technical workflows, setup guides | Development process, CI/CD, environment setup |
-| **Code comments** | Implementation details | Complex logic, non-obvious code |
-| **README files** | Module overviews | New modules, significant changes |
-
-## Confluence Pages (Primary)
-
-### Update via Atlassian MCP
-
-#### Read Current Page
-
-```
-mcp__atlassian__getConfluencePage
-Page ID: <page-id>
-```
-
-#### Update Page
-
-```
-mcp__atlassian__updateConfluencePage
-Page ID: <page-id>
-Title: <page title>
-Content: <updated content in Confluence storage format>
-```
-
-#### Create New Page
-
-```
-mcp__atlassian__createConfluencePage
-Space Key: {{CONFLUENCE_SPACE}}
-Title: <page title>
-Content: <content in Confluence storage format>
-Parent Page ID: <parent-id> (optional)
-```
-
-### Confluence Content Format
-
-Confluence uses storage format (HTML-like). Common patterns:
-
-```html
-<h2>Section Title</h2>
-<p>Paragraph text.</p>
-
-<ul>
-  <li>Bullet point 1</li>
-  <li>Bullet point 2</li>
-</ul>
-
-<ac:structured-macro ac:name="code">
-  <ac:parameter ac:name="language">kotlin</ac:parameter>
-  <ac:plain-text-body><![CDATA[
-    // code here
-  ]]></ac:plain-text-body>
-</ac:structured-macro>
-
-<ac:structured-macro ac:name="info">
-  <ac:rich-text-body>
-    <p>Info box content</p>
-  </ac:rich-text-body>
-</ac:structured-macro>
-```
-
-## Local Documentation (/docs)
-
-### Update Local Docs
-
-Use the Edit tool to update existing documentation:
-
-```
-Edit file: {{PROJECT_ROOT}}/docs/[filename].md
-```
-
-### Documentation Template
-
-```markdown
-# [Title]
-
-**Last Updated:** [YYYY-MM-DD]
-**Author:** [agent-name]
-
-## Overview
-
-[Brief description of what this document covers]
-
-## [Main Section]
-
-[Content]
-
-### [Subsection]
-
-[Content]
-
-## Related Documentation
-
-- [Link to related doc 1]
-- [Link to related doc 2]
-
----
-
-**Questions?** File a Jira ticket with component "Documentation".
-```
-
-## Keep Documentation in Sync
-
-When updating documentation, ensure both locations are updated:
-
-### Architecture Changes
-
-1. Update Confluence Architecture page (primary)
-2. Update `/KnowledgeLibrary/architecture.txt` (local cache)
-
-### Process Changes
-
-1. Update Confluence Development page (primary)
-2. Update `/docs/DEVELOPMENT_WORKFLOW.md` (local reference)
-
-### PRD Changes
-
-1. Update Confluence Product page (primary)
-2. Update `/KnowledgeLibrary/prd.txt` (local cache)
-
-## What to Document
-
-### Always Document
-
-- Architecture decisions and rationale
-- New modules or significant refactors
-- API changes or new endpoints
-- Configuration changes
-- Process changes
-- Breaking changes
-
-### Document When Significant
-
-- Bug fixes with non-obvious solutions
-- Performance optimizations
-- Security considerations
-- Integration details
-
-### Skip Documentation For
-
-- Minor bug fixes
-- Code formatting changes
-- Dependency version bumps (unless breaking)
-- Internal refactors with no API changes
-
-## Documentation Checklist
-
-Before completing documentation update:
-
-- [ ] Content is accurate and up-to-date
-- [ ] Examples are working and tested
-- [ ] Links are valid
-- [ ] Code snippets are correct
-- [ ] Related docs are cross-referenced
-- [ ] Both Confluence and local docs updated (if applicable)
-
-## Error Handling
-
-**If Confluence MCP is unavailable:**
-1. Update local documentation first
-2. Note in completion report: "Confluence update pending - please sync manually"
-3. Create a task to sync Confluence later
-
-**If page doesn't exist:**
-1. Create new page with `mcp__atlassian__createConfluencePage`
-2. Or create local doc and note Confluence page needs creation
-
-## Completion
-
-After documentation update, report:
-```
-Documentation Updated
-
-Updated:
-- [Confluence page name] (URL)
-- [Local file path]
-
-Changes:
-- [Summary of what was documented]
-
-Sync Status:
-- Confluence: [Updated/Pending]
-- Local docs: [Updated/N/A]
-```
-
-Now proceed with the documentation update.

package/commands/optional/jira-create.md

@@ -1,200 +0,0 @@
----
-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]
----
-
-# 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/commands/optional/jira-transition.md

@@ -1,184 +0,0 @@
----
-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>
----
-
-# 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.