david.delagneau
8026da5719
- 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.
2.0 KiB
2.0 KiB
description
| description |
|---|
| Sync Mattermost context and automatically promote high-confidence project memory |
Use the configured Mattermost sync command to fetch fresh communication context and maintain workspace memory automatically.
Preferred command sources:
AIW_MATTERMOST_SYNC_CMD- compatibility fallback:
FIDELITY_MATTERMOST_SYNC_CMD - fallback:
bash scripts/mattermost/sync.sh
Run the command and use its output as fresh communication context:
!if [ -n "$AIW_MATTERMOST_SYNC_CMD" ]; then bash -lc "$AIW_MATTERMOST_SYNC_CMD"; elif [ -n "$FIDELITY_MATTERMOST_SYNC_CMD" ]; then bash -lc "$FIDELITY_MATTERMOST_SYNC_CMD"; elif [ -f scripts/mattermost/sync.sh ]; then bash scripts/mattermost/sync.sh; else echo "No Mattermost sync command is configured."; fi
Use this command implicitly when the user asks for the latest or last Mattermost message, especially messages from Jeff or the current manager.
Then:
- if the command fails, stop there and do not edit any workspace files
- use
ai/inbox/mattermost-latest.mdif it exists and is non-empty - otherwise use
scripts/mattermost/generated/mattermost_context.jsonlif it exists and is non-empty - apply the memory promotion rules from
knowledge/memory-promotion-rules.md - treat Mattermost output as live communication evidence; the agent decides what becomes promoted memory
- automatically promote explicit, project-relevant, high-confidence facts
- default destination is
ai/logs/$(date +%F).md - update
ai/state/current.mdonly for facts that materially change the current work window - update
ai/work-items/*.mdfor explicit Jira IDs, approved titles, points, scope, and status notes - keep
ai/state/work-items.mdaligned as the compact summary of active ticket files - do not write tooling noise, sync status, or generic chat chatter into project memory
- if a fact is ambiguous, skip it rather than asking the user what to do
Return:
- What was synchronized
- Which files were updated
- Which facts were promoted or intentionally skipped