Skip to content

Closed — opened in error - #26

Closed
ghozzza wants to merge 1 commit into
celo-org:mainfrom
ghozzza:ghozzza/monthly-report-command
Closed

Closed — opened in error#26
ghozzza wants to merge 1 commit into
celo-org:mainfrom
ghozzza:ghozzza/monthly-report-command

Conversation

@ghozzza

@ghozzza ghozzza commented Aug 29, 2026

Copy link
Copy Markdown

Opened in error and closed. Nothing here needs review.

pm-kit has /weekly-status but nothing for the monthly report, so every
month it gets written from memory of how the last one looked. This adds
the monthly counterpart, built on the same evidence bar.

Four rules in it come from mistakes that have actually cost something:

- Read last month's headings first. Nothing in the workflow compares a
  new report against the previous one, which is how a section gets
  renamed or dropped without anyone deciding to. Keep the heading and
  write "no targets were set for this period" underneath it — a missing
  section reads as a hidden number.
- Merged is not shipped. A PR on main is not in front of users until it
  is deployed; the report says which state each item is in.
- Decisions needed leads, if it is non-empty. It is the only part that
  changes what happens next.
- Say what the report does NOT cover — a count you could not run, a
  deployment you could not confirm.

README updated in all four places that enumerate the commands,
including the "first five / last two" sentence, and the plugin version
bumped so `claude plugin update` picks the command up.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@ghozzza ghozzza closed this Aug 29, 2026
@ghozzza ghozzza changed the title feat(plugin): add /monthly-report, the monthly counterpart to /weekly-status Closed — opened in error Aug 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant