ze-progress

Identify a Ze spec's lifecycle stage and recommend the next command.

50|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/ze-software/ze --skill ze-progress
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ze-progress
Source: https://github.com/ze-software/ze/tree/main/.codex/skills/ze-progress
Command: npx skills add https://github.com/ze-software/ze --skill ze-progress

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps operators quickly determine where a Ze spec sits in the lifecycle and what the next action should be, surfacing concrete evidence from the spec and session data.

Core Features & Use Cases

  • Tracks lifecycle stages: implementation evidence, open deferrals, post-edit review, verification readiness, and learned-summary closure.
  • Reads the selected spec from tmp/session/selected-spec and analyzes tests, ACs, file lists, and status metadata to decide current state.
  • Use Case: A developer asks for the current status of a spec to decide next steps in the review and closure process.

Quick Start

Run the ze-progress command after selecting a spec to display its current lifecycle stage and the recommended next action

Frequently Asked Questions about ze-progress

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

FAQPage Schema
How do I track the lifecycle status of a spec during software review?

To track spec lifecycle status, the skill analyzes the selected spec from session data, evaluates implementation evidence, open deferrals, and verification readiness, then returns the current stage and the next recommended action.

How do I determine the next action for a spec in the verification phase?

To determine the next action for a spec in the verification phase, the skill evaluates post-edit review readiness and open deferrals against spec metadata, returning a single concrete recommended command to advance the workflow.

Does spec lifecycle management require a specific session file format?

Spec lifecycle management requires the selected spec to be stored in the tmp/session/selected-spec file, which the skill reads to analyze tests, acceptance criteria, and status metadata for evidence.

What is the best way to automate spec review and closure workflows?

The best way to automate spec review workflows is to run the ze-progress command after selecting a spec, which analyzes lifecycle evidence and outputs the single next recommended action for the closure process.

Why does spec progress tracking return only one recommended next command?

Spec progress tracking returns only one recommended next command to satisfy the evaluation sequence, ensuring the operator receives a single concrete action to advance the spec through implementation, review, or verification stages.