skills.rest
estevanhernandez-stack-ed
estevanhernandez-stack-edCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reflect

Guide a peer engineer through a structured post-ship retro and review.

1|Updated Apr 3, 2026
Search Tags:#process-improvement#peer-review#retro#reflect#friction-logging#builder-feedback
One-click install
npx skills add https://github.com/estevanhernandez-stack-ed/vibe-cartographer --skill reflect-estevanhernandez-stack-ed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/estevanhernandez-stack-ed/vibe-cartographer/tree/main/plugins/vibe-cartographer/skills/reflect
Command: npx skills add https://github.com/estevanhernandez-stack-ed/vibe-cartographer --skill reflect-estevanhernandez-stack-ed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams perform a focused post-ship retro and peer review, turning lived experience into actionable lessons.

Core Features & Use Cases

  • Two-part flow: a brief check-in and a qualitative project review.
  • Persona-adaptive voice ensures feedback matches the builder's style.
  • Guides the review of artifacts across docs/scope, docs/prd, docs/spec, docs/checklist, and the live build.

Quick Start

Initiate /reflect after a ship, complete the check-in and review, and capture reflections and lessons learned in docs/reflection.md.

Frequently Asked Questions about reflect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a structured post-ship retro with a peer engineer?▼

A structured post-ship retro guides a peer engineer through a two-part qualitative project review, evaluating artifacts like docs/scope, docs/prd, and docs/spec to surface concrete strengths and actionable improvements after a ship.

What is friction-logging and how does it improve peer review?▼

Friction-logging is a workflow that surfaces concrete obstacles and actionable improvements during peer review. It enforces documented evaluation rubrics across project artifacts to provide structured, qualitative builder feedback.

Can I adapt peer feedback to match a builder's specific persona?▼

Yes, persona-adaptive voice ensures feedback matches the builder's chosen style. The review applies this adapted voice across artifact evaluations, including docs/checklist and the final reflection.

What project artifacts are evaluated during a post-ship retrospective?▼

The retrospective evaluates artifacts across docs/scope, docs/prd, docs/spec, docs/checklist, and the live build. Reviewing these prerequisites ensures comprehensive coverage of the project's shipped scope.

How do I document lessons learned from a project retrospective?▼

You document lessons learned by completing a brief check-in and qualitative project review, then capturing reflections in docs/reflection.md. This workflow turns lived shipping experience into actionable notes.

When should I initiate a post-ship retro and what prerequisites are enforced?▼

Initiate a retro immediately after a ship. The retro enforces prerequisites, ensuring required artifacts like docs/spec and docs/checklist exist and are reviewed before capturing lessons in docs/reflection.md.

Related Skills

Explore More Software Engineering Skills→
zabuuqzabuuq

retro

Synthesize sprint notes and artifacts into a project retrospective document.

Community
Advanced
challengepostchallengepost
40

reflect

Run a two-part quiz and qualitative project review to generate docs/reflection.md.

Official
Intermediate
AlexiosBluffMaraAlexiosBluffMara
2

adversarial-ux-test

Roleplay a tech-resistant persona to identify UX friction and generate actionable tickets.

Community
Advanced
Zhachory1Zhachory1

council

Orchestrate multi-persona adversarial reviews of engineering artifacts and decisions.

Community
Advanced