chronicle

Name: chronicle
Availability: InStock
Author: oddship

Generate narrative builder's logs from coding sessions in markdown.

3|Updated Feb 24, 2026

Search Tags:#automation #logs #session analysis #chronicle #builder's log #code narrative

Ready to run

npx skills add https://github.com/oddship/bosun --skill chronicle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chronicle
Source: https://github.com/oddship/bosun/tree/main/.pi/skills/chronicle
Command: npx skills add https://github.com/oddship/bosun --skill chronicle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed builder's logs from coding sessions, transforming raw activity into narrative summaries that capture the development journey.

Core Features & Use Cases

Automated Narrative Generation: Synthesizes chronicles from session and plan data.
Plan vs. Reality Analysis: Highlights deviations and pivots in the development process.
Use Case: After a day of coding, use this Skill to automatically generate a daily log entry detailing the features worked on, challenges faced, and outcomes achieved, formatted in a professional builder's log style.

Quick Start

Generate today's builder's log using the /chronicle command.

Frequently Asked Questions about chronicle

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

FAQPage Schema

How do I automatically generate a builder's log from my coding sessions?▼

To generate a builder's log from coding sessions, execute the /chronicle command, which analyzes session execution data and synthesizes it into a structured markdown narrative. It identifies development journeys, summarizes sessions, and detects deviations from plans.

What is session analysis for code narrative generation?▼

Session analysis for code narrative generation is the process of examining raw execution data to construct a chronological story of development. It identifies journeys, summarizes sessions, and highlights deviations from plans to craft a compelling builder's log.

Can I track plan deviations and pivots in my development process automatically?▼

Yes, you can track plan deviations automatically by generating builder's logs from sessions and associated plans. The analysis detects deviations and pivots in the development process and highlights them within the structured markdown narrative.

How do I create a daily development log entry from raw activity data?▼

You create a daily development log by running the /chronicle command against your session and plan data. It synthesizes raw activity into a professional builder's log entry detailing features worked on, challenges faced, and outcomes achieved.

Does chronicle require any specific dependencies to process session data?▼

No, chronicle requires no external dependencies to process session data. It relies on parallel processing of analyzed data by specialized scribe agents to synthesize chronicles from session and plan data.

What format does the automated session narrative generation output?▼

Automated session narrative generation outputs a structured markdown format. It synthesizes execution data and associated plans into a detailed builder's log that captures the development journey, including deviations and pivots.