Agent skill

Ops Projects

by Lifecycle-Innovations-Limited in Lifecycle-Innovations-Limited/claude-ops

OPS on-demand: This skill should be used when the user asks to "portfolio dashboard", "gsd projects"…

MITAuto-check: notes

Install Ops Projects

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-projects -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-projects --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-ops/skills/ops-projects .claude/skills/ops-projects && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "ops-projects" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-projects into .claude/skills/ops-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-projects", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-projects

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-projects -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-projects --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude-ops/skills/ops-projects .agents/skills/ops-projects && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ops-projects" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-projects into .agents/skills/ops-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-projects", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-projects -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-projects --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude-ops/skills/ops-projects .cursor/skills/ops-projects && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ops-projects" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-projects into .cursor/skills/ops-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-projects", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Lifecycle-Innovations-Limited/claude-ops.git --path claude-ops/skills/ops-projects

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-projects -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-projects --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude-ops/skills/ops-projects .gemini/skills/ops-projects && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ops-projects" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-projects into .gemini/skills/ops-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-projects", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-projects

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-projects -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude-ops/skills/ops-projects .github/skills/ops-projects && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ops-projects" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-projects into .github/skills/ops-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-projects", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-projects -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-projects --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude-ops/skills/ops-projects .opencode/skills/ops-projects && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ops-projects" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-projects into .opencode/skills/ops-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-projects", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ops-projects
GitHub stars: 540
Token cost: ~1.8k tokens
SKILL.md length: 323 words
Files: 1
Skills in repo: 67
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

OPS on-demand: This skill should be used when the user asks to "portfolio dashboard", "gsd projects"…

Works in 3 steps: Preferences: cat… → Daemon health: cat… → GSD registry: cat…
Asks to portfolio dashboard
SKILL.md covers Runtime Context, Quick commands, Data flow and Dashboard output, plus 4 more sections
Calls bash

What it does

Ops Projects is an agent skill from Lifecycle-Innovations-Limited/claude-ops. OPS on-demand: This skill should be used when the user asks to "portfolio dashboard", "gsd projects"…

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Business operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS monitoring, revenue… The licence is MIT.

When your agent uses it

Asks to portfolio dashboard

Example prompts

“portfolio dashboard”
“gsd projects”
“/ops-projects”

