Automated summary
Displays the status of EARS specifications for a project (pending, in progress, done) with counts and metadata.
Strengths
- Clear visualization of spec progress
- Supports multiple projects and filtering by name
- Automatic extraction of metadata (title, priority, date)
Limitations
- Requires a specific folder structure (~/.claude/specs/<project>/{pending,doing,done})
- Only recognizes .ears.md files
- Does not directly update statuses
When tracking the progress of EARS technical specifications in a project.
For unstructured specifications or those stored in a different format.
Security analysis
SafeThe skill is a read-only bash script that reads and displays metadata from spec files under a fixed directory. It does not invoke destructive or external commands, does not process untrusted input dangerously, and handles file names safely.
No concerns found
How this analysis is madeExamples
/specs-status/specs-status my-project/specs-status allname: specs-status description: 현재 프로젝트의 EARS 스펙 상태 현황 표시 user-invocable: true
/specs-status [project|all]
현재 프로젝트 또는 지정된 프로젝트의 스펙 상태를 표시합니다.
Arguments
- 无参数 - 현재 디렉토리명을 프로젝트명으로 사용
- project-name - 지정된 프로젝트의 스펙만 표시
- all - 모든 프로젝트의 스펙을 표시
Implementation
specs-status() {
local SPECS_DIR="$HOME/.claude/specs"
local target_project="$1"
local projects=()
# Determine which projects to show
if [[ -z "$target_project" ]]; then
# No argument: use current directory basename
target_project="$(basename "$PWD")"
projects=("$target_project")
elif [[ "$target_project" == "all" ]]; then
# Show all projects
if [[ ! -d "$SPECS_DIR" ]]; then
echo "No specs directory found"
return 0
fi
# Get all subdirectories in specs directory
while IFS= read -r -d '' dir; do
projects+=("$(basename "$dir")")
done < <(find "$SPECS_DIR" -mindepth 1 -maxdepth 1 -type d -print0 | sort -z)
else
# Specific project
projects=("$target_project")
fi
# Exit if no projects found
if [[ ${#projects[@]} -eq 0 ]]; then
echo "No projects found"
return 0
fi
# Process each project
for project in "${projects[@]}"; do
local project_dir="$SPECS_DIR/$project"
echo ""
echo "## Specs Status: $project"
echo ""
# Check if project directory exists
if [[ ! -d "$project_dir" ]]; then
echo "No specs found for project $project"
continue
fi
# Track counts
local pending_count=0 doing_count=0 done_count=0
local pending_specs=() doing_specs=() done_specs=()
# Process each status directory
for status in pending doing done; do
local status_dir="$project_dir/$status"
if [[ ! -d "$status_dir" ]]; then
continue
fi
# Find all .ears.md files in status directory
while IFS= read -r -d '' spec_file; do
local spec_id
spec_id="$(basename "$spec_file" .ears.md)"
local title="" priority="" created=""
# Parse metadata from file using grep for safety
# Extract title (first line with # SPEC-ID: format, e.g., "# 001: Title")
title="$(grep -m1 "^# *[0-9]*: " "$spec_file" 2>/dev/null | sed 's/^# *[0-9]*: //')"
# Extract created date
created="$(grep '^-' "$spec_file" 2>/dev/null | grep 'created:' | sed 's/.*created: *//' | head -1)"
# Extract priority
priority="$(grep '^-' "$spec_file" 2>/dev/null | grep 'priority:' | sed 's/.*priority: *//' | head -1)"
# Default values if not found
[[ -z "$title" ]] && title="(no title)"
[[ -z "$priority" ]] && priority="medium"
[[ -z "$created" ]] && created="(unknown)"
case "$status" in
pending)
((pending_count++))
pending_specs+=("$spec_id|$title|$priority|$created")
;;
doing)
((doing_count++))
doing_specs+=("$spec_id|$title|$priority|$created")
;;
done)
((done_count++))
done_specs+=("$spec_id|$title|$priority|$created")
;;
esac
done < <(find "$status_dir" -maxdepth 1 -type f -name "*.ears.md" -print0 | sort -z)
done
# Display summary table
echo "| Status | Count |"
echo "|---------|-------|"
echo "| Pending | $pending_count |"
echo "| Doing | $doing_count |"
echo "| Done | $done_count |"
echo ""
# Check if any specs found
if [[ $pending_count -eq 0 && $doing_count -eq 0 && $done_count -eq 0 ]]; then
echo "No specs found for project $project"
continue
fi
# Display pending specs
if [[ $pending_count -gt 0 ]]; then
echo "### Pending"
for spec in "${pending_specs[@]}"; do
IFS='|' read -r spec_id spec_title spec_priority spec_created <<< "$spec"
echo "- **$spec_id**: $spec_title ($spec_priority) - created: $spec_created"
done
echo ""
fi
# Display doing specs
if [[ $doing_count -gt 0 ]]; then
echo "### Doing"
for spec in "${doing_specs[@]}"; do
IFS='|' read -r spec_id spec_title spec_priority spec_created <<< "$spec"
echo "- **$spec_id**: $spec_title ($spec_priority) - created: $spec_created"
done
echo ""
fi
# Display done specs
if [[ $done_count -gt 0 ]]; then
echo "### Done"
for spec in "${done_specs[@]}"; do
IFS='|' read -r spec_id spec_title spec_priority spec_created <<< "$spec"
echo "- **$spec_id**: $spec_title ($spec_priority) - created: $spec_created"
done
echo ""
fi
done
}
specs-status "$@"
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/ears-specs-status-viewer-mmk3nhcx/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/ears-specs-status-viewer-mmk3nhcx' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ears-specs-status-viewer-mmk3nhcx/download' --output '.skill-downloads/ears-specs-status-viewer-mmk3nhcx/SKILL.md.part' && mv '.skill-downloads/ears-specs-status-viewer-mmk3nhcx/SKILL.md.part' '.skill-downloads/ears-specs-status-viewer-mmk3nhcx/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/ears-specs-status-viewer-mmk3nhcx/SKILL.md' && test -s '.skill-downloads/ears-specs-status-viewer-mmk3nhcx/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/specs-status' && cp -R '.skill-downloads/ears-specs-status-viewer-mmk3nhcx' '.claude/skills/specs-status'Cursor
test -f '.skill-downloads/ears-specs-status-viewer-mmk3nhcx/SKILL.md' && test -s '.skill-downloads/ears-specs-status-viewer-mmk3nhcx/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/specs-status' && cp -R '.skill-downloads/ears-specs-status-viewer-mmk3nhcx' '.cursor/skills/specs-status'Codex
test -f '.skill-downloads/ears-specs-status-viewer-mmk3nhcx/SKILL.md' && test -s '.skill-downloads/ears-specs-status-viewer-mmk3nhcx/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/specs-status' && cp -R '.skill-downloads/ears-specs-status-viewer-mmk3nhcx' '.agents/skills/specs-status'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/ears-specs-status-viewer-mmk3nhcx'openskills read 'ears-specs-status-viewer-mmk3nhcx'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/ears-specs-status-viewer-mmk3nhcx/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.