Skill

project-selector

Switches active project in monorepo: reads .groundwork.yml, lists projects with spec status (PRD, Architecture, Tasks), prompts selection, sets GROUNDWORK_PROJECT context, persists via Node script.

Node

Bash

git-workflow

developer-tools

Install

npx claudepluginhub etr/groundwork

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Quick project switching within a configured monorepo.

SKILL.md

Similar Skills

kotlin-ktor-patterns

Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.

everything-claude-code

163.2k

deep-research

Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.

everything-claude-code

163.2k

inventory-demand-planning

Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.

everything-claude-code

163.2k

Stats

Stars37

Forks4

Last CommitApr 8, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

Select Project Skill

Quick project switching within a configured monorepo.

Workflow

Step 1: Load Config

Read .groundwork.yml from the repo root.

If not found: "No .groundwork.yml found. Run /groundwork:setup-repo to configure your repository first."

Step 2: List Projects

Present available projects with their spec status:

## Available Projects | # | Project | Path | Specs | |---|---------|------|-------| | 1 | web-app | apps/web-app | PRD, Architecture, Tasks | | 2 | mobile-app | apps/mobile-app | PRD | | 3 | api-server | services/api | (none) |

For each project, check if <path>/specs/ exists and what spec files are present.

Use AskUserQuestion to ask which project to work on.

Step 3: Set Context

Set GROUNDWORK_PROJECT=<selected-name>

Set GROUNDWORK_PROJECT_ROOT=<absolute-path>

Persist selection via the persist script:

node ${PLUGIN_ROOT}/lib/persist-project.js <selected-name>

Where ${PLUGIN_ROOT} is the groundwork plugin directory (use the plugin root path from the session context). The script resolves its own terminal-pane identity internally — no env vars required.

Confirm: "Switched to project . Specs at <path>/specs/."

Step 4: Show Status

After switching, show the project's spec status:

PRD: exists / missing

Architecture: exists / missing

Tasks: exists / missing

Design System: exists / missing

Suggest next action based on what's available.

Select Project Skill

Quick project switching within a configured monorepo.

Workflow

Step 1: Load Config

Read .groundwork.yml from the repo root.

If not found: "No .groundwork.yml found. Run /groundwork:setup-repo to configure your repository first."

Step 2: List Projects

Present available projects with their spec status:

## Available Projects

| # | Project | Path | Specs |
|---|---------|------|-------|
| 1 | web-app | apps/web-app | PRD, Architecture, Tasks |
| 2 | mobile-app | apps/mobile-app | PRD |
| 3 | api-server | services/api | (none) |

For each project, check if <path>/specs/ exists and what spec files are present.

Use AskUserQuestion to ask which project to work on.

Step 3: Set Context

Set GROUNDWORK_PROJECT=<selected-name>
Set GROUNDWORK_PROJECT_ROOT=<absolute-path>
Persist selection via the persist script:
```
node ${PLUGIN_ROOT}/lib/persist-project.js <selected-name>
```
Where ${PLUGIN_ROOT} is the groundwork plugin directory (use the plugin root path from the session context). The script resolves its own terminal-pane identity internally — no env vars required.

Confirm: "Switched to project . Specs at <path>/specs/."

Step 4: Show Status

After switching, show the project's spec status:

PRD: exists / missing
Architecture: exists / missing
Tasks: exists / missing
Design System: exists / missing

Suggest next action based on what's available.