Display development workflow status

VerifiedSafe

Displays the current development workflow status (phases with statuses, durations, available commands) by reading a JSON state file. Helps you quickly see your progress in the workflow.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#workflow-status#development-workflow#state-tracking#dev-progress

Recommended for

Automated summary

Displays the current development workflow state (current, completed, or pending phases) from a state file.

Strengths

  • Provides a clear overview of progress with status for each phase.
  • Shows elapsed or total durations for each step.
  • Helps resume interrupted work easily.

Limitations

  • Requires the .claude/data/.dev-workflow-state.json file to exist (workflow must have been started).
  • Does not support parallel or custom workflows.
  • Display is limited to the predefined workflow phases.
When to use it

When you need to check project progress or resume a task after an interruption.

When not to use it

If no workflow is active or for tasks that don't need structured tracking.

Security analysis

Safe
Quality score90/100

The skill only uses Read and Glob, no destructive commands, no network access, no code execution. It reads a fixed local file and displays text. The /output-style command is an internal agent instruction.

No concerns found

How this analysis is made

Examples

Check current workflow status
/dev:status

name: dev:status description: Affiche le workflow et l'étape courante model: haiku allowed-tools: [Read, Glob] version: 1.0.0 license: MIT

Configuration de sortie

Instructions à Exécuter

IMPORTANT : Exécute ce workflow étape par étape :

IMPORTANT : Cette skill affiche un statut court et nécessite un format de sortie spécifique.

Lis le frontmatter de cette skill. Si un champ output-style est présent, exécute immédiatement :

/output-style <valeur-du-champ>

Note : Une fois que le champ output-style sera supporté nativement par Claude Code, cette instruction pourra être supprimée.

Output-style requis : ultra-concise

Objectif

Afficher l'état actuel du workflow de développement pour que l'utilisateur sache où il en est.

Instructions

  1. Chercher un fichier .claude/data/.dev-workflow-state.json dans le répertoire courant
  2. Si le fichier existe, lire l'état du workflow
  3. Afficher le plan avec les statuts de chaque phase

Format de sortie

🔄 Workflow de développement

  {status} 0. Discover   - Comprendre le besoin     {duration}
  {status} 1. Explore    - Explorer codebase        {duration}
  {status} 2. Clarify    - Questions clarification  {duration}
  {status} 3. Design     - Proposer architectures   {duration}
  {status} 4. Plan       - Générer specs            {duration}
  {status} 5. Code       - Implémenter              {duration}
  {status} 6. Review     - QA complète              {duration}
  {status} 7. Summary    - Résumé final             {duration}

📋 Feature: "{feature_description}"
📁 Plan: {plan_path}
⏱️ Temps total: {total_duration}

Affichage des durées

Pour chaque phase :

  • Si completed avec durationMs → afficher ({formatted_duration})
  • Si in_progress avec startedAt → afficher (en cours depuis {elapsed})
  • Si pas de timing → ne rien afficher

Format de durée

Formater les durées de manière lisible :

  • < 60s → {X}s (ex: 45s)
  • < 60min → {X}m {Y}s (ex: 2m 30s)
  • >= 60min → {X}h {Y}m (ex: 1h 15m)

Légende des statuts

  • ✅ - Phase complétée
  • 🔵 - Phase en cours (ajouter ← En cours à la fin)
  • ⬜ - Phase à faire

Si aucun workflow actif

Afficher :

📭 Aucun workflow actif

Pour démarrer un nouveau workflow :
  /dev:feature <description>

Ou exécuter les phases individuellement :
  /dev:discover <description>

Commandes disponibles

Lister les commandes du workflow :

📖 Commandes disponibles

Workflow complet :
  /dev:feature <desc>  - Lance toutes les phases automatiquement

Phases individuelles :
  /dev:discover <desc> - 0. Comprendre le besoin
  /dev:explore         - 1. Explorer le codebase
  /dev:clarify         - 2. Questions de clarification
  /dev:design          - 3. Proposer architectures
  /dev:plan            - 4. Générer le plan
  /dev:code [plan]     - 5. Implémenter
  /dev:review          - 6. QA complète
  /dev:summary         - 7. Résumé final

Utilitaires :
  /dev:debug <error>   - Analyser une erreur
  /dev:log <fichier>   - Ajouter LoggableInterface

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/display-development-workflow-status-mm8o52fa/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/display-development-workflow-status-mm8o52fa' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/display-development-workflow-status-mm8o52fa/download' --output '.skill-downloads/display-development-workflow-status-mm8o52fa/SKILL.md.part' && mv '.skill-downloads/display-development-workflow-status-mm8o52fa/SKILL.md.part' '.skill-downloads/display-development-workflow-status-mm8o52fa/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/display-development-workflow-status-mm8o52fa/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills