Verified:GitHub

write-story

Generate structured PR narratives from parallel agent outputs and commit references.

1|Updated Jan 15, 2026

Search Tags:#automation #collaboration #story-writing #PR-descriptions #branch-guidelines #workflow-docs #branch-narratives

Ready to run

npx skills add https://github.com/qmu/workaholic --skill write-story

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-story
Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/write-story
Command: npx skills add https://github.com/qmu/workaholic --skill write-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill centralizes PR narrative creation by assembling scattered notes and outputs into a single, coherent story that serves as the PR description.

Core Features & Use Cases

Structured narrative: Enforces a fixed PR layout with sections such as Overview, Motivation, Journey, Changes, and Outcomes.
Ticket-driven clarity: Integrates per-ticket changes in chronological order with clickable commit references.
Knowledge reuse: Pulls context from agent outputs and historical notes to produce a comprehensive PR narrative.

Quick Start

Use the write-story skill to generate a branch narrative that captures PR content.

Frequently Asked Questions about write-story

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

FAQPage Schema

How do I generate a structured PR description from multiple branch commits?▼

To generate a structured PR description, you consolidate parallel agent outputs and scattered notes into a cohesive story. This creates an organized narrative with sections like overview, motivation, journey, and changes per ticket with commit links.

What is the best way to organize per-ticket changes in a pull request?▼

The best way to organize per-ticket changes is using a structured PR narrative that integrates changes in chronological order with clickable commit references. This ensures ticket-driven clarity and consistent descriptions across multiple changes.

Can I integrate release notes into a branch narrative for PR-ready stories?▼

Yes, you can integrate release notes into a branch narrative by consolidating parallel agent outputs into a single story. The narrative enforces a fixed PR layout that includes performance and release notes integration alongside the journey and outcomes.

Does this PR narrative generation approach work for branch-driven development workflows?▼

Yes, PR narrative generation works for branch-driven development workflows where multiple tickets and changes must be described consistently. It centralizes PR narrative creation by assembling scattered notes and outputs into an actionable PR description.

How do I consolidate parallel agent outputs into a cohesive PR story?▼

You consolidate parallel agent outputs by pulling context from historical notes and agent outputs to produce a comprehensive PR narrative. This knowledge reuse assembles scattered notes into a single, coherent story that serves as the PR description.