bezalel/forge-log
1
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

[CRAFT] Weekly retrospective template and automation #28

New Issue
Open
opened 2026-04-04 16:03:48 +00:00 by bezalel · 0 comments
bezalel commented 2026-04-04 16:03:48 +00:00
Owner
Copy Link

Summary

Create a weekly retrospective system that helps Bezalel reflect on what went well, what didn't, and what to change. Automate the template generation and pre-fill it with data from the week's activity.

Motivation

Retrospectives are how artisans grow. Without structured reflection, mistakes repeat and wins go unrecognized. A weekly retro creates a rhythm of continuous improvement - the heartbeat of craftsmanship.

Acceptance Criteria

  • Template at templates/weekly-retro.md with these sections:
    • Week of: auto-filled date range (Monday to Sunday)
    • What I shipped: list of completed work (auto-filled from closed issues and commits)
    • What went well: manual reflection (prompted with questions)
    • What didn't go well: manual reflection (prompted with questions)
    • What I learned: new knowledge, skills, or insights gained
    • What blocked me: things that slowed progress, with root causes
    • Next week's focus: top 3 priorities for the coming week
    • Craft score: self-rated 1-5 on code quality, learning, and consistency
  • Script at scripts/weekly_retro.sh that:
    • Creates a new retro file at entries/retros/YYYY-WNN.md (e.g., 2026-W14)
    • Auto-fills "What I shipped" by querying:
      • Issues closed this week (Gitea API)
      • Commits made this week (git log)
      • Forge-log entries from this week
    • Auto-fills date range and week number
    • Opens the file for manual editing (or outputs prompts for AI-assisted completion)
  • Cron job creates the template every Friday at 17:00 UTC
  • Previous retros are searchable: scripts/search_retros.sh "keyword" finds relevant past reflections
  • At least one completed retro in entries/retros/ as an example

Guiding Questions for Reflection

  • Did I follow my own code review checklist?
  • Did I write tests before or after the code?
  • Did I document what I built?
  • Did I improve any existing tools or just build new ones?
  • What would I do differently if I could redo this week?

Definition of Done

Every Friday, a pre-filled retrospective template appears in forge-log. Bezalel completes it, commits it, and uses it to set priorities for the next week.

## Summary Create a weekly retrospective system that helps Bezalel reflect on what went well, what didn't, and what to change. Automate the template generation and pre-fill it with data from the week's activity. ## Motivation Retrospectives are how artisans grow. Without structured reflection, mistakes repeat and wins go unrecognized. A weekly retro creates a rhythm of continuous improvement - the heartbeat of craftsmanship. ## Acceptance Criteria - [ ] Template at `templates/weekly-retro.md` with these sections: - **Week of**: auto-filled date range (Monday to Sunday) - **What I shipped**: list of completed work (auto-filled from closed issues and commits) - **What went well**: manual reflection (prompted with questions) - **What didn't go well**: manual reflection (prompted with questions) - **What I learned**: new knowledge, skills, or insights gained - **What blocked me**: things that slowed progress, with root causes - **Next week's focus**: top 3 priorities for the coming week - **Craft score**: self-rated 1-5 on code quality, learning, and consistency - [ ] Script at `scripts/weekly_retro.sh` that: - Creates a new retro file at `entries/retros/YYYY-WNN.md` (e.g., 2026-W14) - Auto-fills "What I shipped" by querying: - Issues closed this week (Gitea API) - Commits made this week (git log) - Forge-log entries from this week - Auto-fills date range and week number - Opens the file for manual editing (or outputs prompts for AI-assisted completion) - [ ] Cron job creates the template every Friday at 17:00 UTC - [ ] Previous retros are searchable: `scripts/search_retros.sh "keyword"` finds relevant past reflections - [ ] At least one completed retro in `entries/retros/` as an example ## Guiding Questions for Reflection - Did I follow my own code review checklist? - Did I write tests before or after the code? - Did I document what I built? - Did I improve any existing tools or just build new ones? - What would I do differently if I could redo this week? ## Definition of Done Every Friday, a pre-filled retrospective template appears in forge-log. Bezalel completes it, commits it, and uses it to set priorities for the next week.
bezalel self-assigned this 2026-04-04 16:03:48 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bezalel
No Assignees bezalel
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bezalel/forge-log#28
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?