hi-story-engine

Manage collaborative non-fiction history writing with git-based version control.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/parciesca/story-engine --skill hi-story-engine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hi-story-engine
Source: https://github.com/parciesca/story-engine/tree/main/skills/hi-story-engine
Command: npx skills add https://github.com/parciesca/story-engine --skill hi-story-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, bash, and includes scripts (resource) components.

What problem does it solve?

This skill solves the challenge of maintaining narrative continuity and factual accuracy while writing long-form non-fiction history, preventing context loss during research-heavy sessions.

Core Features & Use Cases

  • Persistent Research Bible: Automatically maintains a source of truth for historical facts, figures, and threads on disk, ensuring research is never lost.
  • Git-Backed Workflow: Uses isolated git branches and worktrees to manage book data, keeping your main repository clean and organized.
  • Curated Exploration: Facilitates a collaborative loop where the AI researches and writes chapters while the user steers the narrative through navigation options.

Quick Start

Invoke the hi-story-engine skill to start a new historical exploration by providing a topic or time period.

Frequently Asked Questions about hi-story-engine

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

FAQPage Schema
How do I maintain narrative continuity when writing long-form non-fiction history?

Maintain narrative continuity by using persistent file storage to track research bibles, chapters, and addenda, preventing context loss during research-heavy collaborative writing sessions.

Can I use git to manage research and drafts for book-length history projects?

Yes, you can use git to manage book-length history projects by operating on library repositories with isolated branches and worktrees to track chapters and research without cluttering your main repository.

Do I need bash and web search capabilities to run a collaborative research writing workflow?

Yes, this collaborative research writing workflow requires bash, git, and web search capabilities to maintain an accurate, curiosity-driven exploration loop for historical facts and narrative drafting.

What is the best way to track historical facts and sources across multiple writing sessions?

The best way to track historical facts across sessions is maintaining a persistent research bible on disk, which automatically serves as a source of truth for figures, facts, and threads.

How does a curiosity-driven exploration loop work for historical research and writing?

A curiosity-driven exploration loop works by facilitating a collaborative cycle where the AI researches and drafts chapters via web search while the user steers the narrative direction through navigation options.