How do I install the Status skill?

Run npx skillmds@latest add cwijayasundara/status in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Status safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Status?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Status free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Status?

cwijayasundara (@cwijayasundara) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Status by cwijayasundara — Agent Skill

Name: Status
Author: cwijayasundara

File contents

Pipeline status

A read-only view of where the SDLC pipeline is right now. It aggregates the files the harness already writes (claude-progress.txt, .claude/state/*, features.json, specs/stories/dependency-graph.md, .claude/runs/*.jsonl) into one normalized snapshot and renders it. It writes no state and makes no network calls.

Design: docs/internal/PIPELINE_PROGRESS_PROPOSAL_2026-06-21.md.

Usage

Run the script directly — it works inside or outside a Claude session, so you can watch a running /auto from a second terminal:

# one-shot snapshot (default)
node .claude/scripts/pipeline-status.js status

# live view, redraws every 3s (override with --interval SECONDS)
node .claude/scripts/pipeline-status.js watch

# unified step timeline for the current session (Devin's Progress tab)
node .claude/scripts/pipeline-status.js timeline

# machine-readable — the deterministic contract for CI / e2e / scripts
node .claude/scripts/pipeline-status.js status --json

npm run status is a shortcut for status.

What it reports

status prints: phase · health (on_track / blocked / failing) · group progress (done / current / remaining) · features passing X/Y · coverage vs baseline · current iteration · pending reviews · navigation freshness/token savings · context-cache entries/token savings · next action · blocked stories.

--json emits the full snapshot object (schema_version: 1). Treat that object — not the text rendering — as the stable interface; the text layout may change.

When to use

"Where is the build?" during or after an /auto / /build run.
Scripting a gate or e2e assertion off --json (e.g. assert health !== "failing").
Reviewing what steps ran this session via timeline.

This is a reporting surface only. It does not advance the pipeline — use /auto, /build, /gate, etc. for that.

---name: statusdescription: Show SDLC pipeline progress — a one-shot snapshot, a live watch, or a step timeline. Read-only; aggregates the state the harness already writes. CLI-friendly (Devin-style status/watch/timeline with --json).---# Pipeline statusA read-only view of where the SDLC pipeline is right now. It aggregates the filesthe harness already writes (`claude-progress.txt`, `.claude/state/*`,`features.json`, `specs/stories/dependency-graph.md`, `.claude/runs/*.jsonl`) intoone normalized snapshot and renders it. It writes no state and makes no networkcalls.Design: `docs/internal/PIPELINE_PROGRESS_PROPOSAL_2026-06-21.md`.## UsageRun the script directly — it works inside or outside a Claude session, so you canwatch a running `/auto` from a second terminal:```bash# one-shot snapshot (default)node .claude/scripts/pipeline-status.js status# live view, redraws every 3s (override with --interval SECONDS)node .claude/scripts/pipeline-status.js watch# unified step timeline for the current session (Devin's Progress tab)node .claude/scripts/pipeline-status.js timeline# machine-readable — the deterministic contract for CI / e2e / scriptsnode .claude/scripts/pipeline-status.js status --json````npm run status` is a shortcut for `status`.## What it reports`status` prints: phase · health (`on_track` / `blocked` / `failing`) · groupprogress (`done / current / remaining`) · features passing X/Y · coverage vsbaseline · current iteration · pending reviews · navigation freshness/tokensavings · context-cache entries/token savings · next action · blocked stories.`--json` emits the full snapshot object (`schema_version: 1`). Treat that object —not the text rendering — as the stable interface; the text layout may change.## When to use- "Where is the build?" during or after an `/auto` / `/build` run.- Scripting a gate or e2e assertion off `--json` (e.g. assert `health !== "failing"`).- Reviewing what steps ran this session via `timeline`.This is a reporting surface only. It does not advance the pipeline — use `/auto`,`/build`, `/gate`, etc. for that.

Frequently asked questions

Status