grooming-report

When to Use

During and after a backlog grooming session. Use this alongside grooming-prep and backlog-health-check: those decide what to do, this one keeps a durable record of what was done so sessions are auditable and reviewable.

Why

Grooming touches many tickets across a session. Without a record, there is no way to answer "what changed last Tuesday?", to review automated actions after the fact, or to hand a summary to the team. This skill maintains a machine-readable audit trail and turns it into a report the PO and team can read.

Where the Files Live

Keep the audit trail in the gitignored local/ directory so it stays with the user's workflow config and out of version control:

• local/grooming_log.jsonl — append-only audit trail (one JSON object per line)
• local/grooming_report.md — generated report (do not edit by hand)

Instructions

Read local/jira-workflow.md first to understand the project's conventions (issue types, hierarchy, required fields, status names).

1. Mark the start of the session

Before making any changes, append a session marker to local/grooming_log.jsonl:

{"session_start": "YYYY-MM-DD", "groomer": "Name", "total_issues": N, "analyzed": M, "note": "what this session focused on"}

• total_issues — how many issues matched the grooming query
• analyzed — how many you actually reviewed this session

2. Log every action as you go

Append one line per action. Use a small, consistent set of action values so the report stays scannable. Common actions:

{"issue": "KEY-123", "action": "updated", "changes": ["added_label_X", "assigned_to_parent_KEY-100"], "notes": "context", "timestamp": "ISO8601"}
{"issue": "KEY-456", "action": "postponed_for_team_review", "reason": "needs_team_input_on_priority", "timestamp": "ISO8601"}
{"action": "created_epic", "issue": "KEY-789", "summary": "Epic title", "parent": "PARENT-KEY", "timestamp": "ISO8601"}
{"action": "created_feature", "issue": "KEY-790", "summary": "Feature title", "parent": "PARENT-KEY", "timestamp": "ISO8601"}