skills.rest
benjaminshoemaker
benjaminshoemakerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

populate-state

Generate .claude/phase-state.json from EXECUTION_PLAN.md and git history.

39|5|Updated Dec 28, 2025
Search Tags:#workflow#git history#orchestrator#state#EXECUTION_PLAN#phase-state#populate
One-click install
npx skills add https://github.com/benjaminshoemaker/ai_coding_project_base --skill populate-state
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: populate-state
Source: https://github.com/benjaminshoemaker/ai_coding_project_base/tree/main/.claude/skills/populate-state
Command: npx skills add https://github.com/benjaminshoemaker/ai_coding_project_base --skill populate-state

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates recovering orchestration progress by building the phase-state.json file from the EXECUTION_PLAN.md and git history, enabling teams to resume work after context loss or when joining an existing project.

Core Features & Use Cases

  • Parse the execution plan to determine total phases and tasks.
  • Cross-check git history to determine completion and activity.
  • Generate the standardized phase-state JSON used by the orchestrator.
  • Use case: start a new phase on an existing project or recover state after a repository clone.

Quick Start

Run the populate-state command from your project directory to generate the phase-state.json file in the .claude folder.

Frequently Asked Questions about populate-state

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

FAQPage Schema
How do I recover orchestrator phase-state.json from git history?▼

You can recover phase-state.json by parsing your EXECUTION_PLAN.md and cross-checking git history to derive per-phase and per-task status, generating a standardized state file in the .claude folder.

Can I restore orchestration progress when joining an existing project?▼

Yes, running the populate-state command from your project directory builds phase-state.json from the existing execution plan and git history, allowing you to resume orchestrator work on a cloned repository.

What should I do if my phase-state.json is missing or corrupted?▼

If phase-state.json is missing or corrupted, you can regenerate it by parsing the execution plan and git history to reconstruct per-phase and per-task completion status for the orchestrator.

How does the orchestrator synchronize state with actual git progress?▼

The orchestrator synchronizes state by parsing the execution plan to determine total phases and tasks, then cross-checking git history to determine completion and activity, outputting a standardized phase-state JSON file.

When do I need to regenerate phase-state.json for workflow orchestration?▼

You need to regenerate phase-state.json when starting to use the orchestrator on an existing project, when the file is missing or corrupted, or when your tracked state has drifted from actual git progress.

Does populate-state work without external dependencies?▼

Yes, the skill operates with no external dependencies, relying solely on your project's EXECUTION_PLAN.md and git history to generate the phase-state.json file in the .claude directory.

Related Skills

Explore More Software Engineering Skills→
RussianLioNRussianLioN
1

rollback-changes

Parse a changes log file to restore files, revert commands, and undo Git commits.

Community
Advanced
n0rvynn0rvyn
1

execute-plan

Execute verified implementation plan tasks in deterministic 5-task batches.

Community
Advanced
danielkhigaydanielkhigay

run-phase

Orchestrate builder and evaluator agents to execute a Gaz blueprint phase.

Community
Advanced
dstanberrydstanberry
7

conventional-commit

Inspect staged and unstaged changes to generate and execute conventional commits.

Community
Intermediate