write-history

Append progress entries to the AI-DLC history file by cycle, phase, and step.

24|2|Updated Nov 6, 2025
One-click install
npx skills add https://github.com/ikeisuke/ai-dlc-starter-kit --skill write-history
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-history
Source: https://github.com/ikeisuke/ai-dlc-starter-kit/tree/main/skills/write-history
Command: npx skills add https://github.com/ikeisuke/ai-dlc-starter-kit --skill write-history

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill appends progress history to the AI-DLC history file at the appropriate cycle, phase, unit, and step, ensuring traceable records across Inception, Construction, and Operations.

Core Features & Use Cases

  • Append history entries when steps complete or reviews finish, coordinating with the main aidlc workflow.
  • Determine the correct history file path from cycle/version and phase information, enabling consistent logging.
  • Use in any phase of the AI-DLC lifecycle (inception, construction, operations) including unit-specific updates during Construction.

Quick Start

Run the write-history script with the required flags to append a log entry for the current cycle, phase, and step.

Frequently Asked Questions about write-history

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

FAQPage Schema
How do I automatically record AI development lifecycle progress into a history file?

To automatically record AI development lifecycle progress, you can run the write-history script with required flags. It appends traceable log entries to the AI-DLC history file as tasks complete across inception, construction, and operations phases.

What is the best way to log unit-level updates during the construction phase of a workflow?

Logging unit-level updates during the construction phase requires appending entries to the AI-DLC history file. This skill enforces file I/O handling and cycle-version awareness to ensure traceable records for specific unit steps.

How does cycle and version awareness work when logging script history?

Cycle and version awareness determines the correct history file path before appending logs. This mechanism coordinates with the main AI-DLC workflow to place progress entries at the appropriate cycle, phase, unit, and step.

Can I use bash scripts to append traceable records across different development phases?

Yes, you can use bash scripts to append traceable records across inception, construction, and operations phases. The script handles file I/O and artifact referencing to ensure consistent logging throughout the entire lifecycle.

Do I need to manually specify the file path when logging workflow history?

No, you do not need to manually specify the file path when logging workflow history. The skill automatically determines the correct history file path from the current cycle, version, and phase information.

When should I not use automated history logging for AI-DLC tasks?

You should not use automated history logging when tasks are incomplete or reviews are unfinished. This skill is designed to append entries only when steps complete or reviews finish, ensuring accurate traceable records.