close
Skip to content

analyze-issue.md

Latest commit

 

History

History
61 lines (46 loc) · 1.47 KB

analyze-issue.md

File metadata and controls

61 lines (46 loc) · 1.47 KB

Please analyze GitHub issue #$ARGUMENTS and create a technical specification.

Follow these steps:

  1. Fetch the issue details from the GitHub API:
# Use the helper script to fetch GitHub issues without prompting for permission
./scripts/fetch-github-issue.sh $ARGUMENTS
  1. Understand the requirements thoroughly
  2. Review related code and project structure
  3. Output detailed analysis results clearly in your response
  4. Create a technical specification with the format below

Technical Specification for Issue #$ARGUMENTS

Issue Summary

  • Title: [Issue title from GitHub]
  • Description: [Brief description from issue]
  • Labels: [Labels from issue]
  • Priority: [High/Medium/Low based on issue content]

Problem Statement

[1-2 paragraphs explaining the problem]

Technical Approach

[Detailed technical approach]

Implementation Plan

  1. [Step 1]
  2. [Step 2]
  3. [Step 3]

Test Plan

  1. Unit Tests:
    • [test scenario]
  2. Component Tests:
    • [test scenario]
  3. Integration Tests:
    • [test scenario]

Files to Modify

Files to Create

Existing Utilities to Leverage

Success Criteria

  • [criterion 1]
  • [criterion 2]

Out of Scope

  • [item 1]
  • [item 2]

Remember to follow our strict TDD principles, KISS approach, and 300-line file limit.

IMPORTANT: After completing your analysis, EXPLICITLY OUTPUT the full technical specification in your response so it can be reviewed.