crafter-status

Resolve and display STATE.md contents from .crafter or .planning paths.

2|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/richardriman/crafter --skill crafter-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crafter-status
Source: https://github.com/richardriman/crafter/tree/main/skills/crafter-status
Command: npx skills add https://github.com/richardriman/crafter --skill crafter-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve and present the current state of a Crafter-powered project by locating STATE.md in the recommended location, with a fallback to the legacy .planning/STATE.md and guidance to migrate when needed.

Core Features & Use Cases

  • Resolve the active project state by reading STATE.md from .crafter/STATE.md, preferring the modern path and offering a migration prompt if only the legacy path exists.
  • Read and display the full contents of STATE.md, enabling a concise, human-readable summary of current work, completed tasks, and blockers.
  • Generate a brief, conversational status narrative covering what is being worked on, what was completed, what comes next, and any known issues.

Quick Start

Read the resolved STATE.md file and print its full contents, then summarize it concisely.

Frequently Asked Questions about crafter-status

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

FAQPage Schema
How do I check my Claude Code project status from a STATE.md file?

Project status is checked by locating and reading the STATE.md file, typically stored in the .crafter/ directory, and displaying its full contents to summarize active tasks and blockers.

What is the best way to track engineering workflow state for active tasks and blockers?

Tracking engineering workflow state involves maintaining a STATE.md file that records recent completions and blockers, which can then be resolved and displayed as a concise project status summary.

How do I migrate STATE.md from a legacy .planning directory to .crafter?

Migrating STATE.md involves resolving the legacy .planning/STATE.md path, recognizing it as a fallback, and following migration guidance to move the project state to the modern .crafter/STATE.md location.

Does Crafter status resolution work with legacy project tracking paths?

Yes, Crafter status resolution works with legacy paths by falling back to .planning/STATE.md if the modern .crafter/STATE.md file is not found, while prompting the user to migrate.

Why is my project state summary not showing recent completions and blockers?

The project state summary will not display correctly if the STATE.md file is missing from both the primary .crafter/ directory and the fallback .planning/ directory, preventing path resolution.