Reflection Craft FAQs

Question 1

How does it know which parts of the code were changed?

Accepted Answer

The skill is subsystem-aware; it analyzes git diffs and maps them to your project's defined subsystems to ensure the reflection is grounded in the actual technical changes made.

Question 2

When is the best time to trigger this skill?

Accepted Answer

You should use Reflection Craft at the end of an engineering session, specifically when you want to 'reflect on this session', 'capture learnings', or 'debrief this work' to ensure knowledge isn't lost.

Question 3

What kind of output does Reflection Craft generate?

Accepted Answer

It creates a structured Markdown artifact in a dedicated discoveries folder, containing session context, a friction log, categorized learnings (rules, features, fixes, spec-updates), and proposed system changes.

Question 4

What is the 'Frontier Check' in Reflection Craft?

Accepted Answer

It is a selection process that prioritizes learnings that 'shift the frontier'—meaning improvements that increase both the quality and volume of future output rather than simply trading one for the other.

Question 5

Does this skill work with other Claude Code commands?

Accepted Answer

Yes, it is part of an integrated workflow where the reflection artifact serves as the input for further discovery or consolidation commands to implement the captured improvements.

Reflection Craft

Key Features

Use Cases

Reflection Craft

Key Features

Use Cases