Skip to content

Instantly share code, notes, and snippets.

@lifeodyssey
Created December 16, 2025 04:13
Show Gist options
  • Select an option

  • Save lifeodyssey/99005b0725bf5c88d84bbc55332ff9f8 to your computer and use it in GitHub Desktop.

Select an option

Save lifeodyssey/99005b0725bf5c88d84bbc55332ff9f8 to your computer and use it in GitHub Desktop.
explore solution prompt example

Context

I am working on [TICKET_ID]: [Brief ticket description]

Requirements

Please read the requirements document at: [path/to/requirements.md]

Task

Explore the codebase and propose at least 3 different approaches to solve this problem.

For each approach, please document:

  • Overview: High-level description of the approach

  • Implementation details: Key technical decisions and what needs to change

  • Pros: What are the advantages of this approach?

  • Cons: What are the disadvantages or limitations?

  • Tradeoffs: What compromises are we making with this approach?

  • Estimated complexity: Low/Medium/High

  • Output Format

Identify current problem and summarize first, and then use websearch to get the up to date best pracitce for this problem. tody is 2025-12-08.

Follow the official doc: https://exmaple.com to geneate the solution.

when need to introduce new depdendency, check github/npm/maven for the newest version and select the one that still in maintenance.

Please create a markdown file at: claude-context/[ticket-id]-approaches.md

Structure it like this:

Solution Approaches for [TICKET_ID]

Approach 1: [Name]

  • Overview: ...
  • Implementation details: ...
  • Pros: ...
  • Cons: ...
  • Tradeoffs: ...
  • Estimated complexity: ...

Approach 2: [Name]

...

Approach 3: [Name]

...

Recommendation

If you have an initial recommendation based on the codebase exploration, note it here (but the final decision will be made in the next step). Additional Guidance Consider both incremental changes and more radical refactorings Think about maintainability, testability, and future extensibility Consider performance implications if relevant Look at similar patterns already used in the codebase

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment