feat: Update behavior rules and documentation for workspace maintenance and flow references
This commit is contained in:
@@ -13,6 +13,7 @@ This repository is a support workspace, not the implementation repository.
|
||||
- manager update drafts
|
||||
- stable project knowledge
|
||||
- debugging summaries
|
||||
- reusable command, prompt, skill, and agent rules that make the workspace behave consistently
|
||||
|
||||
---
|
||||
|
||||
@@ -21,3 +22,17 @@ This repository is a support workspace, not the implementation repository.
|
||||
- product source code
|
||||
- assumptions about code changes not yet verified
|
||||
- statements that imply work was executed from this machine unless explicitly true
|
||||
|
||||
---
|
||||
|
||||
## Operational Surface
|
||||
|
||||
When the user corrects a recurring behavior, the workspace should update the file that controls that behavior:
|
||||
|
||||
- `.opencode/commands/` for slash commands
|
||||
- `prompts/` for reusable drafting templates
|
||||
- `.opencode/agents/` and `ai/AGENTS.md` for default agent behavior
|
||||
- `.opencode/skills/` for specialized workflows
|
||||
- `knowledge/` and `ai/context/process/` for durable process rules
|
||||
|
||||
Daily logs can preserve evidence, but they should not be the only place where a reusable behavior rule lives.
|
||||
|
||||
Reference in New Issue
Block a user