[BUG] Claude code asks to read skill prompt files

Resolved 💬 3 comments Opened May 17, 2026 by CSchulz Closed May 18, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

I am using superpowers skill to run sub agent development and I have recognized that claude asks to read the prompt files.

⏺ Skill(superpowers:subagent-driven-development)
  ⎿  Successfully loaded skill

                                                                                                                                         02:55 PM claude-sonnet-4-6
⏺ Let me read the prompt templates before starting.

⏺ Read(.../.claude/plugins/cache/claude-plugins-official/superpowers/5.1.0/skills/implementer-prompt.md)

⏺ Read(.../.claude/plugins/cache/claude-plugins-official/superpowers/5.1.0/skills/spec-reviewer-prompt.md)

⏺ Read(.../.claude/plugins/cache/claude-plugins-official/superpowers/5.1.0/skills/code-quality-reviewer-prompt.md)

 Read file

  Read(~/.claude/plugins/cache/claude-plugins-official/superpowers/5.1.0/skills/implementer-prompt.md)

 Do you want to proceed?
 ❯ 1. Yes
   2. Yes, allow reading from skills/ during this session
   3. No

What Should Happen?

It should read the prompt files without asking, because it already loaded the skill.

Error Messages/Logs

Steps to Reproduce

  1. Create some code review instructions which needs to be fixed containing something like this at the end:
Want me to implement the body-parsing approach?
  1. Answer with Yes, use /superpowers:subagent-driven-development

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.133 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