New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Status

by atelier-fashion in atelier-fashion/adlc-toolkit

Show current state of all ADLC work across the project. An agent skill from atelier-fashion/adlc-toolkit.

MITAuto-check passed

Install Status

skills CLI
$ npx skills add atelier-fashion/adlc-toolkit --skill status -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install atelier-fashion/adlc-toolkit status --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/atelier-fashion/adlc-toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/status .claude/skills/status && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
status
GitHub stars
171
Token cost
~2.3k tokens
SKILL.md length
1,067 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

Show current state of all ADLC work across the project. An agent skill from atelier-fashion/adlc-toolkit.

  • Works in 4 steps: Scan All ADLC Artifacts → Build Status Report → Apply Filters (if provided) → …
  • SKILL.md covers Ethos, Context, Input and Prerequisites, plus 1 more section
  • Calls git and python3

What it does

Status is an agent skill from atelier-fashion/adlc-toolkit. Show current state of all ADLC work across the project

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Shared SDLC skills and templates for Claude Code. The licence is MIT.

Example prompts

  • “/status”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Scan All ADLC Artifacts
  2. Build Status Report
  3. Apply Filters (if provided)
  4. Highlight Action Items

What it can do on your machine

Read from SKILL.md and the folder at commit 3a48c27. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Status loads about 2.3k tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 1,067 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~15
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from atelier-fashion/adlc-toolkit at commit 3a48c27, republished under its MIT licence (© atelier-fashion). 1,067 words, ~2,337 tokens.

