write-task-history

Document completed conversation work into a dated markdown task history file.

Updated May 31, 2025
One-click install
npx skills add https://github.com/dEitY719/dotfiles --skill write-task-history
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-task-history
Source: https://github.com/dEitY719/dotfiles/tree/main/claude/skills/write-task-history
Command: npx skills add https://github.com/dEitY719/dotfiles --skill write-task-history

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing and maintaining a daily task history from ongoing conversations is time-consuming and error-prone. This skill automates the process by capturing what happened in a session and exporting ready-to-use artifacts for project management and code reviews.

Core Features & Use Cases

  • Automates logging of completed work from a conversation into a dated task-history file
  • Generates two ready-to-paste formats: a JIRA ticket (plain text with sections) and a git PR description (markdown)
  • Works across projects and teams to document progress, decisions, and outcomes

Quick Start

Ask the AI to log today's work from the conversation using the write-task-history skill.

Frequently Asked Questions about write-task-history

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

FAQPage Schema
How do I generate a JIRA ticket draft from a conversation?

To generate a JIRA ticket draft from a conversation, the skill parses your recent work context and formats the completed tasks into a plain text, copy-paste-ready ticket structure.

What is the best way to automate a daily work log from chat history?

Automating a daily work log from chat history is done by resolving a storage path and writing your session's completed tasks into a dated markdown file with a timestamp.

How do I create a PR description based on recent work?

You can create a PR description based on recent work by prompting the skill to process your conversation context, which formats the session details into ready-to-paste markdown.

Can I write task history to a specific markdown file path?

Yes, you can write task history to a specific file path because the skill resolves a storage path before writing both the JIRA ticket and PR description outputs to a dated markdown file.

Does documenting task history require any external dependencies?

Documenting task history with this skill requires no external dependencies, as it independently processes conversation context and outputs formatted markdown files.