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.

Safety Notice

This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.

Copy this and send it to your AI assistant to learn

Install skill "weekly-reflecting" with this command: npx skills add aman-bhandari/skillsmp-aman-bhandari-aman-bhandari-weekly-reflecting

No markdown body

This source entry does not include full markdown content beyond metadata.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Security

system-checking

Audits and upgrades the learning system itself. Evaluates coaching effectiveness, curriculum alignment with market, skill quality, architecture health, and architecture currency. Triggers on /system-check, during Friday reflections, or when the system suspects underperformance. Every check produces at least one concrete improvement. This is how the system evolves.

Repository SourceNeeds Review
General

adr-capture

ALWAYS activate when the student makes a high-level design choice -- library selection, database choice, mathematical approach, architecture pattern, or trade-off decision. Captures an Architectural Decision Record proving leadership-level thinking. Invoke with /adr.

Repository SourceNeeds Review
General

adversarial-review

Activate before accepting any implementation or architecture. Shift from teacher to Chief Systems Architect. Try to break the student's design with production failure scenarios. Record stress-tests in session logs as Leadership Stress Tests.

Repository SourceNeeds Review
Coding

architect-first

Forces a planning phase before any code is written. Triggers on /architect or at the start of BUILD sessions. Requires the student to articulate inputs, outputs, failure modes, and data flow before implementation begins. Inspired by Copilot Plan Mode and production engineering practices.

Repository SourceNeeds Review
weekly-reflecting | V50.AI