@deimoscloud/coreai 0.1.9 → 0.1.10

package/WORKFLOWS.md

@@ -1,295 +0,0 @@
-# Workflow Definitions
-
-> **PURPOSE:** Defines mandatory workflows as state machines.
-> All agents MUST follow these workflows. Each state has required outputs.
-
----
-
-## Workflow 1: Ticket Implementation
-
-**Applies to:** Any Jira ticket being implemented
-
-### State Machine
-
-```
-BACKLOG → IN_PROGRESS → PR_CREATED → IN_REVIEW → APPROVED → MERGED → DONE
-```
-
-### State Definitions
-
-#### BACKLOG
-- **Entry:** Ticket exists, not yet assigned
-- **Owner:** EM
-- **Exit to IN_PROGRESS:** EM delegates to engineer via inbox
-
-#### IN_PROGRESS
-- **Entry conditions:**
-  - Engineer received task via inbox
-  - Engineer moves ticket to "In Progress" via Jira
-  - Engineer adds Jira comment: "Starting work. Branch: `feature/SUR-XX-description`"
-- **Owner:** Engineer
-- **Required outputs before exit:**
-  - [ ] Code changes complete
-  - [ ] Unit tests written and passing
-  - [ ] Lint checks pass
-  - [ ] Static analysis passes
-  - [ ] All acceptance criteria addressed
-- **Exit to PR_CREATED:** Engineer creates PR
-
-#### PR_CREATED
-- **Entry conditions:**
-  - Branch pushed to origin
-  - PR created with correct title format
-- **Owner:** Engineer
-- **Required outputs:**
-  - PR URL logged in completion report
-  - Jira comment: "PR created: [URL]"
-- **Exit to IN_REVIEW:** Engineer moves ticket to "In Review"
-
-#### IN_REVIEW
-- **Entry conditions:**
-  - Ticket status is "In Review"
-  - CI checks passing
-  - Completion report sent to EM inbox
-- **Owner:** Engineer → EM → Reviewers
-- **EM validation:**
-  - [ ] Ticket status correct
-  - [ ] PR exists
-  - [ ] CI passing
-  - [ ] Completion report valid
-- **Required outputs:**
-  - EM assigns reviewers via inbox
-  - Reviewers post approval/feedback on PR
-- **Exit to APPROVED:** Reviewer posts APPROVED decision
-
-#### APPROVED
-- **Entry conditions:**
-  - At least one approval posted on PR
-  - All review comments addressed
-  - CI still passing
-- **Owner:** User (human)
-- **Required action:** User merges PR
-- **Exit to MERGED:** PR merged to main
-
-#### MERGED
-- **Entry conditions:**
-  - PR merged to main
-  - CI passes on main
-- **Owner:** EM
-- **Required outputs:**
-  - Jira comment: "Merged to main: [commit SHA]"
-  - Ticket moved to "Done"
-- **Exit to DONE:** Verification complete
-
-#### DONE
-- **Entry conditions:**
-  - Jira ticket is "Done"
-  - All documentation updated
-- **Owner:** EM
-- **Workflow complete**
-
----
-
-## Workflow 2: Code Review
-
-**Applies to:** Any PR assigned for review
-
-### State Machine
-
-```
-ASSIGNED → REVIEWING → DECISION_POSTED
-```
-
-### State Definitions
-
-#### ASSIGNED
-- **Entry:** Reviewer receives request via inbox
-- **Owner:** Reviewer (solutions-architect, security-engineer, etc.)
-- **Exit to REVIEWING:** Reviewer begins review
-
-#### REVIEWING
-- **Required checks:**
-  - [ ] Code follows development standards
-  - [ ] Tests are adequate for changes
-  - [ ] No security vulnerabilities
-  - [ ] Architecture aligns with design
-  - [ ] Performance implications considered
-- **Exit to DECISION_POSTED:** Review complete
-
-#### DECISION_POSTED
-- **Required outputs:**
-  - Review comment posted on GitHub PR (via `gh pr comment`)
-  - Completion report sent to EM inbox
-- **Review comment format:**
-
-```markdown
-## Code Review: SUR-XX
-
-### Summary
-[Brief description of what was reviewed]
-
-### Checklist
-- [x] Code follows development standards
-- [x] Tests are adequate
-- [x] No security vulnerabilities
-- [x] Architecture aligns with design
-- [x] Performance considered
-
-### Findings
-- [Positive/concern/blocking items]
-
-### **DECISION: APPROVED** | **DECISION: CHANGES REQUESTED**
-
-[If APPROVED]: Ready for merge by repository owner.
-[If CHANGES REQUESTED]: Please address the issues marked above.
-
----
-*Review by: [agent-name]*
-```
-
----
-
-## Workflow 3: Release Process
-
-**Applies to:** Creating a new release for deployment
-
-### State Machine
-
-```
-PLANNING → VERSION_BUMPED → TAGGED → BUILD_VERIFIED → DEPLOYED
-```
-
-### State Definitions
-
-#### PLANNING
-- **Entry:** Release scope defined
-- **Required:** All included tickets merged to main
-- **Exit:** Version numbers updated
-
-#### VERSION_BUMPED
-- **Required outputs:**
-  - versionCode incremented
-  - versionName updated
-  - Version bump commit pushed
-- **Exit:** Git tag created
-
-#### TAGGED
-- **Required outputs:**
-  - Annotated tag: `watch-vX.Y.Z` or `phone-vX.Y.Z`
-  - Tag message includes release notes
-  - Release workflow triggered
-- **Exit:** Build completes
-
-#### BUILD_VERIFIED
-- **Required outputs:**
-  - GitHub Release created with artifacts
-  - ProGuard mapping attached
-- **Exit:** Deployed to testing track
-
-#### DEPLOYED
-- **Required outputs:**
-  - Deployed to Play Console track
-  - Installation verified
-  - Notification sent
-
----
-
-## Workflow 4: Hotfix Process
-
-**Applies to:** Critical bugs requiring immediate fix
-
-### State Machine
-
-```
-IDENTIFIED → HOTFIX_BRANCH → FIX_IMPLEMENTED → EXPEDITED_REVIEW → DEPLOYED
-```
-
-### State Definitions
-
-#### IDENTIFIED
-- **Entry:** Critical bug confirmed
-- **Required:** HOTFIX label on ticket, team notified
-- **Exit:** Hotfix branch created
-
-#### HOTFIX_BRANCH
-- **Required:** Branch from affected release or main
-- **Naming:** `hotfix/SUR-XX-description`
-- **Exit:** Fix coding started
-
-#### FIX_IMPLEMENTED
-- **Required outputs:**
-  - Minimal fix (no feature creep)
-  - Regression test added
-  - All checks passing
-- **Exit:** PR created
-
-#### EXPEDITED_REVIEW
-- **Required:** Single reviewer, focused on fix correctness
-- **Exit:** Approved and merged
-
-#### DEPLOYED
-- **Required outputs:**
-  - Version bumped to patch release
-  - Deployed directly to production
-  - Post-mortem scheduled
-
----
-
-## Checkpoint Reporting Format
-
-When completing any workflow state, report using this format:
-
-```markdown
-## Workflow Checkpoint
-**Workflow:** [Ticket Implementation | Code Review | Release | Hotfix]
-**Ticket:** SUR-XX
-**Previous State:** [state name]
-**Current State:** [state name]
-**Timestamp:** [YYYY-MM-DD HH:MM]
-
-### Entry Conditions Verified
-- [x] Condition 1
-- [x] Condition 2
-
-### Required Outputs Completed
-- [x] Output 1: [details/link]
-- [x] Output 2: [details/link]
-
-### Next State
-**Target:** [next state name]
-**Blockers:** [None | list blockers]
-```
-
----
-
-## Workflow Violations
-
-If unable to complete a required output:
-
-1. **STOP** - Do not proceed to next state
-2. **Report blocker** - Document what's missing
-3. **Escalate** - Notify appropriate agent
-4. **Wait** - Do not skip the step
-
-**Common violations to catch:**
-- Creating PR before tests pass
-- Merging without CI green
-- Skipping Jira status updates
-- Not posting review to GitHub PR
-- Missing workflow checkpoint in completion report
-
----
-
-## Quick Reference
-
-| Workflow | When to Use | Final State |
-|----------|-------------|-------------|
-| Ticket Implementation | Implementing a Jira ticket | DONE |
-| Code Review | Reviewing a PR | DECISION_POSTED |
-| Release | Creating a scheduled release | DEPLOYED |
-| Hotfix | Critical production bug | DEPLOYED |
-
----
-
-*Version: 1.0.0*
-*Last Updated: 2026-01-05*

