entity-tracker
SolidBuilds and maintains ENTITY_STATE.yaml — the persistent structured database of every character, location, object, organization, timeline entry, and world rule in the manuscript. Operates in BUILD mode (initial extraction from existing chapters) and UPDATE mode (incremental tracking as new chapters are written or revised). The single source of truth that other skills consume instead of rebuilding entity databases from scratch.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- felipelobomotta-blip
- Repository
- felipelobomotta-blip/book-genesis-v4
- Created
- 5 months ago
- Last Updated
- 3 days ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
continuity-guardian
Cross-manuscript consistency auditor. Runs after every 3-5 chapter batch and after full manuscript completion. Catches continuity errors, information-flow violations, timeline contradictions, and orphaned plot threads that individual chapter writers miss. The agent that asks "but how does he KNOW that?"
gabe-entity
Entity-context reader — assembles ONE application entity's slice (code map + registry + bindings) into a context pack from the command center's committed data, without re-reading the codebase. Usage: /gabe-entity <slug> | list | <slug> --json
pm-entity-registry
Build the Entity & State Registry - Live Register 1 of 4 in the FDD+SDD framework. Extracts business entities from PRD Business Capabilities, defines their states and transitions in Mermaid.js, and writes to /domain/entities.md. Phase 4 skill - runs after PRD is complete. This is the operational register; pm-domain-model is the optional higher-level companion (cross-domain ERD and domain boundaries) that sits above it.