specs-status — specs-status install specs-status, dotfiles, community, specs-status install, ide skills, specs-status command-line tool, project specs management, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Perfect for Development Agents needing project specification management and command-line interface capabilities. specs-status is a command-line tool that displays the specs status of a project, allowing developers to manage and view project specifications efficiently.

Features

Displays specs status of the current project or a specified project
Supports command-line arguments for project-name and all projects
Uses the basename of the current directory as the project name if no argument is provided
Stores project specs in the $HOME/.claude/specs directory
Allows developers to view specs for all projects using the 'all' argument

# Core Topics

SangIlMo SangIlMo
[0]
[0]
Updated: 3/8/2026

Agent Capability Analysis

The specs-status skill by SangIlMo is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance. Optimized for specs-status install, specs-status command-line tool, project specs management.

Ideal Agent Persona

Perfect for Development Agents needing project specification management and command-line interface capabilities.

Core Value

Empowers agents to view project specs using a command-line interface, supporting project management through specs status display, and provides flexibility with options to view specs for the current project, a specified project, or all projects, utilizing bash scripting and directory navigation.

Capabilities Granted for specs-status

Displaying specs status for the current project
Viewing specs for a specified project
Listing specs for all projects

! Prerequisites & Limits

  • Requires bash environment
  • Limited to project specs management
  • No graphical user interface support
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

specs-status

Install specs-status, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly

/specs-status [project|all]

현재 프로젝트 또는 지정된 프로젝트의 스펙 상태를 표시합니다.

Arguments

  • 无参数 - 현재 디렉토리명을 프로젝트명으로 사용
  • project-name - 지정된 프로젝트의 스펙만 표시
  • all - 모든 프로젝트의 스펙을 표시

Implementation

bash
1specs-status() { 2 local SPECS_DIR="$HOME/.claude/specs" 3 local target_project="$1" 4 local projects=() 5 6 # Determine which projects to show 7 if [[ -z "$target_project" ]]; then 8 # No argument: use current directory basename 9 target_project="$(basename "$PWD")" 10 projects=("$target_project") 11 elif [[ "$target_project" == "all" ]]; then 12 # Show all projects 13 if [[ ! -d "$SPECS_DIR" ]]; then 14 echo "No specs directory found" 15 return 0 16 fi 17 # Get all subdirectories in specs directory 18 while IFS= read -r -d '' dir; do 19 projects+=("$(basename "$dir")") 20 done < <(find "$SPECS_DIR" -mindepth 1 -maxdepth 1 -type d -print0 | sort -z) 21 else 22 # Specific project 23 projects=("$target_project") 24 fi 25 26 # Exit if no projects found 27 if [[ ${#projects[@]} -eq 0 ]]; then 28 echo "No projects found" 29 return 0 30 fi 31 32 # Process each project 33 for project in "${projects[@]}"; do 34 local project_dir="$SPECS_DIR/$project" 35 36 echo "" 37 echo "## Specs Status: $project" 38 echo "" 39 40 # Check if project directory exists 41 if [[ ! -d "$project_dir" ]]; then 42 echo "No specs found for project $project" 43 continue 44 fi 45 46 # Track counts 47 local pending_count=0 doing_count=0 done_count=0 48 local pending_specs=() doing_specs=() done_specs=() 49 50 # Process each status directory 51 for status in pending doing done; do 52 local status_dir="$project_dir/$status" 53 54 if [[ ! -d "$status_dir" ]]; then 55 continue 56 fi 57 58 # Find all .ears.md files in status directory 59 while IFS= read -r -d '' spec_file; do 60 local spec_id 61 spec_id="$(basename "$spec_file" .ears.md)" 62 local title="" priority="" created="" 63 64 # Parse metadata from file using grep for safety 65 # Extract title (first line with # SPEC-ID: format, e.g., "# 001: Title") 66 title="$(grep -m1 "^# *[0-9]*: " "$spec_file" 2>/dev/null | sed 's/^# *[0-9]*: //')" 67 # Extract created date 68 created="$(grep '^-' "$spec_file" 2>/dev/null | grep 'created:' | sed 's/.*created: *//' | head -1)" 69 # Extract priority 70 priority="$(grep '^-' "$spec_file" 2>/dev/null | grep 'priority:' | sed 's/.*priority: *//' | head -1)" 71 72 # Default values if not found 73 [[ -z "$title" ]] && title="(no title)" 74 [[ -z "$priority" ]] && priority="medium" 75 [[ -z "$created" ]] && created="(unknown)" 76 77 case "$status" in 78 pending) 79 ((pending_count++)) 80 pending_specs+=("$spec_id|$title|$priority|$created") 81 ;; 82 doing) 83 ((doing_count++)) 84 doing_specs+=("$spec_id|$title|$priority|$created") 85 ;; 86 done) 87 ((done_count++)) 88 done_specs+=("$spec_id|$title|$priority|$created") 89 ;; 90 esac 91 done < <(find "$status_dir" -maxdepth 1 -type f -name "*.ears.md" -print0 | sort -z) 92 done 93 94 # Display summary table 95 echo "| Status | Count |" 96 echo "|---------|-------|" 97 echo "| Pending | $pending_count |" 98 echo "| Doing | $doing_count |" 99 echo "| Done | $done_count |" 100 echo "" 101 102 # Check if any specs found 103 if [[ $pending_count -eq 0 && $doing_count -eq 0 && $done_count -eq 0 ]]; then 104 echo "No specs found for project $project" 105 continue 106 fi 107 108 # Display pending specs 109 if [[ $pending_count -gt 0 ]]; then 110 echo "### Pending" 111 for spec in "${pending_specs[@]}"; do 112 IFS='|' read -r spec_id spec_title spec_priority spec_created <<< "$spec" 113 echo "- **$spec_id**: $spec_title ($spec_priority) - created: $spec_created" 114 done 115 echo "" 116 fi 117 118 # Display doing specs 119 if [[ $doing_count -gt 0 ]]; then 120 echo "### Doing" 121 for spec in "${doing_specs[@]}"; do 122 IFS='|' read -r spec_id spec_title spec_priority spec_created <<< "$spec" 123 echo "- **$spec_id**: $spec_title ($spec_priority) - created: $spec_created" 124 done 125 echo "" 126 fi 127 128 # Display done specs 129 if [[ $done_count -gt 0 ]]; then 130 echo "### Done" 131 for spec in "${done_specs[@]}"; do 132 IFS='|' read -r spec_id spec_title spec_priority spec_created <<< "$spec" 133 echo "- **$spec_id**: $spec_title ($spec_priority) - created: $spec_created" 134 done 135 echo "" 136 fi 137 done 138} 139 140specs-status "$@"

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is specs-status?

Perfect for Development Agents needing project specification management and command-line interface capabilities. specs-status is a command-line tool that displays the specs status of a project, allowing developers to manage and view project specifications efficiently.

How do I install specs-status?

Run the command: npx killer-skills add SangIlMo/.dotfiles/specs-status. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for specs-status?

Key use cases include: Displaying specs status for the current project, Viewing specs for a specified project, Listing specs for all projects.

Which IDEs are compatible with specs-status?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for specs-status?

Requires bash environment. Limited to project specs management. No graphical user interface support.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add SangIlMo/.dotfiles/specs-status. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use specs-status immediately in the current project.

Related Skills

Looking for an alternative to specs-status or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

149.6k
0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

138.4k
0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI