agentleFS
peopleforresterpeopleforrester/claude-dotfiles/skills/workflow/spec-status/SKILL.md

spec-status

Skill3 starsChanged 8 months agoMITView on GitHub

Show specification progress and next tasks

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read all .spec/*.spec.md files and display summary:

    line 18
  2. Very specific:

    Read .spec/{slug}.spec.md and .spec/{slug}.tasks.md:

    line 34
  3. Distinctive:

    If the user requests JSON format:

    line 100

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/spec-status

Display the current status of one or all specifications, including task progress, completion percentage, and recommended next actions.

Arguments

  • $ARGUMENTS — Optional: spec slug to show details for a specific spec

Process

Without Arguments — List All Specs

Read all .spec/*.spec.md files and display summary:

## Active Specifications

| Spec | Status | Progress | Next Task |
|------|--------|----------|-----------|
| user-auth | active | 5/12 (42%) | 2.3 Implement logout |
| api-rate-limit | draft | 0/8 (0%) | Review spec |
| payment-integration | completed | 15/15 (100%) | — |

**Total:** 3 specs, 20/35 tasks complete (57%)

With Spec Slug — Show Details

Read .spec/{slug}.spec.md and .spec/{slug}.tasks.md:

## Spec: User Authentication

**Status:** active
**Created:** 2026-02-05
**Updated:** 2026-02-05
**Progress:** 5/12 tasks (42%)

### Task Status

#### Phase 1: Foundation ✓ Complete
- [x] 1.1 Create database migration for users table
- [x] 1.2 Create database migration for sessions table
- [x] 1.3 Create User model with repository pattern

#### Phase 2: Core Implementation (In Progress)
- [x] 2.1 Implement AuthService.register()
- [x] 2.2 Implement AuthService.login()
- [ ] 2.3 Implement AuthService.logout() ← **NEXT**
- [ ] 2.4 Create auth middleware

#### Phase 3: Hardening
- [ ] 3.1 Add rate limiting
- [ ] 3.2 Add input validation
- [ ] 3.3 Add comprehensive tests

### Progress Bar
[████████░░░░░░░░░░░░] 42%

### Recent Activity
- 2026-02-05: Completed task 2.2 (login implementation)
- 2026-02-05: Completed task 2.1 (register implementation)

### Recommended Actions
1. Continue with task 2.3: Implement AuthService.logout()
2. Run `/spec-task user-auth 2.3 start` to begin
3. After completing Phase 2, run `/verify` before Phase 3

Status Values

StatusMeaning
draftSpec created but not yet approved for implementation
activeImplementation in progress
completedAll tasks done and verified
archivedSpec retained for reference but no longer active

Progress Calculation

Progress is calculated from the tasks file:

  • Count [x] (completed) vs [ ] (pending) checkboxes
  • Percentage = completed / total * 100
  • Round to nearest integer

Output Formats

Summary View (no args)

Compact table of all specs with key metrics.

Detail View (with slug)

Full task breakdown with progress bars and recommendations.

JSON Output (for scripting)

If the user requests JSON format:

{
  "spec": "user-auth",
  "status": "active",
  "created": "2026-02-05",
  "updated": "2026-02-05",
  "progress": {
    "completed": 5,
    "total": 12,
    "percentage": 42
  },
  "nextTask": {
    "id": "2.3",
    "title": "Implement AuthService.logout()"
  }
}

Error Handling

ConditionResponse
No .spec/ directory"No specs found. Create one with /spec-new"
Spec slug not found"Spec '{slug}' not found. Available: [list]"
Tasks file missing"Tasks file missing for '{slug}'. Regenerate with planner agent."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.