40 lines
1.7 KiB
Markdown
40 lines
1.7 KiB
Markdown
# OpenCode Entry Workflow
|
|
|
|
## Goal
|
|
|
|
Use OpenCode as the daily AI entry point for this workspace without losing project context.
|
|
|
|
---
|
|
|
|
## Setup
|
|
|
|
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.
|
|
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`.
|
|
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 ...`.
|
|
6. When you need a standup, run `/standup`.
|
|
|
|
---
|
|
|
|
## Why This Works
|
|
|
|
- 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.
|
|
- 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.
|
|
- 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.
|
|
- This reduces reliance on fragile session memory.
|