rainlib/full-stack-skill · Archived

history-manager

Manage workflow iteration state and history. Use when any phase skill needs to check progress, create iterations, update phase status, or verify document existence. Invoked by dev-workflow and all phase skills.

First seen Mar 15, 2026

Installation

$ npx skills add rainlib/full-stack-skill --skill history-manager

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from rainlib/full-stack-skill.

npx skills add rainlib/full-stack-skill

Browse all from rainlib/full-stack-skill

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Write, Bash(python *)

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,784 B
  • docs SUMMARY.md 233 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 11 installs

SKILL.md

History Manager

Provides iteration and phase state management for the full-stack workflow. Other skills invoke this skill to read/write docs/history.json instead of managing state directly.

Available Commands

All commands use the bundled cross-platform Python 3 script (macOS + Windows):

python ${CLAUDE_SKILL_DIR}/scripts/history_manager.py <command> [args]

init

Initialize docs/history.json if it does not exist.

python ${CLAUDE_SKILL_DIR}/scripts/history_manager.py init

status

Print the current iteration state, showing which phases are completed and which is next.

python ${CLAUDE_SKILL_DIR}/scripts/history_manager.py status

new-iter

Create a new iteration (e.g. iter-001), create its docs/iter-xxx/ directory, and set it as current.

python ${CLAUDE_SKILL_DIR}/scripts/history_manager.py new-iter

set-phase <phase> <phase_id>

Record a phase as completed: set its id in the current iteration and advance the state to the next phase.

python ${CLAUDE_SKILL_DIR}/scripts/history_manager.py set-phase requirements req-001

Valid phase names: requirements, technologyselection, technicalreview, programdesign, taskbreakdown, unittesting, codedevelopment, self_verification.

get-phase <phase>

Get the current phase id for a given phase (returns null if not yet started).

python ${CLAUDE_SKILL_DIR}/scripts/history_manager.py get-phase requirements

check-file <phase> <phase_id>

Check whether the document file for a given phase exists in the current iteration directory.

python ${CLAUDE_SKILL_DIR}/scripts/history_manager.py check-file requirements req-001

Returns exists:<path> or missing:<path>.

How Other Skills Should Use This

  1. Before starting a phase: Invoke history-manager to run get-phase <phase_name> and check-file to determine if the phase was already completed. Skip if both the id exists and the file exists.
  2. After completing a phase: Invoke history-manager to run set-phase <phasename> <phaseid> to record completion and advance the state machine.
  3. dev-workflow orchestrator: Invokes history-manager for init, new-iter, and status at startup, then delegates phase state updates to each phase skill (which in turn invokes history-manager).

Current Status

!python ${CLAUDESKILLDIR}/scripts/history_manager.py status