lifecycle-extend

Extend Agora's ILL lifecycle with new states while preserving saga invariants.

Updated May 2, 2026
One-click install
npx skills add https://github.com/gmanch94/agora --skill lifecycle-extend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lifecycle-extend
Source: https://github.com/gmanch94/agora/tree/main/.claude/skills/lifecycle-extend
Command: npx skills add https://github.com/gmanch94/agora --skill lifecycle-extend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adding a new lifecycle state or step in Agora is easy to get wrong, and missing just one required code/docs/test update can break saga invariants or leave the coordinator unable to drive the state machine.

Core Features & Use Cases

  • Lifecycle scaffolding checklist: Ensures the new lifecycle state and forward/compensator step are added across models, saga registry/handlers, migrations (when needed), PRD documentation, coordinator tests, happy-path demos, and architecture diagrams.
  • Safety and invariant enforcement: Guides the implementation so forward steps require a committed gate, compensators target only committed forward events, and idempotency and datetime rules match Agora’s conventions.
  • ISO 18626 mapping support: Helps connect the new user-visible lifecycle state to the correct ISO 18626 message/state mapping and updates the lifecycle diagram and PRD table accordingly.

Quick Start

Tell the skill the new state name, the step name, where it sits between existing states, the forward ReShare side-effect, the compensator undo/observation strategy, and the ISO 18626 mapping you intend to represent.

Frequently Asked Questions about lifecycle-extend

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

FAQPage Schema
How do I add a new state to an ILL lifecycle state machine without breaking saga orchestration?

To add an ILL lifecycle state without breaking saga orchestration, implement coordinated forward and compensator pairs, update the saga registry, and enforce idempotency rules to preserve invariants.

What is a forward and compensator pair in saga orchestration?

A forward and compensator pair in saga orchestration is a set of coordinated steps where the forward action executes a state change and the compensator reverses it, targeting only committed forward events to maintain transactional safety.

How do I map a new ReShare ILL workflow state to the ISO 18626 standard?

To map a new ReShare ILL workflow state to ISO 18626, identify the corresponding message and state mappings, then update your PRD documentation and architecture diagrams to reflect the new lifecycle coverage accurately.

What components need updates when extending an agent-driven ILL lifecycle?

Extending an agent-driven ILL lifecycle requires coordinated updates across lifecycle models, saga flows, optional migrations, documentation, coordinator tests, and architecture diagrams to ensure the state machine remains fully functional.

Why do compensators in a saga state machine require a committed gate?

Compensators in a saga state machine require a committed gate to ensure undo operations only target forward events that have been successfully committed, preventing data inconsistency and maintaining strict transactional invariants.

Does adding a lifecycle step require database migrations in Agora?

Adding a lifecycle step in Agora requires database migrations when the new state or forward and compensator steps alter existing data structures, ensuring the saga registry and models remain synchronized with the database schema.