Packmind Onboard

packmind-onboard

Run "packmind --version" to get the current cli installation.

Find the highest version at or below the cli version in this list:

• 0.16.0
• 0.23.0
• 0.35.0 Remember this value as $PACKMIND_CLI_VERSION for the rest of the skill.

Action skill. Provides complete automated onboarding for Packmind:

1. Creates or selects a package
2. Analyzes codebase for patterns
3. Generates draft Standards and Commands
4. Creates items via CLI

Automatic package creation when none exist, user selection when packages are available.

Guarantees

• Read-only analysis. Analysis phase does not modify any project files.
• Drafts before creation. All items are written as drafts first, allowing review before creation.
• Preserve existing. Never overwrite existing artifacts. If a slug already exists, create -2, -3, etc.
• Evidence required. Every reported insight must include file-path evidence (and line ranges when feasible).
• Focused output. Max 5 Standards and 5 Commands generated per run.
• Graceful failure. Partial failures don't lose successful work; failed drafts are preserved.
• User control. When packages exist, users confirm package selection before creation.

Definitions

• Pattern (non-linter): a convention a linter cannot reliably enforce (module boundaries, cross-domain communication, workflow parity, error semantics, etc).
• Evidence: path[:line-line] entries; omit line ranges only when the file isn't text-searchable.

Step 0 — Introduction

Print exactly:

I'll start the Packmind onboarding process. I'll create your first standards and commands and send them to your Packmind organization. This usually takes ~3 minutes.

Step 1 — Get Repository Name

Get the repository name for package naming:

basename "$(git rev-parse --show-toplevel)"

Remember this as the repository name for package creation in Step 2.

Also run packmind whoami and extract the Host: value from the output. Remember this URL for the completion summary.

Step 2 — Package Handling

Handle package creation or selection.

Check existing packages

List available packages by following packmind-versions/$PACKMIND_CLI_VERSION/list-packages.md.

Parse the output to get package names and slugs.

No packages exist

Auto-create a package using the repository name. Follow packmind-versions/$PACKMIND_CLI_VERSION/create-package.md using ${REPO_NAME}-standards as the package name.

The create-package step will determine the space. Capture the chosen space slug as $SPACE_SLUG and the new package slug as $PACKAGE_SLUG.

Print:

No existing packages found — created a new one: ${REPO_NAME}-standards

One package exists

Ask via AskUserQuestion:

• "Add to {package-name}?"
• "Create new package instead"

Multiple packages exist

Ask via AskUserQuestion:

• List each existing package as an option
• Include "Create new package" option

If "Create new package" is selected

• Ask for package name (suggest ${REPO_NAME}-standards as default)
• Follow packmind-versions/$PACKMIND_CLI_VERSION/create-package.md using the chosen name.
• The create-package step will determine the space. Capture the chosen space slug as $SPACE_SLUG and the new package slug as $PACKAGE_SLUG.

If an existing package is selected

Follow packmind-versions/$PACKMIND_CLI_VERSION/select-package.md.

After this step

Remember $PACKAGE_SLUG (the slug of the selected/created package) and $SPACE_SLUG for later reference — they will be used together in Step 9 to ensure items are added to the correct package in the correct space (as @$SPACE_SLUG/$PACKAGE_SLUG).

Step 3 — Announce

Print exactly:

packmind-onboard: analyzing codebase (read-only)
Target package: [package-name]

Step 4 — Detect Existing Packmind and Agent Configuration

Before analyzing, detect and preserve any existing Packmind/agent configuration.

Glob (broad, future-proof)

Glob for markdown in these roots (recursive):

• .packmind/**/*.md
• .claude/**/*.md
• .agents/**/*.md
• **/skills/**/*.md
• **/rules/**/*.md