feat: Add Fidelity workspace agent and context management commands

- 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.

prompts/.gitkeep

@@ -0,0 +1 @@
+

prompts/manager-update.md

@@ -0,0 +1,14 @@
+# Manager Update Prompt
+
+Use the current state, today's log, and `ai/context/people/jeff.md`.
+
+Draft a Mattermost update for Jeff in concise US English.
+
+Requirements:
+
+- Structure around Context, Observation, and Action
+- Make scope explicit
+- Clarify whether the issue is external behavior or regression
+- Mention auth state when relevant
+- Preserve the original technical meaning
+- Keep the message direct and short

prompts/mattermost-translation.md

@@ -0,0 +1,16 @@
+# Mattermost Translation Prompt
+
+Translate rough engineering notes into natural US English for Mattermost.
+
+Requirements:
+
+- Preserve exact technical meaning
+- Remove ambiguity
+- Prefer concise wording
+- Keep the tone professional and direct
+- If the draft lacks context, infer only from workspace files and do not invent facts
+
+Output:
+
+1. Clean message
+2. Short note listing any assumptions made

prompts/standup.md

@@ -0,0 +1,25 @@
+# Standup Prompt
+
+Use the latest files in `ai/state/current.md`, `ai/context/project.md`, `ai/context/people/jeff.md`, and today's log.
+
+Generate a standup update for an iOS engineer working on Fidelity.
+
+Requirements:
+
+- Use the most recent context only
+- Be specific about what was worked on
+- Mention debugging findings only if they materially changed understanding
+- Clarify auth-dependent behavior when relevant
+- Avoid vague phrases and generic progress language
+- Keep it concise and ready to send
+
+Format:
+
+Yesterday:
+- ...
+
+Today:
+- ...
+
+Blockers:
+- ...