Copy a command from Product Forge to user or project level
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill copy-command67
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Copy a command from Product Forge plugins to your user-level (~/.claude/) or project-level (.claude/) directory.
# List available commands
/copy-command
# Copy to project (default)
/copy-command product-design:create-prd
# Copy to user level
/copy-command git-workflow:commit --user
# Explicit project level
/copy-command devops-data:create-rfc --project<plugin>:<command-name> - The command to copy in plugin:name format--user - Copy to ~/.claude/{plugin}/commands/{name}.md--project - Copy to .claude/{plugin}/commands/{name}.md (default)Commands are single markdown files (.md) containing:
# Project-level (default)
.claude/
└── git-workflow/
└── commands/
└── commit.md
# User-level (--user)
~/.claude/
└── git-workflow/
└── commands/
└── commit.mdWhen the user runs this command:
Scan Product Forge plugins cache for all available commands:
ls ~/.claude/plugins/cache/product-forge-marketplace/*/commands/*.md 2>/dev/nullFor each plugin with commands, list them with descriptions:
description{plugin}:{command-name} - {description}Display formatted list:
Available commands from Product Forge:
product-design:
create-prd - Interactive PRD creation wizard
create-qa-test - Create a new QA test procedure
task-focus - Focus on a specific task with context
...
git-workflow:
commit - Guided git commit with atomic commit analysis
rebase - Rebase local changes on remote updates
code-review - Review code changes for issues
...
devops-data:
create-rfc - Create a new RFC technical specification
create-tech-spec - Create a new Technical Specification
...
Usage: /copy-command <plugin>:<command-name> [--user | --project]Parse arguments:
plugin and command-name from <plugin>:<command-name> format--user or --project (default)Locate source command:
SOURCE=~/.claude/plugins/cache/product-forge-marketplace/{plugin}/commands/{command-name}.mdDetermine destination path:
--project: .claude/{plugin}/commands/{command-name}.md--user: ~/.claude/{plugin}/commands/{command-name}.mdCheck if destination exists:
Command '{command-name}' already exists at {destination}.
Options:
- Overwrite: Replace existing command
- Rename: Save as {command-name}-copy.md
- Cancel: Abort operationCreate destination directory structure:
mkdir -p {destination_dir}Copy command file:
cp {source} {destination}Confirm success:
Command copied successfully!
Source: ~/.claude/plugins/cache/product-forge-marketplace/{plugin}/commands/{command-name}.md
Destination: {destination}
The command is now available as /{command-name} in your {project|user} configuration.0ebe7ae
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.