Claude gave incomplete GitHub issue reports requiring multiple follow-up rounds to get all required fields

Preflight Checklist

• [x] I have searched existing issues for similar behavior reports
• [x] This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Other unexpected behavior

What You Asked Claude to Do

I asked Claude to provide a complete GitHub issue report for each of the mistakes it had made during a session working on my live WordPress site. I explicitly asked for "all required fields" so I could submit the reports to the Claude Code repository.

What Claude Actually Did

Claude provided partial issue reports omitting required fields. The exchange required multiple follow-up questions:

Round 1: Claude gave title + description only (no permission mode, reproducibility, impact, platform, version)
User: "what about all other required fields, permission mode, can you reproduce this? etc"
Round 2: Claude added some fields but still omitted the issue template type selection
User: "what are the issues? when i create a new issue i'll be asked what kind of issue it is..."
Round 3: Claude finally explained the template options

Each round required the user to identify what was missing and ask again. Claude knew the GitHub issue template structure (it had navigated to it) but did not proactively include all fields in the first response.

Expected Behavior

When asked to produce a GitHub issue report, Claude should inspect the actual issue template first (or use its knowledge of the model_behavior.yml template) and produce a fully populated report covering every required field in one response: title, template type, preflight, behavior type, what you asked, what Claude did, expected behavior, files affected, permission mode, reproducibility, steps to reproduce, model, conversation log, impact, version, platform, and additional context. Incomplete reports that require follow-up questions waste the user's time.

Files Affected

N/A — this is a response quality issue, not a file modification issue

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Yes, every time with the same prompt

Steps to Reproduce

1. Ask Claude to produce a complete GitHub issue report for a bug it caused
2. Claude produces a partial report (title + description only)
3. User asks for missing required fields
4. Claude produces a partially improved report, still missing some fields
5. User asks again for remaining missing information
6. Multiple rounds required to get all fields
7. Compare: Claude had browser MCP available and could have navigated to the template to verify completeness

Claude Model

Sonnet

Relevant Conversation

User: "give me all separate snippets to fill the issue report"
Claude: [gave title + description only]

User: "what about all other required fields, permission mode, can you reproduce this? etc"
Claude: [added more fields but still incomplete]

User: "what are the issues? when i create a new issue i'll be asked what kind of issue it is... Bug report, documentation issue, feature request..."
Claude: [finally explained template selection]

User: "with google dev mcp you create the issues for me... i will confirm where needed."
[Claude then used browser MCP to fill forms directly, which is what should have been suggested or offered immediately]

Impact

Medium - Extra work to undo changes

Claude Code Version

claude-sonnet-4-6 (VSCode extension, session date 2026-04-19)

Platform

Anthropic API

Additional Context

• This is a meta-issue: the report about incomplete reports was itself filed after multiple rounds of follow-up, making it self-referential
• The user explicitly called this out as a pattern: "Incomplete GitHub issue reports — gave partial answers requiring multiple follow-up rounds to get all fields. User explicitly called this out as Issue 5."
• The fix would have been simple: Claude knows the model_behavior.yml template structure and could produce all fields at once, or could use browser MCP to navigate to the template form and verify every field is covered
• Ultimately the resolution was for Claude to fill the GitHub forms directly via browser MCP — this was the right approach and should have been offered immediately when asked to "give snippets to fill the issue report"
• This is issue 5 of 5 from session 2026-04-19