Download SKILL.mdSave it as .claude/skills/status/SKILL.md (or your agent's skills folder).
name
status
description
Show current state of all ADLC work across the project
argument-hint
Optional filter (e.g., REQ-xxx, "in-progress", "bugs")

/status — ADLC Status Dashboard

You are generating a status report of all ADLC work in the current project.

Ethos

!test -s .adlc/ETHOS.md && cat .adlc/ETHOS.md || echo No ethos found — run /init to vendor .adlc/ETHOS.md

See also /manifest — /status reads this local checkout; /manifest derives in-flight work across all sessions from the remote (open PRs + pushed feat/REQ-* branches), with an advisory overlap report. Use /manifest to see what other people are working on before you start.

Context

  • Specs directory: !ls .adlc/specs/ || echo No specs found
  • Bugs directory: !ls .adlc/bugs/ || echo No bugs found
  • Current branch: !git branch --show-current || echo Not a git repo

Input

Filter: $ARGUMENTS

Prerequisites

Before proceeding, verify that the .adlc/specs/ directory exists (this skill reads requirement and task frontmatter from there). .adlc/bugs/ and live pipeline-state.json files are read when present but are not required. If .adlc/specs/ does not exist, stop and tell the user: "The .adlc/ structure hasn't been initialized. Run /init first to set up the project context."

Instructions

Step 1: Scan All ADLC Artifacts

Detect repository mode — read .adlc/config.yml. If it declares more than one entry under repos:, this is cross-repo mode; otherwise single-repo mode.

  1. Read all requirement.md files under .adlc/specs/REQ-*/ (this repo)
  2. Read all task files under .adlc/specs/REQ-*/tasks/
  3. Read all bug reports under .adlc/bugs/ — including the optional introduced_by / attribution frontmatter, which supplies the Incident Attribution section below
  4. Read all pipeline-state.json files under .adlc/specs/REQ-*/ for live pipeline progress
  5. Also check for nested .adlc/ directories (e.g., api/.adlc/)
  6. Extract frontmatter (id, title, status, updated) from each artifact

Cross-repo scan (only in cross-repo mode): for every sibling declared in .adlc/config.yml:

  • Resolve the sibling's absolute path from repos[<id>].path
  • Read <sibling-path>/.adlc/specs/REQ-*/pipeline-state.json to find REQs where the sibling was primary. Any of those that have a repos block listing the current repo as touched: true represents cross-repo work that affects us but originates elsewhere.
  • Capture REQ id, primary repo id, state file path, and current phase for the cross-repo report section (Step 2).

Cross-repo scan is read-only — /status never modifies sibling repos.

Step 2: Build Status Report

Organize the report as follows:

Requirements Summary Table
IDTitleStatusTasksProgress

For each requirement:

  • Count total tasks and completed tasks
  • Calculate progress percentage
  • Show status from frontmatter
Active Pipelines

If any pipeline-state.json files exist with "completed": false, show:

REQPrimaryBranchCurrent PhaseStartedLast Phase CompletedTouched Repos
  • Primary column: which repo the REQ originates from (the repo holding the state file). In single-repo mode this is always the current repo; omit the column if no cross-repo config exists.
  • Touched Repos column: only populated in cross-repo mode — list every repo id from the state file's repos block where touched: true, with a ✓ for merged and a clock for in-progress.

Phase names: 0=Worktree, 1=Validate Spec, 2=Architect, 3=Validate Tasks, 4=Implement, 5=Verify, 6=Create PR, 7=PR Cleanup, 7.5=Canary, 8=Wrapup

Separate the genuinely-active from the never-closed (BUG-193). A completed:false state file is not proof of an active pipeline — a run that merged its PR but skipped the Phase 8 close-out leaves the same signature, and those files never self-correct. Before listing a REQ as active, test these offline invariants and report any that trip under a Stale Pipeline State heading instead, with the reconciliation as the recommended action:

SignatureReading
completed:false but every touched repo has merged:truemerged; close-out skipped
completed:false, currentPhase:8, 7 ∈ completedPhasesreached the final phase and stopped — verify the PR, then close
completed:true but 8 ∉ completedPhases, or currentPhase ≠ 8, or a touched repo still merged:falseclosed with a partial record
the requirement's frontmatter says status: completethe REQ is done; a completed:false state file contradicts it

Confirm against the forge before reconciling — gh pr view <prNumber> --json state,mergedAt — and write the real merge commit and timestamp into the phase-8 phaseHistory entry rather than a synthesized one. Never infer a merge from the requirement's status alone.

Show full SKILL.md (431 more words)Show less
Cross-Repo Activity (cross-repo mode only)

If the cross-repo scan found REQs originating elsewhere that touch this repo, surface them separately so the user sees inbound cross-repo work without losing context on local REQs:

REQPrimary (origin)Current PhaseThis Repo's RoleBranch Here
REQ-091api4/8 Implementsibling (touched)feat/REQ-091-...

"Branch Here" is detected by checking git -C <this-repo> branch --list feat/REQ-xxx-*. If absent, the REQ hasn't reached Phase 4 yet or this repo isn't touched after all.

In-Progress Work

List any artifacts with status in-review, approved, or in-progress tasks:

  • Which requirement they belong to
  • What phase they're in (spec, architecture, tasks, implementation)
  • What's blocking progress (if any)
Open Bugs
IDTitleSeverityStatusUpdated
Incident Attribution

Which shipped REQs have produced incidents (REQ-593). Derived at read time by scanning .adlc/bugs/ frontmatter — the reverse edge is never stored in a REQ spec, because a stored backlink rots silently when an artifact is moved or renumbered (BR-4, LESSON-019).

Source the partial and call it in the same fenced block (the cross-fence-fn rule):

bash
if [ -f .adlc/partials/attribution.sh ]; then . .adlc/partials/attribution.sh; else . ~/.claude/skills/partials/attribution.sh; fi
# Emits one "BUG-id<TAB>REQ-id" line per attributed edge; add a REQ id as a second
# argument to filter to that REQ's incidents. Strictly read-only.
adlc_attr_bugs_with_attribution "$PWD"
REQIncidentsBugs

One row per REQ that has at least one attributed bug, with the count and the BUG ids. A bug carrying no introduced_by is simply absent — it is not an error. When nothing is attributed, print No attributed incidents yet. rather than an empty table or a warning.

This section reads .adlc/bugs/ only. It modifies no file, and in particular opens nothing under .adlc/specs/**.

Conflict Resolutions

Which pipeline runs resolved a merge or rebase conflict mid-run, and whether the resolution was verified (BUG-212). Read from each spec's pipeline-state.json conflictsResolved array — the record written at the moment of resolution, not the runner's narrative. Strictly read-only; a state file without the key is simply a run that resolved nothing.

bash
# One row per recorded resolution. `conflictsResolved` is optional and additive:
# a state file without it parses unchanged (absent == none resolved).
for f in .adlc/specs/REQ-*/pipeline-state.json; do
  [ -f "$f" ] || continue
  python3 - "$f" <<'PYEOF'
import json, sys, os
p = sys.argv[1]; req = os.path.basename(os.path.dirname(p)).split("-", 2)[:2]
try:
    s = json.load(open(p))
except (OSError, ValueError):
    sys.exit(0)  # unreadable state is /status Step 1's concern, not this section's
for e in s.get("conflictsResolved") or []:
    print("\t".join(["-".join(req), str(e.get("phase", "?")), ",".join(e.get("files") or []),
                     str(e.get("resolvedBy", "?")), str(e.get("strategy", "?")),
                     "yes" if e.get("verified") else "no", str(e.get("resolvedAt", "?"))]))
PYEOF
done
REQPhaseFilesResolved byStrategyVerifiedWhen

When no run has a recorded resolution, print No recorded conflict resolutions. rather than an empty table. An entry with verified: no is not an error — it is the honest value the record exists to surface.

Recently Completed

List artifacts completed in the last 7 days (by updated date).

Step 3: Apply Filters (if provided)
  • If a REQ ID is given, show detailed status for just that requirement and its tasks
  • If "in-progress" is given, show only non-complete work
  • If "bugs" is given, show only bug reports
  • If no filter, show the full dashboard
Step 4: Highlight Action Items

At the bottom, list recommended next actions:

  • Specs that are draft and need validation
  • Approved specs that need architecture/tasks
  • Tasks that are ready to implement (dependencies met)
  • Bugs that are open and unassigned

© atelier-fashion, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in status of atelier-fashion/adlc-toolkit.

Open the folder on GitHubat commit 3a48c27

Compare with similar skills

Status next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Status compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Status this skillatelier-fashion/adlc-toolkit171—~2.3kAutomated safety check: PassMIT
ShowZimoLiao/scholaraio577—~356Automated safety check: PassMIT
Show Me Your Work Decision Logcursor/plugins11k8 repos~1.6kAutomated safety check: PassNone
Show Metellahq/opensession394—~1.6kAutomated safety check: PassMIT
Event Run Of Showmohitagw15856/pm-claude-skills1.4k—~1.4kAutomated safety check: PassMIT
Show Mefmflurry/settings-opencode171—~1.2kAutomated safety check: PassMIT

Similar skills

  • Show

    ZimoLiao/scholaraio

    A skill your agent uses when the user wants to read a paper or inspect metadata, abstract, conclusion, full text, figures, or detail levels L1 through L4.

    577 GitHub stars~356 tokensUpdated 16 days ago
    Auto-check passed

  • Show Me Your Work Decision Log

    cursor/plugins

    Official

    Keeps a TSV decision log for long or unattended agent runs, one row per decision with what, why, evidence and result, so a reviewer can check the work later.

    11k GitHub starsUsed in 8 repos~1.6k tokens
    Agent WorkflowsAuto-check passed

  • Show Me

    tellahq/opensession

    Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.

    394 GitHub stars~1.6k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Event Run Of Show

    mohitagw15856/pm-claude-skills

    Build the minute-by-minute run of show that lets an event run without the planner being asked anything — every cue, who owns it, what happens if it slips, and the version each supplier actually needs.

    1.4k GitHub stars~1.4k tokensUpdated 2 days ago
    Auto-check passed

  • Show Me

    fmflurry/settings-opencode

    Help the user understand the current topic visually. An agent skill from fmflurry/settings-opencode.

    171 GitHub stars~1.2k tokensUpdated 4 days ago
    Documents & OfficeAuto-check passed

  • Show Hn Writer

    Varnan-Tech/opendirectory

    Draft a Show HN post backed by real HN performance data. An agent skill from Varnan-Tech/opendirectory.

    674 GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

More from atelier-fashion/adlc-toolkit

All 16 skills in this repo

  • Canary

    atelier-fashion/adlc-toolkit

    Canary deployment with smoke tests — deploy to a zero-traffic revision, run health checks, and promote on success.

    171 GitHub stars~2.2k tokensUpdated 12 days ago
    Auto-check passed

  • Sprint

    atelier-fashion/adlc-toolkit

    Parallel pipeline orchestrator — launch multiple /proceed sessions concurrently across REQs, monitor progress, and report status.

    171 GitHub stars~9.8k tokensUpdated 12 days ago
    Auto-check passed

  • Template Drift

    atelier-fashion/adlc-toolkit

    Detect drift across ALL the sync surfaces /init vendors into a project — .adlc/templates/.md, .adlc/partials/.sh, .adlc/ETHOS.md, and the workflow runtime (.adlc/workflows/adlc-sprint.workflow.js +…

    171 GitHub stars~9k tokensUpdated 12 days ago
    Auto-check passed

  • Proceed

    atelier-fashion/adlc-toolkit

    End-to-end ADLC pipeline that takes a requirement from spec through to deployed.

    171 GitHub stars~14k tokensUpdated 12 days ago
    Auto-check: warnings

  • Init

    atelier-fashion/adlc-toolkit

    Bootstrap .adlc/ structure in a new repo or subdirectory. An agent skill from atelier-fashion/adlc-toolkit.

    171 GitHub stars~4.1k tokensUpdated 12 days ago
    Auto-check passed

  • Manifest

    atelier-fashion/adlc-toolkit

    Remote-derived view of all in-flight ADLC work — open PRs and pushed feat/REQ- branches across every session — with a coarse component/domain overlap report.

    171 GitHub stars~4.8k tokensUpdated 12 days ago
    Auto-check passed

Questions about Status

What does Status do?

Show current state of all ADLC work across the project. An agent skill from atelier-fashion/adlc-toolkit. Status is an agent skill from atelier-fashion/adlc-toolkit.

How do I install Status in Claude Code?

Run `npx skills add atelier-fashion/adlc-toolkit --skill status -a claude-code`. Or copy the skill folder (status in atelier-fashion/adlc-toolkit) into .claude/skills/status in your project. Claude Code loads it when a task matches its description.

How do I install Status in Codex?

Run `npx skills add atelier-fashion/adlc-toolkit --skill status -a codex`. Or copy the skill folder (status in atelier-fashion/adlc-toolkit) into .agents/skills/status in your project. Codex loads it when a task matches its description.

Can I use Status in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add atelier-fashion/adlc-toolkit --skill status -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/status, .gemini/skills/status, .github/skills/status and .opencode/skills/status in your project.

What does Status need to run?

Going by SKILL.md and its folder, Status needs the command-line tools its instructions call (git and python3). Our summary lists: Python 3.

Does Status access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Status safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Status use?

Status is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Status use?

About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Status?

Skills that share tags, products or a category with Status: Show (ZimoLiao/scholaraio, 577 stars), Show Me Your Work Decision Log (cursor/plugins, 11k stars), Show Me (tellahq/opensession, 394 stars) and Event Run Of Show (mohitagw15856/pm-claude-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Status?

atelier-fashion (a GitHub organization) maintains it in atelier-fashion/adlc-toolkit, which has 171 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 28, 2026.

Source: atelier-fashion/adlc-toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.