philosopher

You can generate a post-build retrospective by running the philosopher skill after completing a build. It analyzes your build execution logs, inspection reports, and planning files to identify what worked and what failed during construction.

Knowledge management for Minecraft build process improvements works by distilling actionable process lessons into Claude's project memory. This ensures that operational lessons and architectural insights captured during construction are recorded for reuse in future builds.

Yes, you can extract manual redstone activation steps from build execution logs. The Skill automatically surfaces one-time manual activation steps, such as redstone kicks, that are required for complex automated builds to function properly.

Yes, you need access to project-specific build artifacts and memory storage to analyze build deviations. The Skill requires these inputs to synthesize inspection data, record reusable procedural insights, and generate process retrospective reports.

Limitations of automating post-build reviews include the dependency on having pre-existing build execution logs and project documentation. The Skill synthesizes planning deviations from these artifacts, meaning it cannot review builds lacking recorded inspection data or planning files.