chore: remove dead microsoft-docs tools from the user-level spec-writer agent

Open
  • Is something wrong?
#430 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
1/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp
Domain
tooling

Research direction

The issue targets ~/.claude/agents/spec-writer.md, a file on the owner's machine, and recommends removing the two unavailable Microsoft Docs tool names. Start by checking the configured tools and the disabled plugin setting; done means the agent lists only tools that exist and a spec-writer invocation still returns a brief. This cannot be contributed through a repository change.

Written by the indexing model from the issue text.

Description

tech-debt

Found while auditing the agents for #400. This is a fix to a file on the owner's machine, not a change in this repo, so there is no PR.

Problem

The user-level agent ~/.claude/agents/spec-writer.md lists two tools from a plugin that is turned off:

tools: Read, Grep, Glob, SendMessage, mcp__plugin_microsoft-docs_microsoft-learn__microsoft_docs_search, mcp__plugin_microsoft-docs_microsoft-learn__microsoft_docs_fetch

~/.claude/settings.json has "microsoft-docs@claude-plugins-official": false, so the two mcp__plugin_microsoft-docs_* tools do not exist. The agent still works, because Claude skips tools it cannot find, but it cannot look up Microsoft documentation, and it looks like it can.

SendMessage in the same list is also unused once the agent-teams flag is removed (#400, piece 2). It is harmless.

Options

  1. Remove the two dead tool names. Simplest. spec-writer then works from the code and the researcher findings only.
  2. Point them at the Microsoft Learn connector already available in the account (mcp__claude_ai_Microsoft_Learn__microsoft_docs_search and ..._microsoft_docs_fetch). Keeps the lookup ability, and depends on the connector staying connected.
  3. Turn the microsoft-docs plugin back on. Restores the original names, but brings the plugin back for every session.

Recommended: option 1, because #400 drops dotnet-advisor, the only other thing that relied on Microsoft documentation. Decide when you pick this up.

Acceptance criteria

  1. ~/.claude/agents/spec-writer.md lists no tool that does not exist on this machine.
  2. A spec-writer invocation from feature-factory still returns a brief.

Out of scope

The other user-level agents (story-writer, codebase-researcher) and any change to what spec-writer writes. Per #400, user-level agents are never copied into this repo.

Dominant language
C#
Stars
1
Forks
0
Avg merge
2h 2m
Merged PRs (30d)
98

Getting set up

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.

More from nevridge/TaskFlow

All issues in nevridge/TaskFlow

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.