@devo-bmad-custom/agent-orchestration 1.0.0

package/src/_memory/skills/excalidraw/SKILL.md

@@ -0,0 +1,78 @@
+---
+name: excalidraw
+description: Use when creating hand-drawn style diagrams, workflow maps, architecture diagrams, flowcharts, mind maps, or any visual diagram output in Excalidraw JSON format (.excalidraw files)
+---
+
+# Excalidraw Diagram Creation Skill
+
+## Core Structure
+
+Excalidraw files are JSON with `"type": "excalidraw"`, `"version": 2`, plus `elements`, `appState`, and `files` arrays.
+
+## Primary Element Types
+
+`rectangle`, `ellipse`, `diamond`, `text`, `arrow`, `line`, `freedraw`, `image`, `frame`
+
+Every element requires: `type`, `id`, `x`, `y`, `width`, `height`, `angle`, `strokeColor`, `backgroundColor`, `fillStyle`, `strokeWidth`, `strokeStyle`, `roughness`, `opacity`, `seed`, `version`, `versionNonce`, `isDeleted`, `groupIds`, `boundElements`, `link`, `locked`
+
+## Key Styling
+
+- `fillStyle`: `"solid"`, `"hachure"`, `"cross-hatch"`
+- `strokeWidth`: `1` (thin), `2` (medium), `4` (bold)
+- `strokeStyle`: `"solid"`, `"dashed"`, `"dotted"`
+- `roughness`: `0` (clean), `1` (artist), `2` (sketchy)
+- `roundness`: `{ "type": 3 }` for rounded corners, `null` for sharp
+
+## Arrows & Bindings
+
+```json
+{
+  "type": "arrow",
+  "points": [[0, 0], [200, 0]],
+  "startArrowhead": null,
+  "endArrowhead": "arrow",
+  "startBinding": { "elementId": "rect-1", "focus": 0, "gap": 5 },
+  "endBinding": { "elementId": "rect-2", "focus": 0, "gap": 5 }
+}
+```
+
+Bound shapes need `"boundElements": [{ "id": "arrow-id", "type": "arrow" }]`
+
+## Text Inside Shapes
+
+```json
+// Shape:
+{ "id": "box1", "boundElements": [{ "id": "lbl1", "type": "text" }] }
+// Text:
+{ "id": "lbl1", "type": "text", "containerId": "box1", "verticalAlign": "middle", "textAlign": "center" }
+```
+
+## Color Palette (Professional)
+
+| Purpose | Color |
+|---------|-------|
+| Start/End | `#b2f2bb` |
+| Process/Action | `#a5d8ff` |
+| Decision | `#ffec99` |
+| Error/Critical | `#ffc9c9` |
+| Review/Gate | `#d0bfff` |
+| Neutral/Background | `#e9ecef` |
+
+## Diagram Type Quick Reference
+
+| Type | Shapes | Direction |
+|------|--------|-----------|
+| Flowchart | rect + diamond | Top→Bottom |
+| Architecture | rect layers | Top→Bottom |
+| Mind Map | ellipse + lines | Center→Out |
+| Sequence | rect + lifelines | Left→Right |
+
+## Full Reference Files
+
+- `diagram-patterns.md` — swimlanes, sequence, architecture patterns
+- `examples.md` — working JSON templates
+- `element-reference.md` — complete property specifications
+
+## Output
+
+Always write the final diagram to a `.excalidraw` file. User can open it directly at excalidraw.com or in the desktop app.

package/src/_memory/skills/excalidraw/diagram-patterns.md

@@ -0,0 +1,53 @@
+# Professional Diagram Patterns
+
+## Flowchart Color Coding
+- Start/End: `#b2f2bb` (green) — ellipse
+- Process/Action: `#a5d8ff` (blue) — rect with roundness
+- Decision/Gate: `#ffec99` (yellow) — diamond
+- Error/Critical: `#ffc9c9` (red) — diamond
+- Review/PMR: `#d0bfff` (purple) — diamond
+- QA/Teal: `#99e9f2` (teal) — rect
+- Parallel: `#ffd8a8` (orange) — rect (wide)
+
+## Swimlane Pattern
+Use large rects with `backgroundColor: "transparent"` and `strokeStyle: "dashed"` for lanes.
+Add lane headers at top. Horizontal arrows cross lane boundaries.
+
+## Sequence Diagram Components
+1. Actors: rounded rect, colored backgrounds
+2. Lifelines: vertical dashed lines (`strokeStyle: "dashed"`, `strokeWidth: 1`)
+3. Sync messages: solid arrows
+4. Return messages: dashed arrows, `strokeColor: "#868e96"`
+5. Spacing: 200px between participants, 50-80px between messages
+
+## Architecture Layers (top to bottom)
+- Presentation: `#a5d8ff`
+- Business: `#b2f2bb`
+- Data: `#d0bfff`
+
+## Mind Map Sizing
+| Level | Font | Shape | Stroke |
+|-------|------|-------|--------|
+| Center | 28-36 | 180x100 | 4 |
+| Level 1 | 20-24 | 140x70 | 2 |
+| Level 2 | 16-18 | 100x50 | 2 |
+
+## Arrow Conventions
+| Style | Meaning |
+|-------|---------|
+| Solid + arrow | Primary flow |
+| Dashed + arrow | Response / async / optional path |
+| Thick solid | Critical path |
+| Color coded | Green=pass, Red=fail, Blue=normal |
+
+## Loop-back Arrows (L-shaped)
+Start from element left edge, go left (-50px), go up to target y, go right to target left edge.
+```json
+"x": shape_left_x, "y": shape_center_y,
+"points": [[0,0], [-50,0], [-50, -(delta_y)], [0, -(delta_y)]]
+```
+
+## Roughness Guide
+- `0` — clean, formal, technical
+- `1` — artist (default, professional)
+- `2` — sketchy, brainstorm feel

