spec-status

Scan codebase specs and generate a dashboard-style implementation status report.

43|1|Updated Feb 19, 2024
One-click install
npx skills add https://github.com/dogganidhal/noddde --skill spec-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-status
Source: https://github.com/dogganidhal/noddde/tree/main/.claude/skills/spec-status
Command: npx skills add https://github.com/dogganidhal/noddde --skill spec-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tracking and reporting the implementation status of specs across a codebase to inform planning and accountability.

Core Features & Use Cases

  • Scan specs across core specs and integration tests to collect title, status, source_file, exports, and depends_on.
  • Determine per-spec pipeline position by examining available artifacts and test results.
  • Generate a consolidated status report suitable for sprint planning, standups, and roadmap updates.

Quick Start

Run the spec-status command to generate the current project-wide spec implementation report.

Frequently Asked Questions about spec-status

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

FAQPage Schema
How do I track spec implementation status across my codebase?

Pipeline status reporting maps each spec to its position in a 6-step pipeline by examining available artifacts and test results. It parses SKILL.md frontmatter to aggregate status, exports, dependencies, and source locations for reliable progress tracking.

What is the best way to generate a spec status report for sprint planning?

Generate a spec status report by running a single command that scans core specs and integration tests. It collects metadata and determines pipeline position to produce a consolidated summary suitable for standups, sprint planning, and roadmap updates.

Can I use spec status tracking for integration tests and core specs?

Yes, spec status tracking scans both core specs and integration tests to collect title, status, source file, exports, and dependencies. This ensures comprehensive project-wide coverage for reliable implementation reporting.

What limitations exist when tracking spec implementation progress across a project?

Tracking spec implementation progress relies on examining available artifacts and test results to determine pipeline position. If artifacts are missing or SKILL.md frontmatter is incomplete, the generated status report may lack accurate dependency and export mapping.