- Introduced a primary agent for the Fidelity AI Workspace to maintain context and support daily engineering tasks. - Created commands for loading workspace context, drafting updates for Jeff, and logging daily notes. - Implemented translation and standup generation commands to enhance communication clarity. - Developed a compaction plugin to preserve essential workspace context during sessions. - Established a structured approach for managing project knowledge, communication rules, and decision-making processes. - Updated README and project structure to reflect new workflows and usage guidelines.
41 lines
728 B
Markdown
41 lines
728 B
Markdown
# Jeff
|
|
|
|
## Role
|
|
|
|
Direct supervisor.
|
|
|
|
---
|
|
|
|
## Communication Requirements
|
|
|
|
- Native US English
|
|
- Prefers clear, concise updates
|
|
- Needs accurate scope, not vague reassurance
|
|
- Should be informed of meaningful progress from this machine through Mattermost
|
|
|
|
---
|
|
|
|
## What Good Updates Include
|
|
|
|
1. Context
|
|
2. Observation
|
|
3. Action
|
|
|
|
Good updates usually clarify:
|
|
|
|
- what issue or task is being discussed
|
|
- whether the behavior is reproducible
|
|
- whether auth state matters
|
|
- whether this looks like an external issue or a regression
|
|
- what the next step is
|
|
|
|
---
|
|
|
|
## AI Usage
|
|
|
|
AI should help:
|
|
|
|
- translate rough Spanish notes into natural US English
|
|
- tighten wording before sending
|
|
- remove ambiguity without changing technical meaning
|