Wrong

Wrong — Reset and Re-evaluate

The current approach isn't working as expected. Step back and re-examine the problem from the beginning.

Workflow

Step 1: Re-analyze the Core Problem

State the problem in clear, simple terms. What exactly are we trying to solve?

Step 2: Identify Missing Context

Determine what additional information is needed about:

• The existing codebase and its patterns
• Performance requirements or constraints
• Integration points with other systems
• Expected usage patterns or scale
• Any domain-specific requirements not yet mentioned

Step 3: Propose Fresh Approaches

Suggest 2-3 alternative solutions that:

• Follow project best practices and idioms
• Match the existing code's style and architecture patterns
• Are maintainable and testable
• Solve the exact problem without over-engineering
• Don't use shortcuts or hacks

Step 4: Explain Trade-offs

For each proposed approach, briefly explain:

• Why this approach fits the problem
• What the main benefits and drawbacks are
• How it integrates with the existing codebase

Step 5: Recommend the Best Path Forward

Which approach is most appropriate and why?

Requirements

• Solution must be production-ready, not a proof of concept
• Code should be idiomatic and follow established patterns
• Include comprehensive tests with edge cases
• Provide complete, runnable code with no placeholders
• Ensure the solution is maintainable

Ask clarifying questions before proceeding.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.