status

Display Specify change lifecycle, artifact completion, and task progress.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/augentic/specify --skill status-augentic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/augentic/specify/tree/main/plugins/spec/skills/status
Command: npx skills add https://github.com/augentic/specify --skill status-augentic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a clear overview of your Specify project's progress, helping you understand where you are in the development lifecycle and what the next steps should be.

Core Features & Use Cases

  • Lifecycle Status: See if your changes are proposing, proposed, applying, or complete.
  • Artifact Completion: Track the status of generated artifacts like proposals, specs, and tasks.
  • Task Progress: Monitor the completion of individual tasks within a change.
  • Use Case: Before starting your workday, you can quickly check the status of all active changes to prioritize your efforts and ensure nothing is blocked.

Quick Start

Run the status skill to see an overview of all active Specify changes.

Frequently Asked Questions about status

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

FAQPage Schema
How do I check the workflow status of my Specify changes?

To check your Specify workflow status, run the status skill to display active changes, artifact completion states like proposals and specs, and current task progress.

What is the best way to track artifact completion during a development lifecycle?

Tracking artifact completion is done by viewing the lifecycle status of your project, which shows whether generated proposals, specs, and tasks are complete or still in progress.

How can I monitor task progress for active project changes?

You can monitor task progress by viewing the status overview, which reports the completion state of individual tasks within each active Specify change.

Do I need a configuration file to view Specify lifecycle states?

Yes, you need a valid `.specify/config.yaml` file because the status skill requires it for schema resolution to accurately report your project's lifecycle and artifact statuses.

Why does my Specify status check fail to show artifact progress?

Your Specify status check fails when the `.specify/config.yaml` file is missing or invalid, preventing the required schema resolution needed to report accurate lifecycle and artifact statuses.