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.
This commit is contained in:
2026-04-16 08:35:53 -06:00
parent 1f57597ca3
commit 8026da5719
41 changed files with 1131 additions and 42 deletions

View File

@@ -10,7 +10,7 @@ Keep this workspace aligned with work happening on another machine so AI output
1. Capture the main tasks worked on during the day.
2. Record key debugging findings and open questions.
3. Copy relevant Mattermost communication into the daily log as summarized notes.
3. Sync or copy relevant communication evidence into the inbox or daily log as summarized notes.
4. Update `ai/state/current.md` if priorities or concerns changed.
5. Add any stable learning to `ai/context/` or `knowledge/`.
5. Add any stable learning to `ai/context/` or `knowledge/`; if the learning changes reusable workspace behavior, update `core/`, commands, prompts, skills, or agent rules too.
6. Before asking AI for a standup or manager update, confirm the log reflects the latest state.

View File

@@ -10,15 +10,15 @@ Use OpenCode as the daily AI entry point for this workspace without losing proje
1. Open this repository as its own VS Code workspace.
2. Run `opencode` from the integrated terminal at the repository root.
3. Use the `fidelity` primary agent when available.
3. Use the `fidelity` primary agent for this project profile, or the generic `workspace` agent for reusable profile work.
4. Let project-level config load from `AGENTS.md`, `opencode.json`, `.opencode/commands/`, and `.opencode/plugins/`.
---
## Recommended Daily Sequence
1. Run `/fidelity-context` at the start of the day.
2. If Mattermost sync is configured, let the inbox refresh automatically or run `/mattermost-sync`.
1. Run `/workspace-context` at the start of the day, or `/fidelity-context` when you want the Fidelity alias.
2. If live communication sync is configured, let the inbox refresh automatically or run `/communication-sync`.
3. When new work happens on the main development machine, run `/sync-context ...` or `/log-note ...`.
4. When you need a supervisor update, run `/manager-update ...`.
5. When you need polished English for Mattermost, run `/translate ...`.
@@ -30,9 +30,9 @@ Use OpenCode as the daily AI entry point for this workspace without losing proje
- Project instructions load automatically from `opencode.json`.
- Root rules also load automatically from `AGENTS.md`.
- The main context command reads the stable workspace files plus today's log.
- The main context command reads the reusable `core/`, active profile, stable workspace files, and today's log.
- Stable context is split by systems, workstreams, process, people, and decisions so the agent can pull the right layer instead of overloading one project file.
- Mattermost context can be refreshed into `ai/inbox/` using your existing local sync script.
- Live communication context can be refreshed into `ai/inbox/` using the configured connector.
- Direct prompts are also treated as memory opportunities, so the agent can update workspace context during normal conversation.
- Daily updates go back into the workspace, so later prompts inherit better context.
- The local compaction plugin helps preserve the most important workspace context during long sessions.