Results for “project-status”
12 skillsteam-list
Scans the projects/ directory and reports the pipeline phase completion status for each Virtual Team project.
19 · bundle
team-list
Scans the projects/ directory and reports the pipeline phase completion status for each Virtual Team project, including validation errors and QA verdicts.
1 · bundle
pipeline
Check health of registered background pipelines across all projects. Shows HEALTHY/DEGRADED/DEAD status. Run /pipeline [project-name] to filter.
8 · bundle
template-sync
Sync Claude Code assets between a project and its project-template buffer, with subcommands for status, diff, pull, promote, trial, and sync-from-buffer. Promotion is always opt-in and never automatic.
0
More results
flow-bio
Authenticate, browse pipelines, samples, and projects, upload data, launch pipeline executions, and check run status on any Flow.bio instance via CLI.
17 · bundle
managing-sst
Manages SST applications by discovering project config, checking stack status, and inspecting bound resources. Supports deployment, live Lambda debugging, secret management, and multi-stage environments.
7
railway-service
Check service status, rename services, change service icons, link services, or create services with Docker images. For creating services with local code, prefer railway-new skill. For GitHub repo sources, use railway-new skill to create empty service then railway-environment skill to configure source.
5
railway-service
Check service status, rename services, change service icons, link services, or create services with Docker images. For creating services with local code, prefer railway-new skill. For GitHub repo sources, use railway-new skill to create empty service then railway-environment skill to configure source.
0
managing-dbt
Manages and monitors dbt projects, model runs, and test results via dbt CLI and dbt Cloud API, covering run status, test failures, source freshness, and manifest analysis.
7
nick-project-orchestrator
Top-layer project orchestration skill for Nick's workflow. Use when a request involves multiple stages, skills, or deliverables and the work needs to stay aligned from idea to scope to design to schema to build to QA to deploy. Coordinates the right sequence, enforces stage gates, prevents drift and overbuilding, tracks status/blockers/next actions, and creates clear handoffs between strategist, design, schema, Supabase, build, QA, and launch work.
0
team-tasks
Coordinate multi-agent development pipelines using shared JSON task files. Use when dispatching work across dev team agents (code-agent, test-agent, docs-agent, monitor-bot), tracking pipeline progress, or running sequential/parallel workflows. Covers project init, task assignment, status tracking, agent dispatch via sessions_send, and result collection. Supports two modes: linear (sequential pipeline) and dag (dependency graph with parallel execution).
1 · bundle
amq-cli
Coordinate agents via the AMQ CLI for file-based inter-agent messaging. Use this skill whenever you need to send messages to another agent (codex, claude, or any named handle), check your inbox, drain queued messages, set up co-op mode between agents, join a swarm team, route messages across projects, or diagnose delivery issues. Also use it when you receive a message and need to know how to reply, inspect receipts, or handle priority. Covers any multi-agent coordination task where agents need to talk to each other — review requests, questions, status updates, decision threads, wake notifications, and orchestrator integration (Symphony, Kanban). For collaborative spec/design workflows specifically, prefer the /amq-spec skill which provides structured phase-by-phase guidance. Not intended for distributed systems design (RabbitMQ, Kafka), CI/CD pipelines, or single-agent tasks with no partner.
0 · bundle