Check iteration progress status

VerifiedSafe

Checks the `docs/work/` directory to list all iterations, display the current iteration's step-by-step progress (table with completion status), and prompt the next step to execute. Helps track project status in structured workflows.

Sby Skills Guide Bot
DevelopmentBeginner
6/2/2026
Claude Code
#status-check#iteration#project-management#workflow

Recommended for

Automated summary

Checks the current iteration status of a project following the 'how-to-work' framework by examining the docs/work/ directory.

Strengths

  • Clear tracking of iteration progress
  • Automatic suggestion of next steps
  • Seamless integration with other /tf: commands

Limitations

  • Requires a specific directory structure
  • Only works if docs/work/ exists
  • Limited to predefined steps of the framework
When to use it

Use this skill when you need to know where you left off in a structured project with iterations.

When not to use it

Do not use it for ad-hoc tasks or projects that do not follow the 'how-to-work' framework.

Security analysis

Safe
Quality score85/100

The skill uses only read-only filesystem commands (ls, cat) confined to docs/work/, with no destructive, exfiltrating, or privilege-escalation actions. Command substitution in context is safe as the .current file is managed by the skill itself within a controlled directory, posing negligible injection risk.

No concerns found

How this analysis is made

Examples

Check current status
Check the current progress of my project.
Ask for next step
What is the current iteration status and what should I do next?

description: "how-to-work 현황 확인. 현재 이터레이션과 단계 진행 상태를 보여준다." allowed-tools: Bash, Read, Glob

현황 확인

컨텍스트

  • 버전 목록: !ls -d docs/work/v*/ 2>/dev/null || echo "NO_VERSIONS"
  • 현재 버전: !cat docs/work/.current 2>/dev/null || echo "NO_CURRENT"
  • 현재 산출물: !ls docs/work/$(cat docs/work/.current 2>/dev/null)/ 2>/dev/null || echo "NO_FILES"

지시사항

docs/work/ 디렉토리를 확인하고 현재 진행 상태를 보고한다.

디렉토리가 없는 경우

"아직 시작되지 않았습니다. /tf:0으로 0단계(문제 정의)부터 시작하세요." 라고 안내한다.

디렉토리가 있는 경우

  1. 전체 이터레이션 목록을 보여준다 (v0, v1, ...).
  2. 현재 이터레이션(.current 파일이 가리키는 버전)의 진행 상태를 아래 표로 출력한다:

| 단계 | 스킬 | 파일 | 상태 | |------|------|------|------| | 0. 문제 정의 | /tf:0 | 0-problem-definition.md | 완료/미완료 | | 1. 목표 정의 | /tf:1 | 1-goals.md | 완료/미완료 | | 2. 요구사항 정리 | /tf:2 | 2-requirements.md | 완료/미완료 | | 3. 설계 | /tf:3 | 3-design.md | 완료/미완료 | | 4. 작업 분해 | /tf:4 | 4-task-breakdown.md | 완료/미완료 | | 5. MVP 구현 | /tf:5 | 5-mvp.md | 완료/미완료 | | 6. 검증 | /tf:6 | 6-verification.md | 완료/미완료 | | 7. 마무리 | /tf:7 | 7-wrap-up.md | 완료/미완료 |

  1. 다음 진행할 단계를 안내한다: "다음 단계: /tf:N으로 진행하세요."

현재 이터레이션이 모두 완료된 경우

"현재 이터레이션(vN)이 완료되었습니다. 새 이터레이션을 시작하시겠습니까?" 라고 질문한다. 사용자가 승인하면:

  1. 다음 버전 디렉토리를 생성한다 (예: docs/work/v1/).
  2. docs/work/.current 파일을 새 버전 이름으로 갱신한다.
  3. "새 이터레이션 v1이 시작되었습니다. /tf:0으로 시작하세요." 라고 안내한다.

별칭 안내

스킬 목록 하단에 아래 별칭 표를 보여준다:

| 숫자 | 별칭 | |------|------| | /tf:0 | /tf:define | | /tf:1 | /tf:goal | | /tf:2 | /tf:req | | /tf:3 | /tf:design | | /tf:4 | /tf:task | | /tf:5 | /tf:mvp | | /tf:6 | /tf:verify | | /tf:7 | /tf:wrapup |

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/check-iteration-progress-status-mmh8qqe1/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/check-iteration-progress-status-mmh8qqe1' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/check-iteration-progress-status-mmh8qqe1/download' --output '.skill-downloads/check-iteration-progress-status-mmh8qqe1/SKILL.md.part' && mv '.skill-downloads/check-iteration-progress-status-mmh8qqe1/SKILL.md.part' '.skill-downloads/check-iteration-progress-status-mmh8qqe1/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.

Tools declared by the author (check availability in your agent): Bash, Read, Glob

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/check-iteration-progress-status-mmh8qqe1/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