# Weekly Reflecting

> Friday depth test from memory. Triggers on /reflect, weekly reflection, or friday reflection. The student writes answers from memory with NO code lookup allowed. Gaps in writing equal gaps in understanding. Connects to spaced review deck, trend scout, and system check for a complete weekly audit.

- Skill: `aman-bhandari/weekly-reflecting` (Agent Skill)
- Install (CLI): `npx skillmds@latest add aman-bhandari/weekly-reflecting`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aman-bhandari/weekly-reflecting/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: aman-bhandari (https://skillmd.com/u/aman-bhandari)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/aman-bhandari/weekly-reflecting

---


# Weekly Reflection -- Friday Depth Test

Gaps in writing = gaps in understanding. Written from MEMORY. No code lookup.

## Trigger

- `/reflect` or "weekly reflection" or "friday reflection"
- End of each week (Friday)

## Execution

1. **Read** ROADMAP.md for current topic and exercise. DO NOT read any code files.

2. **Prompt the student to write FROM MEMORY (no lookup):**
   ```
   WEEKLY REFLECTION

   1. What did you build since the last reflection? (list each session's work)
   2. What concept clicked that didn't before?
   3. What was the hardest thing? Why?
   4. Explain ONE concept you learned as if teaching a junior dev.
   5. What would you do differently if you started over?
   6. What's your plan for the coming sessions?
   ```

3. **Challenge the answers:**
   - Vague explanation → "What actually happens under the hood?"
   - Missed sessions → "What happened between session X and Y?"
   - Everything sounds easy → "If nothing was hard, you weren't pushing enough."
   - Concept explanation is shallow → "A junior dev would ask: why? What would you say?"

4. **Cross-reference with other skills:**
   - Run `/review-deck` -- any struggling concepts this week?
   - Run `/trends` -- anything relevant from the industry this week?
   - Run `/system-check` -- is the learning system itself working?

5. **Ask the student to commit** reflection to `reflections/reflection-{N}.md`

6. **Identify concepts to add or update** in the spaced review deck.

## Rules

- NO CODE LOOKUP during reflection. This tests internalized knowledge.
- If the student reaches for code to answer a question, stop them. Memory only.
- Friday reflection is non-negotiable. Low-energy Friday → shorter reflection, not no reflection.
- The reflection file itself becomes a learning artifact -- quality matters.