What problem does it solve? Operators and non-technical stakeholders often ask "what happened, what works, what was decided, what remains open?" but the answers are buried in technical AOPS records like PM tasks, memory checkpoints, and discussion sessions. This Skill translates that raw project data into a clear, plain-language status brief. ## Core Features & Use Cases - Structured Read Order: Queries PM views (dashboard, task, sprint, digest), then memory records (closeout, decisions, checkpoints), then discussion sessions in a defined priority. - Technical-to-Plain Translation: Converts jargon like cwd, threadId, and closeout into operator-friendly terms such as "working folder" and "the work was closed with approval". - Standardized Output Format: Produces short Turkish bullet sections covering overall status, user-visible changes, decisions, remaining items, and sources. - Use Case: An operator asks "what did we do earlier on the payment feature?" The agent follows the read order, gathers the relevant task and memory records, and returns a concise non-technical summary. ## Quick Start Ask the agent to summarize what happened on a specific AOPS task or sprint in plain language for an operator status update.
