sibyl-human-alignment

Regenerate the SIBYL human-alignment store at each story wrap.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that the SIBYL system maintains alignment between product intent and execution by refreshing the human-alignment store at each story wrap.

Core Features & Use Cases

  • Alignment Generation: Refreshes the .sibyl/alignment/ store with architecture models, divergence reports, decision ledgers, and narrative exports.
  • Lifecycle Integration: Integrated into the SIBYL harness CLI, runs at each story wrap/reflect cycle.
  • Use Case: Automates the regeneration of the architecture model, divergence report, decision ledger, and derived diagrams, ensuring the Human Alignment cockpit tab reflects current information.

Quick Start

Run 'sibyl align' to refresh the human-alignment store.

Frequently Asked Questions about sibyl-human-alignment

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

FAQPage Schema
How do I align product intent with execution tracking during story wrap?

To align product intent with execution tracking, you can run the 'sibyl align' command. This refreshes the human-alignment store by serializing artifacts and regenerating architecture models, divergence reports, and decision ledgers.

What is a human-alignment store in agentic engineering?

A human-alignment store is a directory containing architecture models, divergence reports, decision ledgers, and narrative exports. It ensures that agentic engineering execution remains continuously aligned with the original product intent.

Do I need an isolated subagent to generate architecture diagrams and narratives?

Yes, an isolated subagent is required to generate architecture diagrams and narratives. The alignment process delegates generative narrative and diagram authoring tasks to this subagent while the harness CLI handles artifact serialization.

When should I regenerate divergence reports and decision ledgers?

You should regenerate divergence reports and decision ledgers at each story wrap or reflect cycle. This lifecycle integration ensures the Human Alignment cockpit tab always reflects the most current execution state and product intent.

Can I use SIBYL harness CLI without a subagent for execution tracking?

No, the SIBYL harness CLI requires an isolated subagent to function correctly for this task. While the CLI handles artifact serialization, the subagent is strictly required for the generative tasks of authoring narratives and diagrams.