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

@@ -0,0 +1,88 @@
# Create A Project Profile
Use this checklist when adapting the workspace core for a new project.
---
## 1. Create The Profile
Create:
```text
profiles/<project>/profile.md
profiles/<project>/README.md
```
The profile should declare:
- project name
- workspace purpose
- primary audience
- communication sources
- ticket/work-item system
- manager or stakeholder mapping
- active context files
- enabled commands
- enabled skills
---
## 2. Configure Context
Create or update:
```text
ai/context/project.md
ai/context/index.md
ai/context/process/
ai/context/people/
ai/state/current.md
ai/state/work-items.md
ai/work-items/index.md
```
Keep project-specific facts out of `core/`.
---
## 3. Configure Integrations
Use generic variables first:
```text
AIW_PROJECT_PROFILE=<project>
AIW_CHANNEL_PREFIX=<project-or-team-prefix>
AIW_MATTERMOST_SYNC_CMD=<optional custom command>
AIW_SLACK_EXPORT_PATH=<optional archive path>
```
Connector secrets belong in ignored `.env` files, not in profile files.
---
## 4. Configure Commands And Skills
Start with generic commands:
- `/workspace-context`
- `/communication-sync`
- `/archive-import`
- `/standup`
- `/manager-update`
- `/translate`
- `/ai-prompt`
Add project-specific aliases only when they reduce friction.
---
## 5. Validate
Before using the workspace for real work:
- confirm `opencode.json` is valid JSON
- confirm the profile has no secrets
- run a communication sync with test channels or a dry sample
- generate one standup from sample context
- verify that imported evidence and promoted memory stay separate