microsoft / microsoft/vscode-dotnettools
[P0][Tier 3] Add a discovery-before-generation step to agent instructions/skills
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Tier 3 — Workflow adoption · Priority: P0
Gap
Tier 1 conventions are well documented, but the agent working loop does not have an explicit discovery step that reads nearby code and conventions before writing new code. This is distinct from documenting conventions — it ensures the loop actually consults them at the right moment (Tier 1 vs Tier 3 scope note).
Investment
- Add a discovery-before-generation step to agent instructions/skills: locate nearby patterns (via bluebird semantic search /
csdevkit-cliLSP) before generating.
Acceptance criteria
- Instructions/skills require a discovery pass before generation.
- The step names the available code-intelligence tools to use.
Part of epic #3273
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the agent instructions and skills referenced by the issue, then read epic #3273 for scope and context. Check how bluebird semantic search and csdevkit-cli LSP are named elsewhere. Done means the instructions require discovery before generation and identify both available code-intelligence tools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- developer-experience, documentation, tooling
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100