package/commands/core/check-inbox.md

@@ -1,34 +0,0 @@
----
-description: Check your inbox for new tasks and process them
-argument-hint: [optional: and work on ticket]
----
-
-# Check Inbox
-
-You have been invoked to check your inbox and process any pending tasks.
-
-## Instructions
-
-1. **Read your inbox directory:** `/KnowledgeLibrary/[your-agent-name]/inbox/`
-   - Ignore the `processed/` subdirectory
-   - Look for `.md` files from other agents (especially engineering-manager)
-
-2. **For each unprocessed message:**
-   - Read the task details
-   - If it's a task assignment, begin work following the workflow in `WORKFLOWS.md`
-   - If it's a review request, perform the review
-
-3. **When you complete work:**
-   - Move processed inbox messages to `inbox/processed/` with prefix `PROCESSED_YYYYMMDD_HHMM_`
-   - Write completion summary to the sender's inbox (usually engineering-manager)
-   - End with "Please invoke @[next-agent]" instruction for the user
-
-4. **If inbox is empty:**
-   - Report "No pending tasks in inbox"
-   - Check Jira for any assigned tickets you should be working on
-
-## Additional Context
-
-$ARGUMENTS
-
-Now check your inbox and proceed.

package/commands/core/delegate.md

@@ -1,30 +0,0 @@
----
-description: Delegate a task to an agent using inbox-based delegation (NOT Task tool)
-argument-hint: <ticket-or-task> to <agent-name>
----
-
-# Delegation Request
-
-You are the Engineering Manager. Delegate this task: **$ARGUMENTS**
-
-## CRITICAL RULES - READ FIRST
-
-1. **DO NOT USE THE TASK TOOL** - You must NOT invoke agents directly
-2. **USE INBOX FILES ONLY** - Write task details to the agent's inbox directory
-3. **TELL USER TO INVOKE** - End your response telling the user which agent(s) to invoke
-
-## Delegation Steps
-
-1. Look up the ticket/PR details (use Jira MCP or `gh pr view`)
-2. Update Jira status if applicable (to "In Progress" or add review comment)
-3. Write task file to `/KnowledgeLibrary/[agent-name]/inbox/YYYYMMDD_HHMM-engineering-manager-[topic].md`
-4. Save copy to your outbox
-5. End with: "Please invoke: `@[agent-name] check your inbox`"
-
-## Remember
-
-- You have MCP access - use it to update Jira directly
-- Agents will have MCP access when the USER invokes them via @[agent-name]
-- If you invoke them via Task tool, they lose MCP access - DON'T DO THIS
-
-Now proceed with the delegation.

