Summarize EARS spec statuses by pending, doing, and done.
npx skills add https://github.com/SangIlMo/.dotfiles --skill specs-status
Please help me install this Agent Skill. Skill: specs-status Source: https://github.com/SangIlMo/.dotfiles/tree/main/.claude/skills/specs-status Command: npx skills add https://github.com/SangIlMo/.dotfiles --skill specs-status
This tool identifies and displays the current EARS spec status for one or all projects, helping teams track progress and identify bottlenecks at a glance.
Run the specs-status command from your shell to display the current EARS spec status for the active project.
High-intent search queries and answers about installing and using this skill.
You can track EARS spec status across all local projects by running the status command without targeting a specific project, which aggregates pending, doing, and done specifications into a single summary view.
EARS spec status tracking identifies and summarizes requirement specifications by organizing them into pending, doing, and done categories, providing clear counts and identifiers to visualize project progress.
To check pending and done specs for an active project, run the status command from your shell, which processes local spec directories and returns a concise summary of current specification progress.
Yes, it works with bash for local development project management by processing local spec directories directly from the shell and reporting EARS specification statuses without requiring external dependencies.
It gracefully handles missing EARS specs and unknown project directories by validating local paths, skipping missing data, and reporting clear status summaries without failing the entire status tracking operation.
pradeepmouliGenerate baseline-spec.md and current-state.md from repository analysis.
SangIlMoGenerate EARS specifications from feature descriptions and save them as .ears.md files.
CJ-1981Orchestrate SPEC workflow management with EARS format and Plan-Run-Sync integration.
snicmakinoExtract project briefs and steering context into EARS-format requirements.
