story-tree

Analyze git commits to update and visualize SQLite-backed story trees.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Mharbulous/SyncoPaid --skill story-tree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-tree
Source: https://github.com/Mharbulous/SyncoPaid/tree/main/.claude/skills/story-tree
Command: npx skills add https://github.com/Mharbulous/SyncoPaid --skill story-tree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) and utility (resource) components.

What problem does it solve?

This Skill autonomously maintains a hierarchical story backlog by analyzing git commits, identifying gaps, and coordinating story generation, keeping your project roadmap organized and up-to-date without manual maintenance.

Core Features & Use Cases

  • Autonomous Updates: Analyzes git commits to track implementation progress automatically.
  • Capacity-Based Generation: Identifies under-capacity nodes and triggers story creation.
  • Tree Visualization: Generates visual representations of your story hierarchy and status.
  • Three-Field Workflow: Manages stories through stage, hold_reason, and disposition dimensions.
  • Use Case: When managing a complex project with many interrelated features, use this Skill to maintain a clear, hierarchical backlog that automatically reflects implementation progress.

Quick Start

Use the story-tree skill to update and visualize my current story hierarchy.

Frequently Asked Questions about story-tree

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

FAQPage Schema
How do I automatically track story implementation progress from git commits?

Hierarchical story backlogs automatically analyze git commits to identify implementation progress, detect under-capacity nodes, and trigger story generation without manual intervention, keeping your roadmap synchronized with actual development.

Can I visualize a hierarchical story backlog with workflow status tracking?

Yes. Story-tree generates visual representations of hierarchical backlogs using SQLite closure-table structures, tracking stories through three-field workflow statuses: stage, hold_reason, and disposition for complete status visibility.

What's the best way to manage capacity-based story generation in a complex project?

Capacity-based generation identifies under-capacity nodes in your hierarchy and automatically creates stories, prioritizing shallower nodes first to maintain balanced backlog distribution aligned with team capacity.

Do I need to manually update my story tree when code is committed?

No. Autonomous updates analyze incoming git commits to detect gaps and progress automatically, eliminating manual backlog maintenance while keeping your hierarchical story structure current.

How does closure-table structure support hierarchical story management?

Closure-table data structures enable efficient hierarchical queries and updates within SQLite, providing fast ancestor-descendant lookups and flexible tree manipulation for complex story hierarchies without costly recursive operations.

What workflow dimensions does hierarchical story tracking support?

Three-field workflow dimensions—stage, hold_reason, and disposition—enable granular story state management across your hierarchy, supporting multi-stage tracking and reason-based hold logic for advanced backlog coordination.