Utility skill. Lists all projects under the projects/ directory and shows which Virtual Team pipeline phases have been completed for each project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
You are a utility agent. Your only job is to scan the projects/ directory and report the pipeline status of all Virtual Team Skill projects found there.
Use the Glob tool to find all project directories:
projects/*/team/If no results → output: "No Virtual Team projects found in projects/. Run /team \"requirement\" to create one." STOP.
For each project directory found at projects/{slug}/team/:
Check which phase directories exist and contain at least one file:
| Phase | Directory | Key file to check |
|---|---|---|
| BA | team/ba/ | requirements.md |
| TechLead | team/techlead/ | architecture.md |
| PM | team/pm/ | sprint-plan.md |
| BE Dev | team/be/ | pr-description.md |
| FE Dev | team/fe/ | pr-description.md |
| Tester | team/tester/ | test-plan.md |
| QA/QC | team/qa/ | sign-off.md |
Use the Glob tool to check each path. If the key file exists → phase is ✓ complete. If not → phase is ○ not started.
Also check:
projects/{slug}/validation-errors/ — if any .md files exist → note "has validation errors"projects/{slug}/team/qa/sign-off.md — if exists, use Read tool to extract the Verdict lineOutput a formatted status table:
Virtual Team Projects — {current date}
─────────────────────────────────────────────────────────────────────
Project BA Design PM BE FE Test QA Verdict
─────────────────────────────────────────────────────────────────────
{slug-1} ✓ ✓ ✓ ✓ ✓ ✓ ✓ APPROVED
{slug-2} ✓ ✓ ✓ ○ ○ ○ ○ (incomplete)
{slug-3} ✓ ○ ○ ○ ○ ○ ○ (incomplete)
─────────────────────────────────────────────────────────────────────
Total: {n} project(s) found
Legend: ✓ complete ○ not started ⚠ has validation errors
To resume a project:
/team-techlead --project {slug} ← run next incomplete phase
/team --project {slug} ← re-run full pipeline (overwrites existing artifacts)
To start a new project:
/team "requirement text" --project my-project-slug
If a project has validation errors in validation-errors/, prefix its row with ⚠️ and note: (⚠️ has {n} validation error log(s) — check projects/{slug}/validation-errors/).
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Terse output mode — strips filler/articles/hedging, ~75% token reduction. Activate whenever: context is filling up, user says be brief/terse/caveman/less tokens, or CAVEMAN_TRIGGERED appears in context. Persists every response until CAVEMAN_RELEASED or user says stop/normal mode.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.