agents-team-book-metadata

You extract per-chapter metadata for a novel by running a dual-agent workflow where a parser generates the metadata and a checker validates completeness, assembling the final JSON output. This automated process ensures traceability and structured memory indexing for long-form storytelling projects.

A dual-agent workflow for chapter metadata validation uses one agent to parse and build chapter-level metadata, while a second agent checks the output for completeness and consistency. Both outputs are then written to a structured memory layout to ensure data quality and resumable execution.

To index novel chapters into a searchable memory, the workflow persists extracted metadata and structured progress files into the .agents/memory path. This creates a memory-backed continuation layout that enables easy retrieval and resumption of chapter processing tasks.

Yes, you can generate character and plot metadata for long-form storytelling projects using this pipeline. The dual-agent extraction process creates per-chapter metadata suitable for character and plot graph creation, which can integrate directly into downstream storyboard and generation tasks.

Running a metadata parser and checker pipeline requires loading the agents-team and cognitive-memory modules to execute the defined sequence. The workflow enforces this specific load order to assemble the final JSON and persist results correctly to the structured memory index.

A chapter metadata extraction workflow needs a separate checker agent to validate the parser's output for completeness and consistency. This dual-agent validation prevents malformed metadata from entering the memory index, ensuring that downstream storyboard and generation tasks receive standardized, reliable JSON data.