Refactor AI workspace for improved context management and communication integration

- Introduced new commands and skills for workspace memory curation, professional communication, and status reporting.
- Updated existing commands to utilize new skills and improve clarity in instructions.
- Created a new workspace context command to load reusable core and active project profile.
- Enhanced Mattermost inbox integration with support for generic environment variables.
- Established a clear separation between project-independent core logic and project-specific profiles.
- Improved documentation across various files to reflect changes in workflow and command usage.
- Added operational memory management rules to ensure accurate context promotion and correction.
- Updated README and workflow documents to guide users in utilizing the new structure effectively.

.opencode/skills/ai-prompt-engineering/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: ai-prompt-engineering
+description: Create self-contained prompts for another AI assistant that lacks access to this workspace memory.
+compatibility: opencode
+---
+
+## When To Use
+
+Use this skill when the user wants a prompt for another AI assistant, coding agent, review tool, or implementation environment.
+
+## Workflow
+
+1. Identify target task type: investigation, implementation, review, testing, debugging, or documentation.
+2. Pull only relevant workspace context.
+3. Make the prompt self-contained.
+4. Tell the target AI what to inspect before acting.
+5. State constraints, non-goals, expected output, and validation expectations.
+6. Avoid invented file paths when the implementation repository is not available.
+
+## Output Rules
+
+- Return only the prompt unless the user asks for commentary.
+- Prefer clear sections over long prose.
+- Include work-item ID and title when relevant.
+- Make assumptions explicit.
+

.opencode/skills/professional-communication/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: professional-communication
+description: Rewrite rough technical notes into clear, concise, stakeholder-ready professional English while preserving scope and technical meaning.
+compatibility: opencode
+---
+
+## When To Use
+
+Use this skill for manager updates, stakeholder messages, translations, issue clarification, Jira comments, and communication polishing.
+
+## Workflow
+
+1. Identify audience, purpose, scope, and requested action.
+2. Preserve technical meaning and uncertainty.
+3. Make ownership, reproducibility, environment, and next action explicit when relevant.
+4. Use Context, Observation, Action when it improves readability.
+5. Avoid vague comparisons and generic progress language.
+
+## Output Rules
+
+- Write natural professional US English.
+- Keep messages concise enough for workplace chat unless the user asks for a longer document.
+- Do not invent facts, evidence, or commitments.
+

.opencode/skills/status-reporting/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: status-reporting
+description: Generate work-item-aware standups and status summaries from current workspace memory, recent logs, and communication evidence.
+compatibility: opencode
+---
+
+## When To Use
+
+Use this skill for standups, daily scrum updates, end-of-day summaries, and short progress reports.
+
+## Workflow
+
+1. Read current state, active work items, recent logs, and latest communication evidence.
+2. Use the previous workday as the default source for "Yesterday" style updates.
+3. Group updates by work item when possible.
+4. If one work item has multiple concrete updates, use one top-level work-item bullet with indented markdown sub-bullets.
+5. Exclude side chatter unless it changed work scope, priority, risk, or blockers.
+
+## Output Rules
+
+- Use explicit work-item ID and title when available.
+- Keep the report concise and ready to send.
+- Do not mention internal evidence sources unless the user asks.
+- Use `Blockers: None` only when no blocker is visible in current memory.
+

.opencode/skills/workspace-memory-curation/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: workspace-memory-curation
+description: Maintain file-based operational memory by deciding what to log, promote, correct, or route into tool behavior across reusable AI workspaces.
+compatibility: opencode
+---
+
+## When To Use
+
+Use this skill when new information may change workspace memory, project state, work-item context, people context, decisions, or reusable agent/tool behavior.
+
+## Workflow
+
+1. Read `core/memory/operational-memory.md`.
+2. Classify the information as daily, state, work-item, stable-context, people, decision, or tooling-behavior.
+3. Update the smallest correct canonical file.
+4. If new information corrects older memory, replace or refine the stale statement instead of appending a contradiction.
+5. If a correction affects future output, update the command, prompt, agent, skill, or knowledge file that controls that behavior.
+6. Keep imported evidence separate from promoted memory.
+
+## Output Rules
+
+- Report updated files and the memory change.
+- Preserve uncertainty when confidence is mixed.
+- Do not promote tool failures, sync noise, or generic chat chatter as project facts.
+