run_c321602452fb6a3f

input

{
  "request": "Triage Jira ticket MZCLD-3768: Add runbook creation and updating skill to mozcloud repo",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/MZCLD-3768"
  ],
  "sourceContext": {
    "issue": "MZCLD-3768"
  }
}

summary

MZCLD-3768 requests adding a "runbook creation and updating skill" to the mozcloud repo — essentially a tool/skill that drafts and maintains MozCloud CloudEng runbooks in the team's house style. The ticket is In Progress with no comments yet. The description is fairly detailed and includes a reference to a "sample runbook created from scratch" that appears to be cut off/truncated in the ticket body, and no explicit Confluence runbook/design doc link was found in the ticket to pull additional context from.

findings

• Ticket defines clear functional requirements for the skill: match house style, separate assumed knowledge from required permissions, balance content for experienced SREs vs. less experienced developers, and add structural callouts for when to escalate to Platform/Cloud Eng.
• Ticket specifies a safe-by-default workflow: drafts must be written to a local scratch file or an unpublished Confluence draft (never directly to a live page), and publishing to the final destination (shared Support Runbooks folder or tenant-specific Support:<Service> page) only happens on explicit instruction.
• The description references a 'Sample runbook created from scratch' but the text appears truncated with no visible link, attachment, or example content — this is likely intended as supporting evidence/acceptance criteria but is missing or not captured in the description field.
• No comments exist on the ticket yet, so there's no discussion of implementation progress, blockers, or review status despite it being marked In Progress.
• No Confluence runbook template, house-style guide, or design doc link was found attached to or referenced in the ticket text, so confluence.page.read could not be used to pull supporting context.

proposed actions

Thanks for the clear spec here. A couple of triage notes/questions to help move this forward:

1. The description cuts off after "Sample runbook created from scratch:" — could you attach or link the sample runbook (or the Confluence page for it) so we can validate the skill's output against house style?
2. Could you link the house-style guide / runbook template (Confluence page) this skill should conform to? That will help reviewers confirm the drafted output matches expectations for tone, structure (assumed knowledge vs. permissions), and escalation callouts.
3. Since this is marked In Progress with no comments yet, please post a quick status update — e.g., current implementation location in the mozcloud repo, whether the draft-to-scratch/unpublished-Confluence-draft safeguard is implemented and tested, and what's left before this can move to review.
4. Please confirm the exact target destinations (shared Support Runbooks folder space/page ID, and the Support:<Service> tenant page naming convention) so the publish step can be validated against the correct, current locations.

Happy to help review once the sample runbook and style reference are linked.

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "MZCLD-3768"
    },
    "result": {
      "key": "MZCLD-3768",
      "summary": "Add runbook creation and updating skill to mozcloud repo",
      "status": "In Progress",
      "description_text": "Drafts and updates MozCloud CloudEng runbooks to match the \"house style.    It separates assumed knowledge from required permissions, balances content for both experienced SREs and less experienced developers, and adds structural callouts for when to stop and consult Platform/Cloud Eng.    It writes drafts to a local scratch file or an unpublished Confluence draft (never live) for review, and only publishes to the correct destination \u2014 the shared Support Runbooks folder or a tenant-specific Support: <Service> page \u2014 once explicitly told to.   Sample runbook created from scratch:",
      "comment_count": 0,
      "comments": []
    }
  }
]

log