rrr Workflow for 1-nazt-02-portfolio-vercel

Purpose

Provide a repeatable retrospective (rrr) workflow for agents contributing to the Soul-Brews-Hub/1-nazt-02-portfolio-vercel repository. Capture each session as a dedicated GitHub issue—do not open a PR unless a maintainer later requests code or docs updates.

---

Step-by-Step Checklist

1. Prepare Environment

• Confirm gh CLI is authenticated (gh auth status).
• Sync main for situational awareness: git switch main && git pull --ff-only.
• Note any local changes with git status --short; include a summary in the retrospective issue.

2. Capture Current State

Collect key context that will go into the issue:

git status --short
git diff --stat

If unrelated changes exist, either wrap them up first or describe their status in the retrospective.

3. Gather Session Notes

Before creating the issue, outline:

• Session objectives and accomplishments
• Risks/blockers
• AI Diary (first-person reflection)
• Honest Feedback (candid assessment)
• Follow-up tasks with checkboxes Use the template below so the issue body is ready to paste.

4. Optional QA Checks

If the session touched code, run applicable commands and record the outcomes:

• npm run lint
• npm run build Skip when it’s purely planning/documentation, but document the decision.

5. Create Retrospective Issue

1. Set timestamps in GMT+7:

   SESSION_DATE=$(TZ='Asia/Bangkok' date +%Y-%m-%d)
   END_TIME_LOCAL=$(TZ='Asia/Bangkok' date +%H:%M)

2. Launch the issue with gh (edit placeholders as needed):

   gh issue create \
     --title "retrospective: ${SESSION_DATE} ${END_TIME_LOCAL} GMT+7" \
     --body-file - <<'ISSUE'

Session Retrospective — ${SESSION_DATE} ${END_TIME_LOCAL} GMT+7

Snapshot

• Focus: (What problem/workstream?)
• Context Issues: #7
• Plan Issues: #9
• Related Branch: (If any work was on a branch; otherwise N/A)

Highlights

• ...

Challenges & Risks

• ...

AI Diary

(First-person narrative of decisions, surprises, and feelings.)

Honest Feedback

(Balanced assessment: what worked vs. what needs improvement.)

QA / Checks

• npm run lint
• npm run build
• Notes: ...

Follow-up Tasks

• Task 1
• Task 2 ISSUE

Adjust issue references, highlights, and tasks to reflect the current session.

6. After Issue Creation

• Share the new issue link with the maintainer or in the active conversation.
• Track follow-up tasks via the issue’s checklist or separate plan/context issues.
• Do not merge anything; this workflow is issue-only.

---

Retrospective Notes Template (Scratch Pad)

Use this locally before posting to ensure the issue is organized:

### Highlights
- ...

### Challenges & Risks
- ...

### AI Diary
- ...

### Honest Feedback
- ...

### Follow-up Tasks
- [ ] ...

---

Safety Reminders

• Never use destructive git commands (git reset --hard, force pushes, rm -rf).
• Keep timezone references in GMT+7 (primary) and add UTC only if needed.
• If code changes require a PR later, wait for explicit maintainer direction before opening one.