- 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.
555 B
555 B
Communication Rules
Purpose
These rules keep standups, Jira notes, and Mattermost messages aligned with the actual state of the work.
Rules
- Prefer explicit scope over short vague statements
- Always mention auth state when it changes reproducibility
- Separate external report from regression
- Say whether behavior was confirmed in main when that comparison exists
- End with the next action when writing status updates
Avoid
- "same behavior"
- "looks good"
- "seems fixed"
- "working now"
Use concrete statements instead.