Automated summary
Displays, read-only, the progress of a project's dev and biz pipelines and recommends the next /ace-* command to run.
Strengths
- Strictly read-only: no file is created or modified
- Reads only deliverable frontmatter to keep token usage low
- Covers both pipelines (dev: analyze → design → dev → test → wiki; biz: research → model → plan → judge) with explicit status icons
- Handles both numbered tasks (workspace/tasks/{n}) and unnumbered current work (workspace/current)
Limitations
- Assumes an existing .ace/profile.yaml and workspace/tasks/taskIndex.json layout and fails without them
- Infers progress only from file presence and the frontmatter status field, not from actual content
- Never chains into the next action on its own: explicit user approval is required
To get an at-a-glance view of where a project stands and which command to run next.
To produce or edit deliverables — use the corresponding production skills (analyze, design, dev, test, research, etc.) instead.
Security analysis
SafeThe skill is read-only, using only Read and Glob tools to inspect project metadata and task files. It does not execute destructive commands, access the network, or exfiltrate data, and explicitly instructs not to modify files.
No concerns found
How this analysis is madeExamples
/ace-status지금 파이프라인 어디까지 진행됐는지 dev랑 biz 둘 다 보여줘현재 태스크 상태 확인하고 다음에 실행할 명령어 알려줘name: ace-status description: "파이프라인 현황 조회 + 다음 액션 안내" user-invocable: true allowed-tools:
- Read
- Glob
/ace status — 파이프라인 현황 + 다음 액션
사용법
/ace-status
목적
현재 프로젝트의 dev/biz 파이프라인 진행 상태를 한눈에 보여주고, 다음에 실행할 명령어를 안내한다.
태스크 번호 기반(workspace/tasks/{번호})과 번호 없는 현재 작업(workspace/current)을 모두 지원한다.
실행 흐름
Step 1: 프로필 확인
.ace/profile.yaml을 읽어 프로젝트명, 팩, 모드를 파악한다.
Step 2: 태스크 현황 수집
workspace/tasks/taskIndex.json을 읽고, 동시에 workspace/current/의 산출물도 확인한다.
태스크가 없고 workspace/current/ 산출물도 없으면:
아직 태스크가 없습니다.
→ /ace-task start <이슈번호> 태스크 생성
→ 또는 번호 없이 $ace-analyze / $ace-research 로 workspace/current 작업 시작
Step 3: 산출물 상태 확인
각 태스크 폴더에서 산출물 파일의 존재 여부와 frontmatter status를 확인한다.
번호 없는 작업은 workspace/current/에서 같은 파일명을 확인한다.
dev 파이프라인 체크:
analysis.md→ analyze 단계design.md→ design 단계development.md→ dev 단계test.md→ test 단계workspace/wiki/work-log.md→ wiki 기록
biz 파이프라인 체크:
research.md→ research 단계model.md→ model 단계plan.md→ plan 단계judgement.md→ judge 단계
Step 4: 현황 출력
아래 형식으로 출력한다:
═══ {프로젝트명} 파이프라인 현황 ═══
[dev] 분석 → 설계 → 구현 → 검증
{상태} analyze → {상태} design → {상태} dev → {상태} test
[biz] 리서치 → 모델링 → 계획 → 판단
{상태} research → {상태} model → {상태} plan → {상태} judge
상태 아이콘:
✓ = 완료 (status: done)
◆ = 진행 중 (status: in_progress)
○ = 대기
[다음 액션]
→ /ace-{다음스킬} {설명}
완료 시 출력
상태 조회 결과만 출력하고 파일은 수정하지 않는다. Claude Code에서는 /ace-*, Codex에서는 $ace-* 표기로 같은 스킬을 호출할 수 있음을 함께 안내한다.
태스크 작업과 current 작업이 모두 있으면 최근 수정 시간이 더 최신인 쪽을 기본 다음 액션으로 제안한다.
Step 5: 다음 액션 결정
dev 파이프라인 다음 액션:
| 현재 상태 | 다음 명령 | 설명 |
|-----------|----------|------|
| 태스크 없음 | /ace-task start | 태스크 생성 |
| analyze ○ | /ace-analyze 또는 /ace-dev-quick | 분석 시작 또는 바로 개발 |
| analyze ✓, design ○ | /ace-design | 설계 시작 |
| design ✓, dev ○ | /ace-dev | 구현 시작 |
| dev ✓, test ○ | /ace-test | 테스트 시작 |
| test ✓, wiki 미갱신 | /ace-wiki | 작업 이력/결정 기록 |
| test ✓ | 완료! 커밋/PR 진행 | - |
| 어딘가 ◆ | 해당 스킬 재실행 (이어하기) | 중단된 곳에서 이어서 |
biz 파이프라인 다음 액션:
| 현재 상태 | 다음 명령 | 설명 |
|-----------|----------|------|
| research ○ | /ace-research | 시장/경쟁/고객 리서치 |
| research ✓, model ○ | /ace-model | 비즈니스 모델 설계 |
| model ✓, plan ○ | /ace-plan | 실행 계획 수립 |
| plan ✓, judge ○ | /ace-judge | Go/No-Go 판단 |
| judge ✓ | 판단 완료! 결과에 따라 행동 | - |
| 어딘가 ◆ | 해당 스킬 재실행 (이어하기) | 중단된 곳에서 이어서 |
토큰 안내
마지막에 항상 다음 문구를 포함한다:
💡 다음 작업을 진행할까요? (토큰이 소모됩니다)
사용자가 명시적으로 승인한 후에만 다음 스킬을 실행한다.
규칙
- 이 스킬은 읽기 전용 — 파일을 수정하지 않는다.
- 토큰 소모를 최소화하기 위해 파일은 frontmatter만 읽는다 (전체 내용 불필요).
- 태스크가 여러 개면 가장 최근 업데이트된 태스크를 기본으로 보여준다.
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 filesThis 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.mdFrom the root of a test project, save the file as .skill-downloads/pipeline-status-next-action-mrzxuppp/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/pipeline-status-next-action-mrzxuppp' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/pipeline-status-next-action-mrzxuppp/download' --output '.skill-downloads/pipeline-status-next-action-mrzxuppp/SKILL.md.part' && mv '.skill-downloads/pipeline-status-next-action-mrzxuppp/SKILL.md.part' '.skill-downloads/pipeline-status-next-action-mrzxuppp/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
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/pipeline-status-next-action-mrzxuppp/SKILL.md' && test -s '.skill-downloads/pipeline-status-next-action-mrzxuppp/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ace-status' && cp -R '.skill-downloads/pipeline-status-next-action-mrzxuppp' '.claude/skills/ace-status'Codex
test -f '.skill-downloads/pipeline-status-next-action-mrzxuppp/SKILL.md' && test -s '.skill-downloads/pipeline-status-next-action-mrzxuppp/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/ace-status' && cp -R '.skill-downloads/pipeline-status-next-action-mrzxuppp' '.agents/skills/ace-status'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/pipeline-status-next-action-mrzxuppp'openskills read 'pipeline-status-next-action-mrzxuppp'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual 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/pipeline-status-next-action-mrzxuppp/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.
PDF Reader
Productivity
Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.
Discord Messaging Workflows
Productivity
Use the message tool to send, edit, and moderate Discord messages with interactive components.
Interactive Verdict Preview
Productivity
Generate an interactive HTML preview of keep/drop verdicts for maintainer review, then process the pasted feedback JSON.