project-register¶

Plugin: core-standards
Category: Other
Command: /project-register

/vt-c-project-register — Project Registration¶

Register the current working directory as a tracked project in the V025-claude-toolkit registry. This enables:

/vt-c-toolkit-review scanning for procedure improvement proposals
/vt-c-project-sync aggregation of journals and proposals
Cross-project learning and pattern detection

Invocation¶

/vt-c-project-register          # Interactive registration
/vt-c-project-register --check  # Check registration status only (no changes)

Execution Instructions¶

Step 1: Locate Toolkit Registry¶

TOOLKIT_ROOT="TOOLKIT_ROOT"
REGISTRY="$TOOLKIT_ROOT/intake/projects.yaml"

If $REGISTRY does not exist:

Toolkit registry not found at $REGISTRY.
Is V025-claude-toolkit installed?

Exit cleanly.

Step 2: Check Current Registration¶

Read $REGISTRY and check if the current working directory ($PWD) appears in the projects list.

If already registered:

This project is already registered in the toolkit.

  Name: [name]
  Type: [type]
  Registered: [date]
  Location: [location]
  Last synced: [date or "never"]

No action needed.

Exit cleanly.

If --check argument provided: Display status and exit (do not proceed to Step 3).

Step 3: Detect Project Metadata¶

Auto-detect the following:

Field	Detection Method
`path`	`$PWD`
`name`	`basename $PWD`
`type`	Infer from directory contents (see below)
`location`	Infer from path and git presence (see below)

Type inference: - Has src/ or package.json or Gemfile or Cargo.toml or go.mod or pom.xml → coding - Has .design-state.yaml with current_phase: pd-* → design - Has docs/deliverables/ or docs/ but no source code directories → knowledge - Has both source code and .design-state.yaml or PRD → mixed - Otherwise → ask user

Location inference: - Has .git/ directory → local-git - Path contains OneDrive or CloudStorage or iCloud → local-folder - Otherwise → local-folder

Step 4: Confirm with User¶

Use AskUserQuestion to present detected values:

Register this project in the V025 toolkit?

  Path: <current-working-directory>
  Name: [detected name]
  Type: [detected type]
  Location: [detected location]

Options: - Register — Proceed with detected values - Edit name/type — Change name or type before registering - Cancel — Do not register

If "Edit name/type": Use AskUserQuestion to let user pick the type: - coding — Software development project - design — Product design project - knowledge — Documentation, research, knowledge work - mixed — Combination of code and non-code work

Then ask for name (or accept the detected default).

Step 5: Write Registration¶

Append to intake/projects.yaml:

  - path: [PROJECT_PATH]
    name: [PROJECT_NAME]
    type: [PROJECT_TYPE]
    registered: [YYYY-MM-DD]
    location: [LOCATION]
    last_synced: null

CRITICAL: Match the existing indentation exactly (2 spaces for list items, 4 spaces for fields). Append after the last entry, before any trailing newline.

Step 6: Create Project Infrastructure¶

In the project directory:

mkdir -p docs/toolkit-proposals

If docs/toolkit-proposals/.gitkeep does not exist, create it:

touch docs/toolkit-proposals/.gitkeep

Step 7: Confirm Registration¶

Project registered successfully.

  Name: [name]
  Type: [type]
  Location: [location]

What this enables:
  - /vt-c-toolkit-review will scan docs/toolkit-proposals/ for improvement proposals
  - /vt-c-project-sync will aggregate journals and proposals to V025
  - /vt-c-journal entries marked as "process observation" will flow to V025 intake

Next: Continue with your current workflow.

Edge Cases¶

Scenario	Handling
Toolkit not found at expected path	Exit with message, do not fail silently
Project already registered	Show status, exit cleanly
Path contains spaces	Use quoted paths in all bash operations
Non-git project (OneDrive)	Set `location: local-folder`, skip git-related checks
User cancels	Exit cleanly, no changes made

Integration Points¶

Skill	Relationship
`/vt-c-scaffold`	Also registers projects (during initial scaffolding via /0-init)
`/vt-c-toolkit-review`	Scans registered projects for `docs/toolkit-proposals/`
`/vt-c-project-sync`	Aggregates from all registered projects
`/vt-c-journal`	Routes process observations to V025 for registered projects