storyteller

Convert development session context into narrative markdown with YAML frontmatter.

Updated Sep 9, 2025

Search Tags:#architecture #documentation #storytelling #narrative #technical writing #journey #developer reflections

Ready to run

npx skills add https://github.com/htafolla/chrono-warp-drive --skill storyteller-htafolla

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: storyteller
Source: https://github.com/htafolla/chrono-warp-drive/tree/main/.opencode/skills/storyteller
Command: npx skills add https://github.com/htafolla/chrono-warp-drive --skill storyteller-htafolla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts scattered development progress—decisions, failures, dead ends, and small wins—into clear, engaging narrative documents that preserve context for future you and your team.

Core Features & Use Cases

Session-grounded storytelling: Writes reflections, sagas, journeys, and technical narratives using the current session’s full context as primary material.
Structured story outputs: Produces correctly named files (by type and date) and routes them to the right docs/reflections location.
Readable, developer-friendly voice: Applies a warm, candid tone and enforces required sections like Key Takeaways and What Next, while avoiding common “AI-sounding” patterns.

Quick Start

Ask the AI to write a technical narrative about what changed in the architecture, including the first moment you realized the old approach wouldn’t work, and save it as a {descriptive-name}-narrative with today’s date.

Frequently Asked Questions about storyteller

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

FAQPage Schema

How do I turn my development session context into narrative documentation?▼

You can turn development session context into narrative documentation by transforming decisions, failures, and wins into long-form markdown reflections, sagas, or journeys that preserve technical context for future reference.

What is the best way to write technical narratives for architectural changes?▼

Writing technical narratives for architectural changes is best handled by grounding the story in the current session context, producing developer-friendly markdown with mandated Key Takeaways and What Next sections to capture the journey.

Can I document multi-session bug fix journeys in a single reflection file?▼

Yes, you can document multi-session bug fix journeys in a single reflection file by capturing the full development saga across sessions and routing the generated markdown narrative to your specified docs/reflections path.

How do I structure developer reflections to avoid sounding like an AI generated them?▼

To structure developer reflections and avoid AI-sounding output, apply a warm, candid tone while enforcing specific sections like Key Takeaways and What Next, ensuring the narrative documents remain readable and engaging for the team.

Does this storytelling approach generate YAML frontmatter for technical writing?▼

Yes, this storytelling approach generates YAML frontmatter with required fields for technical writing, accompanying the long-form markdown narrative to ensure your architecture documentation is properly structured and metadata-rich.

When should I use narrative documentation instead of standard technical docs?▼

You should use narrative documentation when you need to preserve the human context of decisions, dead ends, and small wins from a development session, converting scattered progress into engaging stories rather than dry reference material.