microsoft / microsoft/devsquad-copilot
[spike] Managing large doc/ADR sets and stale context in implementation agents
Open
Nobody has claimed this yet.
question
- Dominant language
- No language data
- Stars
- 44
- Forks
- 10
- Avg merge
- 6h 49m
- Merged PRs (30d)
- 1
Description
Brainstorming and investigation, not yet an actionable task.
Problem
Consumers experience challenges managing extensive documentation and multiple ADRs while using DevSquad Copilot. We are observing how implementation agents handle outdated context such as superseded rules or new findings.
Goal of this spike
- Characterize how agents currently handle stale or superseded context.
- Identify options for surfacing superseded ADRs/rules and reconciling new findings.
- Produce a recommendation (possibly one or more follow-up issues or ADRs).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by characterizing how implementation agents handle the documentation and ADR context described in the issue, then compare options for stale or superseded material. Done means a recommendation with identified follow-up issues or ADRs.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100