me2resh Writing rule
When this skill writes a durable artifact, read .claude/rules/writing-standard.md. Use the controlled technical writing profile.
/projects — List Managed Projects
Show every project ApexYard is managing, with a one-line health snapshot. Reads apexyard.projects.yaml at the root of the ops repo (your fork of apexyard) and iterates the registry.
Path resolution
Read the registry path via portfolio_registry, the per-project docs dir via portfolio_projects_dir, and the ideas backlog via portfolio_ideas_backlog — all from .claude/hooks/_lib-portfolio-paths.sh. Source the helper at the top of any bash block that touches those paths:
source "$(git rev-parse --show-toplevel)/.claude/hooks/_lib-read-config.sh"
source "$(git rev-parse --show-toplevel)/.claude/hooks/_lib-portfolio-paths.sh"
registry=$(portfolio_registry)
Defaults match today's single-fork layout (./apexyard.projects.yaml, ./projects, ./projects/ideas-backlog.md). Adopters in split-portfolio mode override the portfolio.{registry, projects_dir, ideas_backlog} keys in .claude/project-config.json. Don't hardcode literal apexyard.projects.yaml or projects/ paths in bash blocks — the helper resolves whichever mode the adopter is in. See docs/multi-project.md.
Usage
/projects
/projects --status active
/projects --json
Behaviour
Read apexyard.projects.yaml:
version: 1
projects:
- name: example-app
repo: your-org/example-app
workspace: workspace/example-app
docs: projects/example-app
status: active
roles: [tech-lead, backend-engineer]
For each project, gather:
# If a local workspace clone exists, use it for git data
if [ -d "{workspace}" ]; then
BRANCH=$(git -C {workspace} rev-parse --abbrev-ref HEAD)
LAST=$(git -C {workspace} log -1 --format='%h %ar %s')
DIRTY=$(git -C {workspace} status --porcelain | wc -l | tr -d ' ')
else
BRANCH="(not cloned)"
LAST="-"
DIRTY="-"
fi
# Always go to GitHub for PRs / issues (project of record)
PRS=$(gh -R {repo} pr list --state open --json number --jq 'length')
ISSUES=$(gh -R {repo} issue list --state open --json number --jq 'length')
If apexyard.projects.yaml doesn't exist at the ops-repo root, print a clear error pointing the user at apexyard.projects.yaml.example and docs/multi-project.md for the setup guide.
Output format
A markdown table:
| Project | Status | Branch | PRs | Issues | Last Commit | Dirty |
|---------|--------|--------|-----|--------|-------------|-------|
| example-app | active | main | 3 | 12 | 2h ago — fix(...) | 0 |
| billing-api | handover | feature/GH-4 | 1 | 8 | 1d ago — feat(...) | 2 |
| marketing-site | paused | main | 0 | 1 | 30d ago — chore(...) | 0 |
After the table, a summary line:
3 projects · 4 open PRs · 21 open issues · 1 dirty workspace
And, if relevant, flag rows that need attention:
⚠ marketing-site: last commit 30 days ago (paused or stale?)
⚠ billing-api: 2 uncommitted files in workspace
Filters
| Flag | Effect |
|---|---|
--status active |
Only show projects with status: active |
--status handover |
Only show projects mid-handover |
--status paused |
Only show paused projects |
--status archived |
Only show archived projects |
--json |
Emit machine-readable JSON instead of a table |
Errors and edge cases
| Condition | Behaviour |
|---|---|
No apexyard.projects.yaml at the ops-repo root |
Print a clear error and a sample registry to copy |
| Project listed but workspace path missing | Show row with (not cloned) — don't fail |
gh not authenticated |
Show row with ? for PRs/issues — don't fail |
repo field looks invalid |
Skip with a warning, continue with the rest |
Rules
- Registry-driven — the registry is the source of truth; no discovery fallback
- Source of truth for PRs/issues = GitHub — never read from a stale local file
- Source of truth for branch state = local workspace —
ghdoesn't know about your dirty files - Don't silently fail on a missing project — show the row, mark the gap
- Sort by status then name — active first, then handover, then paused, then archived
- Never modify the registry from this skill — read-only
Related skills
/inbox— same registry, but filtered to "needs your attention"/status— per-project deep dive (current branch, recent commits)/tasks— actionable list with URLs/handover— onboard a new repo into the registry
Part of ApexYard — multi-project SDLC framework for Claude Code · MIT.