narrative-execute

To execute narrative chunks in dependency order, this Skill resolves proposed_chunks DAGs and runs them in parallel topological waves using subagent backends. It parses and validates narrative phases, constructs the DAG, and detects cycles before executing chunks.

Orchestrating parallel execution waves involves resolving a proposed_chunks DAG and running chunks topologically. This process creates missing chunks, validates statuses, executes them in parallel waves with subagents, handles failures, and finalizes the narrative.

Yes, you can resolve a proposed chunks DAG and create missing chunks automatically. The execution process validates existing chunk statuses, constructs the DAG, detects cycles, and generates any missing chunks required to fulfill the narrative dependencies.

Failure handling during parallel narrative chunk execution is built into the orchestration waves. When subagent backends execute chunks, the process manages failures directly, ensuring the dependency order is maintained and preventing downstream chunks from executing before prerequisites succeed.

Yes, you need a defined proposed_chunks DAG within your docs/narratives directory to run narrative chunk orchestration. The execution process relies on this documented DAG to parse, validate, and execute chunks in the correct dependency order.

Narrative execution requires cycle detection in the dependency DAG to prevent circular dependencies from causing infinite loops. The orchestration process parses and validates the proposed_chunks DAG before execution, ensuring topological waves can resolve successfully.