DavidWells / DavidWells/analytics

Planning

Open
#485 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auto-generated ci-cd claude-code documentation
Dominant language
JavaScript
Stars
2.7k
Forks
267
PR merge metrics
No merged PRs in 30d

Description

Based on what you know about the repository and open issues and PRs, what would you propose that we tackle next? @claude

Additional instructions

Propose Next Development Task

Your next task: Identify and recommend the most logical next development task based on the current project state and goals.

File Existence Check

Check for key documentation files first:

ls . docs

Use these results to inform your analysis.

To achieve this, follow these thought processes:

  1. Understand Context:

    • Review relevant project documentation (e.g., files in docs/, README.md).
    • Analyze current project requirements. If a .cursor/rules/req-task.mdc (or similar) file exists and is relevant, consult it for specific task requirements or context.
    • Consider the most recent actions, discussions, or completed work in the project.
  2. Identify Potential Tasks:

    • Based on your understanding, brainstorm a list of 3-5 potential next tasks that would advance the project.
  3. Evaluate and Recommend:

    • From your list, select the single most logical and impactful task to undertake next.
    • Clearly state your recommendation.
    • Provide concise reasoning for your choice, explaining why it's the most appropriate next step (e.g., dependency for other tasks, highest priority, unblocks other work).

Output Expectation:

Your response should clearly state:

  1. Recommended Next Task: [Describe the task]
  2. Reasoning: [Explain why this task is recommended]
  3. (Optional) Alternative Tasks: [Briefly list 1-2 other potential tasks considered]

REMEMBER: Your goal is to provide a well-reasoned recommendation for the single most impactful next development task.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running ls . docs, then read the available documentation and README.md, along with any relevant .cursor/rules/req-task.mdc file. Review open issues, pull requests, recent discussions, and completed work before comparing several candidate tasks. Done means providing one prioritized next development task with concise reasoning and, optionally, alternatives.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
analytics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.