package/commands/core/git-commit.md

@@ -1,144 +0,0 @@
----
-description: Use when committing code changes, pushing to remote, or saving work. This is a GATED commit that enforces quality checks - all configured checks must pass before the commit proceeds.
-argument-hint: [commit message or ticket reference]
----
-
-# Gated Git Commit
-
-You are committing changes for: **$ARGUMENTS**
-
-## CRITICAL: Quality Gate
-
-**NO COMMIT will proceed until ALL checks pass.** This is non-negotiable.
-
-## Pre-Commit Checks (MANDATORY)
-
-Run these checks IN ORDER. If ANY fail, STOP and fix before proceeding.
-
-### 1. Code Formatting
-
-```bash
-{{LINT_CMD}}
-```
-
-**If fails:**
-- Run the format/fix command if available
-- Review changes
-- Re-run the check
-
-### 2. Static Analysis
-
-```bash
-{{STATIC_ANALYSIS_CMD}}
-```
-
-**If fails:**
-- Review the report
-- Fix code smells and issues
-- Re-run the check
-
-### 3. Unit Tests
-
-```bash
-{{TEST_CMD}}
-```
-
-**If fails:**
-- Review test failures
-- Fix failing tests or update tests for new behavior
-- Re-run tests
-
-### 4. Build Verification
-
-```bash
-{{BUILD_CMD}}
-```
-
-**If fails:**
-- Fix compilation errors
-- Re-run build
-
-## All Checks Passed?
-
-Only proceed to commit if you see **BUILD SUCCESSFUL** (or equivalent) for ALL checks above.
-
-## Commit Process
-
-### 1. Stage Changes
-
-```bash
-git add -A
-```
-
-Or stage specific files:
-```bash
-git add [specific files]
-```
-
-### 2. Commit with Proper Format
-
-**Commit message format:**
-```
-<type>(<scope>): <description> [{{JIRA_PROJECT}}-XX]
-
-[optional body with details]
-```
-
-**Types:** `feat`, `fix`, `refactor`, `test`, `docs`, `chore`, `style`, `perf`
-
-**Examples:**
-```bash
-git commit -m "feat(core): add new feature [{{JIRA_PROJECT}}-123]"
-git commit -m "fix(sync): resolve connection timeout [{{JIRA_PROJECT}}-456]"
-git commit -m "test(core): add unit tests for filtering [{{JIRA_PROJECT}}-789]"
-```
-
-### 3. Push to Remote
-
-```bash
-git push -u origin $(git branch --show-current)
-```
-
-## Commit Checklist
-
-Before committing, verify:
-- [ ] All quality checks passed
-- [ ] Commit message includes ticket number [{{JIRA_PROJECT}}-XX]
-- [ ] Commit message follows type(scope): description format
-- [ ] No debug code or commented-out blocks
-- [ ] No secrets or API keys in code
-- [ ] Changes are related to the ticket being worked on
-
-## Error Recovery
-
-**If checks fail repeatedly:**
-1. Report which specific check is failing
-2. Show the error output
-3. Ask for guidance if the fix is unclear
-
-**If push fails:**
-```bash
-# If remote has new commits, rebase first
-git fetch origin
-git rebase origin/main
-# Then push again
-git push -u origin $(git branch --show-current)
-```
-
-## Completion
-
-After successful commit and push, report:
-```
-Commit successful
-
-Branch: feature/{{JIRA_PROJECT}}-XX-description
-Commit: [short SHA] <commit message>
-Pushed to: origin/feature/{{JIRA_PROJECT}}-XX-description
-
-Quality checks passed:
-- [List of checks that passed]
-
-Ready for PR creation when implementation is complete.
-```
-
-Now proceed with the gated commit process.

