Skip to content

DangQuangSE/team-development-skills / .agents/skills/team-list

team-list

Verified

Utility skill. Lists all projects under the projects/ directory and shows which Virtual Team pipeline phases have been completed for each project.

team-list

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.


Step 1 — Discover Projects

Use the Glob tool to find all project directories:

  • Pattern: projects/*/team/

If no results → output: "No Virtual Team projects found in projects/. Run /team \"requirement\" to create one." STOP.


Step 2 — Check Phase Status for Each Project

For each project directory found at projects/{slug}/team/:

Check which phase directories exist and contain at least one file:

PhaseDirectoryKey file to check
BAteam/ba/requirements.md
TechLeadteam/techlead/architecture.md
PMteam/pm/sprint-plan.md
BE Devteam/be/pr-description.md
FE Devteam/fe/pr-description.md
Testerteam/tester/test-plan.md
QA/QCteam/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 line

Step 3 — Output Project Status Table

Output 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/).

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall