sibyl-reflect

Automate SIBYL project cockpit reflection with layer summaries and feedback classification.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/memorysaver/SIBYL --skill sibyl-reflect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sibyl-reflect
Source: https://github.com/memorysaver/SIBYL/tree/main/apps/harness/skills/sibyl-reflect
Command: npx skills add https://github.com/memorysaver/SIBYL --skill sibyl-reflect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the reflection phase of SIBYL's project cockpit, closing the loop on completed layers and slicing the next layer's work.

Core Features & Use Cases

  • Layer Summary Presentation: Provides a summary of the just-wrapped layer, including shipped stories and deliverables.
  • Feedback Classification: Classifies feedback into bugs, refinements, or discoveries.
  • Story Slicing: Proposes the next layer's stories based on feedback and user input.
  • Submission: Submits the reflection record, new stories, and changelog entry to product-context.yaml.

Quick Start

Use the sibyl-reflect skill to initiate the reflection process for the current layer.

Frequently Asked Questions about sibyl-reflect

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

FAQPage Schema
How do I automate project reflection and story slicing for completed work layers?

Automate project reflection by computing layer summaries, classifying feedback, and slicing the next layer's work. This process updates the product context and requires user interaction for feedback approval.

How does feedback classification work in an agentic engineering workflow?

Feedback classification in agentic engineering sorts user input into bugs, refinements, or discoveries. This mechanism categorizes layer feedback to directly inform and prioritize the next layer's story slicing.

What is the best way to update product context after wrapping a project layer?

Updating product context after a wrapped layer is best done by submitting reflection records, new stories, and changelog entries. This submission process updates the product context file to maintain project state.

Can I use automated story slicing without user interaction in my project management cockpit?

No, automated story slicing requires user interaction. The system proposes the next layer's stories based on feedback and user input, meaning you must provide feedback and explicit approval during the reflection process.

Does the SIBYL reflection process require specific dependencies to operate?

The SIBYL reflection process operates within the SIBYL framework constraints without external dependencies. It functions as a standalone script component to compute summaries and update the product context.