feedback: PRD Parsing Fails with Formatting Issues - Anthropic API error during object generation #476

New issue

Open

opened 2025-10-14 15:57:10 -06:00 by navan · 0 comments

navan commented

2025-10-14 15:57:10 -06:00

Owner

Originally created by @rcaos on 6/18/2025

Hi folks! I hope this feedback saves you valuable debugging time and helps streamline your development process.

Feedback Summary

parse-prd command fails with error:

Error: Anthropic API error during object generation: No object generated: response did not match schema.
Version: 0.17.0

When PRDs contain formatting elements like code blocks, inline code with backticks, or complex formatting. Error message provides no indication that formatting is the root cause.

User Context

I'm a new user writing detailed PRDs with enthusiasm to be comprehensive. Included coding examples, inline code references, and complex formatting to thoroughly document technical requirements. Expected the parser to handle standard markdown formatting.

I'm using task-master with Cursor as an MCP

User Impact

Time Lost: Spent hours debugging what appeared to be an API or configuration issue
Error message doesn't hint at formatting being the problem
Frustration: Had to systematically compare with working PRDs and remove elements to identify the cause
Discovery Process: Only found solution by trial and error, not through clear guidance

Suggestions

Improve Error Messages: Provide more specific error messages that hint at formatting issues
Pre-validation: Add formatting validation that identifies problematic elements before API calls
Documentation Prominence: Make formatting requirements more visible in main docs.
Examples: Show both ✅ good and ❌ bad formatting examples in primary documentation

Relevant Screenshots or Examples

Error Message:

Anthropic API error during object generation: No object generated: response did not match schema.

Additional Notes

This issue could save future users significant debugging time. The formatting requirements exist in taskmaster.mdc but aren't prominent enough for new users who naturally want to include technical details in their PRDs. Consider this a UX improvement opportunity rather than a bug fix.

I added to my cursor rule (taskmaster.mdc):

### PRD Formatting Requirements (CRITICAL)

**🚨 FATAL: Formatting Issues That Break Parsing**

These formatting patterns will cause `"Anthropic API error: response did not match schema"` failures:

**❌ XML-Like Tags:**
```markdown
<context>
Content here
</context>


**❌ Non-ASCII Characters:**
- Arrow symbols: `→` (use "then" instead)  
- Special unicode characters
- Smart quotes: `""` (use regular quotes: `""`)

**❌ Code Blocks:**
```markdown
```swift
// Code examples in PRDs break parsing


**❌ Inline Code with Backticks:**
- `UserDefaults.standard`
- `@DependencyClient` 
- Any text wrapped in backticks

**❌ Complex Nested Formatting:**
- Bold text within lists that contain code
- Multiple levels of nested formatting
- Mixed formatting patterns

**✅ SAFE: Standard Markdown That Works**
Use simple markdown formatting without code blocks or inline code.

*Originally created by @rcaos on 6/18/2025* Hi folks! I hope this feedback saves you valuable debugging time and helps streamline your development process. ### Feedback Summary `parse-prd` command fails with error: ``` Error: Anthropic API error during object generation: No object generated: response did not match schema. Version: 0.17.0 ``` When PRDs contain formatting elements like code blocks, inline code with backticks, or complex formatting. Error message provides no indication that formatting is the root cause. ### User Context I'm a new user writing detailed PRDs with enthusiasm to be comprehensive. Included coding examples, inline code references, and complex formatting to thoroughly document technical requirements. Expected the parser to handle standard markdown formatting. I'm using task-master with Cursor as an MCP ### User Impact - **Time Lost**: Spent hours debugging what appeared to be an API or configuration issue - Error message doesn't hint at formatting being the problem - **Frustration**: Had to systematically compare with working PRDs and remove elements to identify the cause - **Discovery Process**: Only found solution by trial and error, not through clear guidance ### Suggestions 1. **Improve Error Messages**: Provide more specific error messages that hint at formatting issues 2. **Pre-validation**: Add formatting validation that identifies problematic elements before API calls 3. **Documentation Prominence**: Make formatting requirements more visible in main docs. 4. **Examples**: Show both ✅ good and ❌ bad formatting examples in primary documentation ### Relevant Screenshots or Examples **Error Message:** ``` Anthropic API error during object generation: No object generated: response did not match schema. ``` ### Additional Notes This issue could save future users significant debugging time. The formatting requirements exist in taskmaster.mdc but aren't prominent enough for new users who naturally want to include technical details in their PRDs. Consider this a UX improvement opportunity rather than a bug fix. ### I added to my cursor rule (taskmaster.mdc): ``` ### PRD Formatting Requirements (CRITICAL) **🚨 FATAL: Formatting Issues That Break Parsing** These formatting patterns will cause `"Anthropic API error: response did not match schema"` failures: **❌ XML-Like Tags:** ```markdown <context> Content here </context> **❌ Non-ASCII Characters:** - Arrow symbols: `→` (use "then" instead) - Special unicode characters - Smart quotes: `""` (use regular quotes: `""`) **❌ Code Blocks:** ```markdown ```swift // Code examples in PRDs break parsing **❌ Inline Code with Backticks:** - `UserDefaults.standard` - `@DependencyClient` - Any text wrapped in backticks **❌ Complex Nested Formatting:** - Bold text within lists that contain code - Multiple levels of nested formatting - Mixed formatting patterns **✅ SAFE: Standard Markdown That Works** Use simple markdown formatting without code blocks or inline code. ```