propose simple playbook structure for comment

[jgumbley]

Important

Adds a draft playbook for the support team in support/PLAYBOOK.md, detailing mission, onboarding, support management, issue maintenance, and documentation enhancement.

• New Document:
  • Adds support/PLAYBOOK.md as a draft playbook for the support team.
• Mission & Prioritization:
  • Defines primary mission to help users with Roo Code.
  • Proposes using GitHub issues for tracking priorities.
• Onboarding:
  • Lists steps for new team members, including posting availability and forking the documentation repo.
• Support Thread Management:
  • Details management of Discord and Reddit support threads, including tagging and monitoring.
• Issue Maintenance:
  • Outlines regular review and validation of GitHub issues.
• Documentation Enhancement:
  • Emphasizes the importance of documentation improvement and outlines pending tasks.

^{This description was created by for 26c40cb. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 26c40cb in 37 seconds

More details

• Looked at 57 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 6 drafted comments based on config settings.

1. support/PLAYBOOK.md:3

• Draft comment:
  Clarify the phrase 'starter for 10' – the number 10 is ambiguous.
• Reason this comment was not posted:
  Marked as duplicate.

2. support/PLAYBOOK.md:3

• Draft comment:
  The document note mentions it 'will soon become deprecated', which may confuse users about its ongoing relevance.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is purely informative and does not provide a specific suggestion or request for action. It does not align with the rules for useful comments.

3. support/PLAYBOOK.md:49

• Draft comment:
  Define the 'Pending' section more clearly, including actionable next steps.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 20% <= threshold 50%
  This comment is asking for clarification on a 'Pending' section, which seems to be related to documentation or a PR description. It doesn't provide a specific code suggestion or ask for a test to be written. It seems to be more about ensuring clarity in documentation, which is not allowed by the rules.

4. support/PLAYBOOK.md:3

• Draft comment:
  Clarify 'starter for 10' and rephrase 'deprecated' to indicate ongoing updates.
• Reason this comment was not posted:
  Marked as duplicate.

5. support/PLAYBOOK.md:16

• Draft comment:
  Consider converting the URL to a markdown link for improved readability.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50%
  None

6. support/PLAYBOOK.md:49

• Draft comment:
  Add more specifics or timelines to the 'Pending' items to guide prioritization.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_wGjzVWmt4DQGfEeJ

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[mrubens]

I like the content here, but I'm not sure where it should live. Maybe in the main Roo-Code repo? I view this repo as being for end-user-facing documentation.