Requirements

Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob, WebFetch, AskUserQuestion

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Preferences: cat ${OPS_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json — read owner, timezone
Daemon health: cat ${OPS_DATA_DIR}/daemon-health.json — show service status in dashboard footer
GSD registry: cat ${OPS_DATA_DIR}/registry.json — primary project index (updated by daemon twice daily + on-demand with --sync)

What it can do on your machine

Read from SKILL.md and the folder at commit 6a4340b. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash
- Read
- Grep
- Glob
- WebFetch
- AskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ops Projects loads about 1.8k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 323 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~29
When it runs · the whole SKILL.md, loaded when a task matches: ~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Bash, Read, Grep, Glob, WebFetch, AskUserQuestion
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Lifecycle-Innovations-Limited/claude-ops at commit 6a4340b, republished under its MIT licence (© Lifecycle-Innovations-Limited). 323 words, ~1,787 tokens.

Download SKILL.mdSave it as .claude/skills/ops-projects/SKILL.md (or your agent's skills folder).

name: ops-projects
description: OPS on-demand: This skill should be used when the user asks to "portfolio dashboard", "gsd projects"…
allowed-tools: Bash, Read, Grep, Glob, WebFetch, AskUserQuestion
argument-hint: [project-alias|--sync|--refresh]
effort: low
maxTurns: 20
disallowedTools: Edit, Write, NotebookEdit

Runtime Context

Before rendering, load:

Preferences: cat ${OPS_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json — read owner, timezone
Daemon health: cat ${OPS_DATA_DIR}/daemon-health.json — show service status in dashboard footer
GSD registry: cat ${OPS_DATA_DIR}/registry.json — primary project index (updated by daemon twice daily + on-demand with --sync)

OPS ► PROJECTS — GSD Portfolio Dashboard

Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).

Quick commands

bash

# Refresh registry data on demand
bash ${CLAUDE_PLUGIN_ROOT}/scripts/ops-gsd-registry-sync.sh

# Show registry contents
cat ${OPS_DATA_DIR}/registry.json

# Show health summary
cat ${OPS_DATA_DIR}/cache/projects_health.json

Data flow

$HOME  (walked recursively, depth <= OPS_GSD_SCAN_DEPTH, default 5)
   + any extra roots listed in OPS_GSD_SCAN_ROOTS (colon-separated)
              │
              ▼
      <any-dir>/.planning/
              │
              ├── HANDOFF.json     ← active-phase projects
              ├── STATE.md
              ├── ROADMAP.md
              └── MILESTONES.md
              │
              ▼  ops-gsd-registry-sync.sh (daemon: 6am + 6pm)
                    │
                    ▼
              ${OPS_DATA_DIR}/
                  ├── registry.json          ← all projects, sorted by priority
                  └── cache/
                        └── projects_health.json  ← health summary
                              │
                              ▼  ops-projects skill reads this

Discovery

ops-gsd-registry-sync.sh does not assume a fixed workspace directory. It walks $HOME and records every .planning/ directory it finds, so any layout works.

OPS_GSD_SCAN_ROOTS — colon-separated extra roots to walk besides $HOME (use this for projects that live outside the home directory)
OPS_GSD_SCAN_DEPTH — how deep to walk (default 5)
OPS_GSD_SCAN_EXCLUDE — colon-separated extra directory names to skip
OPS_GSD_INCLUDE_WORKTREES=1 — also scan .worktrees/ (skipped by default, since worktrees duplicate an existing project)

Build noise (node_modules, .git, .venv, dist, caches) is always skipped.

Dashboard output

Build the dashboard from ${OPS_DATA_DIR}/cache/projects_health.json (fall back to ${OPS_DATA_DIR}/registry.json if missing). Show:

╔══════════════════════════════════════════════════════════════╗
║  OPS ► PROJECTS          [owner]    [date]    [daemon status] ║
╠══════════════════════════════════════════════════════════════╣
║  GSD Portfolio — 23 projects                                 ║
║                                                              ║
║  🟢 EXECUTING (3)                                           ║
║    my-webapp            Phase 12  [executing]   branch: main  0 dirty ║
║    my-plugin            Phase 16  [executing]   branch: main  2 dirty ║
║    my-saas-app          Phase 39  [executing]   branch: dev   0 dirty ║
║                                                              ║
║  🟡 PAUSED (4)                                              ║
║    my-project-a         Phase 08  [paused]      branch: feat  1 dirty ║
║    my-project-b         Phase 3   [verifying]   branch: main  0 dirty ║
║    ...                                                          ║
║                                                              ║
║  🔴 BLOCKED (1)                                             ║
║    my-ecommerce         Phase 7   [await-UAT]   branch: prod  0 dirty ║
║                                                              ║
║  ⚪ IDLE / UNTRACKED (15)                                    ║
║    my-side-project      Phase 1   [complete]    branch: main  0 dirty ║
║    my-other-app         —         —              branch: dev  3 dirty ║
║    ...                                                          ║
╠══════════════════════════════════════════════════════════════╣
║  ⚡ Services: message-listener ● | inbox-digest ⏱ 2h | gsd-registry ⏱ 12h ║
╚══════════════════════════════════════════════════════════════╝

Status indicators (from `status` field, case-insensitive)

executing → 🟢
paused / verifying / phase_complete → 🟡
human / uat / blocked / pending → 🔴
empty status + has phase → ⚪ (idle)
no phase, no status → ⚪ (untracked/no GSD)

Columns per project: ALIAS | PHASE | STATUS | BRANCH | DIRTY | NEXT ACTION

Project deep-dive

If $ARGUMENTS contains a project alias, find it in the registry and show:

╔══════════════════════════════════════════════════════════════╗
║  PROJECT — [alias]                                           ║
╠══════════════════════════════════════════════════════════════╣
║  Path:      [path from registry]                             ║
║  Phase:     [phase]  Status: [status]                       ║
║  Milestone: [milestone name]                                ║
║  Branch:    [branch]   Dirty: [N]  Unpushed: [N]            ║
║  Blockers:  [N]                                            ║
║  Next:      [next_action text]                              ║
║                                                              ║
║  GSD files: ✓ ROADMAP  ✓ MILESTONES  [HAS_HANDOFF] STATE   ║
╚══════════════════════════════════════════════════════════════╝

Actions:
  [1] Open project directory
  [2] Continue GSD (/gsd-next [alias])
  [3] Git: branch / status / log
  [4] Run /ops projects (back to portfolio)

Present numbered actions and let the user pick by typing the number or action name.

--sync flag

If --sync or --refresh is passed, run the registry sync script first, then display the updated dashboard:

bash

bash ${CLAUDE_PLUGIN_ROOT}/scripts/ops-gsd-registry-sync.sh 2>&1

Show "Refreshing..." while running, then present the full updated dashboard.

Error states

If registry.json is missing/empty: show a one-shot sync prompt

No project registry found. Run /ops projects --sync to build it.

If daemon health shows action_needed: surface that in a warning banner

CLI reference (for manual use)

Command	What it does
`/ops projects`	Show full portfolio
`/ops projects [alias]`	Deep-dive on one project
`/ops projects --sync`	Force-refresh registry + show dashboard
`/ops:setup registry`	Open registry setup (future)

Files

Just SKILL.md in claude-ops/skills/ops-projects of Lifecycle-Innovations-Limited/claude-ops.

Open the folder on GitHubat commit 6a4340b

Compare with similar skills

Ops Projects next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ops Projects compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ops Projects this skillLifecycle-Innovations-Limited/claude-ops	540	—	~1.8k	Automated safety check: Notes	MIT	yesterday
Knowledge Opsaffaan-m/ECC	275k	2 repos	~1.7k	Automated safety check: Pass	MIT	3 days ago
Research Opsaffaan-m/ECC	275k	2 repos	~902	Automated safety check: Pass	MIT	3 days ago
Terminal Opsaffaan-m/ECC	275k	2 repos	~750	Automated safety check: Pass	MIT	3 days ago
Messages Opsaffaan-m/ECC	275k	1 repos	~724	Automated safety check: Pass	MIT	3 days ago
Email Opsaffaan-m/ECC	275k	1 repos	~1.1k	Automated safety check: Pass	MIT	3 days ago

Similar skills

Knowledge Ops
affaan-m/ECC
Knowledge base management, ingestion, sync, and retrieval across multiple storage layers (local files, MCP memory, vector stores, Git repos).
275k GitHub starsUsed in 2 repos~1.7k tokens
Knowledge ManagementAuto-check passed
Research Ops
affaan-m/ECC
Evidence-first current-state research workflow for ECC. An agent skill from affaan-m/ECC.
275k GitHub starsUsed in 2 repos~902 tokens
Research & ScienceAuto-check passed
Terminal Ops
affaan-m/ECC
Evidence-first repo execution workflow for ECC. An agent skill from affaan-m/ECC.
275k GitHub starsUsed in 2 repos~750 tokens
Testing & QAAuto-check passed
Messages Ops
affaan-m/ECC
Evidence-first live messaging workflow for ECC. An agent skill from affaan-m/ECC.
275k GitHub starsUsed in 1 repo~724 tokens
Productivity & AutomationAuto-check passed
Email Ops
affaan-m/ECC
Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC.
275k GitHub starsUsed in 1 repo~1.1k tokens
Writing & ContentAuto-check passed
GitHub Ops
affaan-m/ECC
GitHub操作、自動化、APIインテグレーション、およびCI/CDワークフロー. An agent skill from affaan-m/ECC.
275k GitHub stars~1.1k tokensUpdated 3 days ago
DevOps & CloudAuto-check passed

Questions about Ops Projects

What does Ops Projects do?

OPS on-demand: This skill should be used when the user asks to "portfolio dashboard", "gsd projects"…. Ops Projects is an agent skill from Lifecycle-Innovations-Limited/claude-ops.

When should I use Ops Projects?

Ops Projects fits situations like: asks to portfolio dashboard.

How do I install Ops Projects in Claude Code?

Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-projects -a claude-code`. Or copy the skill folder (claude-ops/skills/ops-projects in Lifecycle-Innovations-Limited/claude-ops) into .claude/skills/ops-projects in your project. Claude Code loads it when a task matches its description.

How do I install Ops Projects in Codex?

Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-projects -a codex`. Or copy the skill folder (claude-ops/skills/ops-projects in Lifecycle-Innovations-Limited/claude-ops) into .agents/skills/ops-projects in your project. Codex loads it when a task matches its description.

Can I use Ops Projects in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-projects -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ops-projects, .gemini/skills/ops-projects, .github/skills/ops-projects and .opencode/skills/ops-projects in your project.

What does Ops Projects need to run?

Going by SKILL.md and its folder, Ops Projects needs the command-line tools its instructions call (bash). Its frontmatter pre-approves these tools: Bash, Read, Grep, Glob, WebFetch, AskUserQuestion.

Does Ops Projects access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ops Projects safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Ops Projects use?

Ops Projects is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ops Projects use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ops Projects?

Skills that share tags, products or a category with Ops Projects: Knowledge Ops (affaan-m/ECC, 275k stars), Research Ops (affaan-m/ECC, 275k stars), Terminal Ops (affaan-m/ECC, 275k stars) and Messages Ops (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ops Projects?

Lifecycle-Innovations-Limited (a GitHub organization) maintains it in Lifecycle-Innovations-Limited/claude-ops, which has 540 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on October 7, 2026.

Source: Lifecycle-Innovations-Limited/claude-ops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Ops Projects

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Runtime Context

OPS ► PROJECTS — GSD Portfolio Dashboard

Quick commands

Data flow

Discovery

Dashboard output

Status indicators (from status field, case-insensitive)

Columns per project: ALIAS | PHASE | STATUS | BRANCH | DIRTY | NEXT ACTION

Project deep-dive

--sync flag

Error states

CLI reference (for manual use)

Files

Compare with similar skills

Similar skills

More from Lifecycle-Innovations-Limited/claude-ops

Questions about Ops Projects

Status indicators (from `status` field, case-insensitive)