skills.rest
kamioj
kamiojCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-status

Report the current status of a spec-driven development change.

9|Updated May 27, 2026
Search Tags:#SDD workflow#spec-driven development#development status#workflow tracking#development management
One-click install
npx skills add https://github.com/kamioj/spec-workflow --skill spec-status-kamioj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-status
Source: https://github.com/kamioj/spec-workflow/tree/main/codex/skills/spec-status
Command: npx skills add https://github.com/kamioj/spec-workflow --skill spec-status-kamioj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The spec-status skill unit provides an overview of the current status of your spec-driven development (SDD) change, helping you understand the available artifacts and the next steps in the workflow.

Core Features & Use Cases

  • Change Status Overview: Report the current state of an SDD change, including open tasks, artifacts, and the recommended next step.
  • Artifact Check: Validate the presence of necessary artifacts like research, design, proposal, and verification documents.
  • Next Step Guidance: Direct the user to the next appropriate action in the workflow, whether it's completing a research phase, designing, proposing, applying changes, verifying, or archiving.

Quick Start

Run $spec-status to get a summary of the current status and the recommended next action for your SDD change.

Frequently Asked Questions about spec-status

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

FAQPage Schema
How do I check the status of my spec-driven development workflow?▼

To check your spec-driven development workflow status, run the status command to scan for research, design, proposal, and verification artifacts, reporting current progress and recommending the next workflow action.

What artifacts are required for a complete spec-driven development change?▼

A complete spec-driven development change requires the presence of research.md, proposal.md, and verify.md artifacts to provide a full picture of the research, proposal, and verification phases.

How do I know the next step in my SDD workflow?▼

To determine the next step in your SDD workflow, the status assessment evaluates existing artifacts and recommends the appropriate action: completing research, designing, proposing, applying changes, verifying, or archiving.

Can I track development management progress without all the SDD artifacts?▼

You can track development management progress without all artifacts. The status check assesses research, design, proposal, and verification documents individually, reporting the current state and recommending the next workflow step.

Does spec-driven development status tracking require any special environment setup?▼

Spec-driven development status tracking requires no special environment setup or dependencies. It operates by checking for the presence of standard workflow artifact files like research.md, proposal.md, and verify.md within your project directory.

Related Skills

Explore More Software Engineering Skills→
Soju06Soju06
2.6k

openspec-continue-change

Creates the next OpenSpec artifact from parsed status and templates via the openspec CLI.

Community
Advanced
SAPSAP
221

openspec-sync-specs

Merge delta specifications into main OpenSpec specs under openspec/specs.

Official
Advanced
rock-hurock-hu

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes with conflict resolution and status reports.

Community
Intermediate
nbarthelemynbarthelemy

autonomous-loop

Manage autonomous iterative development loops with checkpointing, cost tracking, and safety limits.

Community
Advanced