package/src/_memory/skills/nimbalyst-tracking/SKILL.md

@@ -0,0 +1,103 @@
+---
+name: nimbalyst-tracking
+description: Nimbalyst structured item tracking syntax. Use when identifying tasks, bugs, ideas, or decisions.
+---
+
+# SKILL: Nimbalyst Structured Tracking
+
+## Goal
+Integrate structured item tracking across all AI agent interactions using YAML frontmatter blocks.
+
+## Tracked Item Types
+- `task`: Actionable items to be completed.
+- `bug`: Defects found in code or design.
+- `idea`: Potential improvements or new concepts.
+- `decision`: Key architectural or product decisions.
+- `feature-request`: User or stakeholder requested features.
+- `technical-debt`: Identified code or architecture smells.
+- `user-feedback`: Feedback gathered from users.
+- `user-story`: Agile user stories generated during planning.
+- `plan`: Planning items.
+
+## Rules
+1. **Structured YAML Blocks**: Output trackable items as `trackingStatus` YAML frontmatter in markdown files.
+2. **Capture Aggressively**: Every time you identify a bug, make a decision, or propose an idea, create a tracker.
+3. **File Placement**: Write tracker files to `nimbalyst-local/tracker/[type]-[id].md`
+4. **MCP Bridge**: If you have access to `tracker_create` or `tracker_update` MCP tools (Nimbalyst environment), call them directly IN ADDITION to writing the file. This ensures items appear immediately on the Nimbalyst Trackers page.
+5. **Status Updates**: When updating an existing item's status:
+   - Update the `status` and `updated` fields in the file's YAML frontmatter
+   - If `nimbalystId` is present in frontmatter, call `tracker_update(id: nimbalystId, status: mapped_status)`
+   - If `nimbalystId` is NOT present, search `tracker_list(search: title)` to find the item, then call `tracker_update`
+
+### MCP Tool Field Mapping
+
+| YAML Field | MCP `tracker_create` Param | Notes |
+|------------|---------------------------|-------|
+| `title`    | `title`                   | Required |
+| `type`     | `type`                    | task, bug, idea, decision |
+| `priority` | `priority`                | low, medium, high, critical |
+| `status`   | `status`                  | See status mapping below |
+| `tags`     | `tags`                    | Pass as array |
+| body       | `description`             | Markdown description |
+
+### Status Mapping (File -> Nimbalyst MCP)
+
+| File Status    | Nimbalyst Status |
+|---------------|-----------------|
+| Draft          | to-do           |
+| Ready          | to-do           |
+| In Development | in-progress     |
+| In Review      | in-progress     |
+| Completed      | done            |
+| Rejected       | to-do           |
+| Blocked        | to-do           |
+
+## Item Structure
+
+Each tracker item is a markdown file with this frontmatter:
+
+```yaml
+---
+trackingStatus:
+  itemId: [type]-[unique-id]
+  nimbalystId: [nimbalyst-id]    # Set by sync automation or MCP bridge - enables direct updates
+  title: [Short Description]
+  type: [task|bug|idea|decision]
+  status: [Draft|Ready|In Development|In Review|Completed|Rejected|Blocked]
+  priority: [None|Low|Medium|High|Critical]
+  assignee: [username]
+  tags:
+    - [tag1]
+    - [tag2]
+  created: "YYYY-MM-DD"
+  updated: "YYYY-MM-DDTHH:MM:SS.sssZ"
+---
+
+Description and details here.
+```
+
+## Example Usage
+
+If you are the Architect and you just decided to use Redis for pub/sub:
+
+"I have decided to use Redis for the WebSocket pub/sub implementation. Here is the recorded decision:
+
+```yaml
+---
+trackingStatus:
+  itemId: decision-pubsub-01
+  title: "Use Redis for WebSocket Pub/Sub"
+  type: decision
+  status: Completed
+  priority: Medium
+  assignee: []
+  tags:
+    - architecture
+    - websockets
+    - redis
+  created: "2026-03-11"
+  updated: "2026-03-11T12:00:00.000Z"
+---
+```
+
+"