agentleFS
Sign inStart free
RainLibRainLib/full-stack-skill/.claude/skills/history-manager/SKILL.md

history-manager

Skill0 starsChanged 8 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 14
  2. Very specific:

    Create a new iteration (e.g.

    line 38
  3. Distinctive:

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

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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, technology_selection, technical_review, program_design, task_breakdown, unit_testing, code_development, 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 <phase_name> <phase_id> 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 ${CLAUDE_SKILL_DIR}/scripts/history_manager.py status

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free