microsoft / microsoft/work-iq

Unrealiable Summary by Date

Open
#130 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PowerShell
Stars
1k
Forks
132
Avg merge
5d 19h
Merged PRs (30d)
6

Description

I am stumped by inconsistency in how work-iq is summarizing when asked to stick to a specific date.

For the past 2 days I have been experimenting with the following type of prompt in Copilot (with work-iq plugin):

PROMPT: List ALL projects, research topics, and substantive work I was actively involved in on 2026-04-26. Look at my meetings (including clusters of separate meetings with similar names), emails, any documents, and Teams messages. Do not include projects where I didn't actively participate by asking a question, writing a doc or responding to an email. For each project or topic, give: Project/topic name Detailed description using file summaries, transcripts etc. if available. People I collaborated with
Be thorough and include even small or one-off projects. It's better to over-include than to miss something. Just list the facts, no commentary.

It worked pretty well and produced a nice summaries of projects. But now the prompt is failing for me and at least 2/3 of the projects are now weeks later (one is from May 26, a month later). I tried a more stringent prompt and got the same result:

PROMPT V2: List ALL projects, research topics, and substantive work I was actively involved in on 2026-04-26. Look at my meetings (including clusters of separate meetings with similar names), emails, any documents, and Teams messages. Do not include projects where I didn't actively participate on 2026-04-26 by taking an action on 2026-04-26 such as asking a question, writing a doc or responding to an email or interacting on Teams. (...)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the two prompts from issue #130 through the Work IQ plugin, using the specified date and the listed meetings, emails, documents, and Teams messages. Compare the returned project dates with the requested date; done means the summary consistently includes only substantive activity from that date and does not pull projects from later weeks.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.