package/commands/core/pr-create.md

@@ -1,193 +0,0 @@
----
-description: Use when creating a pull request, opening a PR, or when code is ready for review. Creates PR with proper format, links to Jira ticket, and automatically transitions the ticket to "In Review" status.
-argument-hint: [ticket reference or PR title]
----
-
-# Create Pull Request
-
-You are creating a PR for: **$ARGUMENTS**
-
-## Pre-PR Checklist
-
-Before creating a PR, verify:
-
-### 1. All Commits Pushed
-
-```bash
-git status
-```
-
-Ensure no uncommitted changes. If there are changes, use `/git-commit` first.
-
-### 2. Branch is Up-to-Date
-
-```bash
-git fetch origin main
-git log origin/main..HEAD --oneline
-```
-
-If behind main, rebase:
-```bash
-git rebase origin/main
-git push --force-with-lease
-```
-
-### 3. CI Checks Ready
-
-All local checks should have passed during `/git-commit`.
-
-## Extract Ticket Information
-
-### From Branch Name
-```bash
-git branch --show-current
-# Expected format: feature/{{JIRA_PROJECT}}-XX-description
-```
-
-### From Jira (if available)
-Use MCP to get ticket details:
-- Title
-- Description
-- Acceptance criteria
-
-## Create Pull Request
-
-### PR Title Format
-```
-[{{JIRA_PROJECT}}-XX] <Brief description>
-```
-
-**Examples:**
-- `[{{JIRA_PROJECT}}-123] Add feature state machine`
-- `[{{JIRA_PROJECT}}-456] Fix connection timeout handling`
-
-### PR Body Template
-
-```markdown
-## Summary
-
-Brief description of what this PR does.
-
-## Changes
-
-- Change 1
-- Change 2
-- Change 3
-
-## Ticket
-
-[{{JIRA_PROJECT}}-XX]({{JIRA_URL}}/browse/{{JIRA_PROJECT}}-XX)
-
-## Testing
-
-- [ ] Unit tests added/updated
-- [ ] Manual testing completed
-- [ ] Tested on [device/emulator]
-
-## Checklist
-
-- [ ] Code follows development standards
-- [ ] All quality checks pass
-- [ ] No debug code or TODOs left
-- [ ] Documentation updated (if applicable)
-```
-
-### Create PR with GitHub CLI
-
-```bash
-gh pr create \
-  --title "[{{JIRA_PROJECT}}-XX] <description>" \
-  --body "$(cat <<'EOF'
-## Summary
-
-<description>
-
-## Changes
-
-- <change 1>
-- <change 2>
-
-## Ticket
-
-[{{JIRA_PROJECT}}-XX]({{JIRA_URL}}/browse/{{JIRA_PROJECT}}-XX)
-
-## Testing
-
-- [ ] Unit tests added/updated
-- [ ] Manual testing completed
-
-## Checklist
-
-- [ ] Code follows development standards
-- [ ] All quality checks pass
-- [ ] No debug code or TODOs left
-EOF
-)"
-```
-
-## Update Jira Ticket
-
-**MANDATORY:** After PR is created, transition the Jira ticket to "In Review".
-
-### Using Atlassian MCP
-
-1. Transition ticket to "In Review" status
-2. Add comment with PR link:
-
-```
-PR created: <PR URL>
-
-Changes:
-- <summary of changes>
-
-Ready for code review.
-```
-
-### Fallback (if MCP unavailable)
-
-Report to user:
-```
-Please manually update Jira ticket {{JIRA_PROJECT}}-XX:
-- Status: In Review
-- Add comment with PR link: <URL>
-```
-
-## Request Review
-
-If you know who should review:
-```bash
-gh pr edit <PR_NUMBER> --add-reviewer <github-username>
-```
-
-## Completion
-
-After PR creation, report:
-```
-Pull Request Created
-
-PR: #<number> - [{{JIRA_PROJECT}}-XX] <title>
-URL: <github PR URL>
-Branch: feature/{{JIRA_PROJECT}}-XX-description -> main
-
-Jira Updated:
-- Ticket {{JIRA_PROJECT}}-XX transitioned to "In Review"
-- Comment added with PR link
-
-Next Steps:
-- CI checks will run automatically
-- Await code review
-- Address any feedback
-```
-
-## Error Handling
-
-**If PR creation fails:**
-- Check if branch is pushed: `git push -u origin $(git branch --show-current)`
-- Check if PR already exists: `gh pr list --head $(git branch --show-current)`
-- Check GitHub CLI auth: `gh auth status`
-
-**If Jira transition fails:**
-- Note the failure in your completion report
-- Ask user to manually update Jira
-
-Now proceed with PR creation.