Menú
Deploy the framework to a target project by replacing shared dirs with symlinks (junctions) back to the framework repo. Run once after copying .claude/ to a new project.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Create well-structured atomic commits with conventional commit messages. Use when ready to commit working changes.
Write a feature spec from requirements in .claude/input/. Use when starting a new feature, before implementation begins.
Orchestrate the full spec → implement → review → fix → commit pipeline. Use when shipping a complete feature end-to-end.
Break a concept document, draft, or product brief into independent PRDs that each feed into /ship. Use when input contains multiple features or a big-picture vision.
Ship decomposed PRDs in parallel. Analyzes file conflicts, groups into batches, runs /ship in isolated worktrees, merges results. Use after /decompose.
Implement a feature from a spec file in .claude/specs/. Use after a spec is written and approved.
| name | deploy |
| description | Deploy the framework to a target project by replacing shared dirs with symlinks (junctions) back to the framework repo. Run once after copying .claude/ to a new project. |
| argument-hint | <target-project-path> |
| model | sonnet |
| effort | medium |
Replace shared framework directories in a target project with junctions pointing back to this framework repo, so updates propagate automatically.
.claude/ directory (either copied from Framework or created fresh)Shared (symlinked) — maintained in Framework, identical across all projects:
| Dir | Contents |
|---|---|
skills/ | All 21 skill definitions |
agents/ | Subagent personas |
rules/ | Auto-loaded instructions (instincts) |
Local (never symlinked) — project-specific, stay as regular directories:
| Dir | Why local |
|---|---|
context/ | Project-specific knowledge base |
specs/ | Feature specs for this project |
reviews/ | Review reports for this project |
input/ | Requirements for this project |
references/ | Research material for this project |
hooks/ | Project-specific lifecycle hooks |
handoffs/ | Session state (gitignored) |
docs/ | Generated docs (project-specific) |
worktrees/ | Git worktree state |
settings.json | Project-specific settings |
settings.local.json | Local overrides |
metrics-pipeline.csv | Ship pipeline run log |
metrics-scout.csv | Scout/harvest run log |
Validate target path. $ARGUMENTS must be an absolute path or relative path to a project directory. Resolve it to absolute. Confirm <target>/.claude/ exists. If not, ask: "No .claude/ directory found at <target>. Copy the full framework first? (Y/N)" — if Y, copy the entire .claude/ directory to the target, then continue.
Detect OS. Run uname -s to detect the platform:
cmd.exe //c "mklink /J <link> <target>" (junctions — no admin rights needed)ln -s <target> <link> (standard symlinks)Detect framework root. The framework repo root is the working directory where this skill is invoked. Store as $FRAMEWORK_ROOT. Verify $FRAMEWORK_ROOT/.claude/skills/ exists.
For each shared directory (skills, agents, rules):
a. Check if <target>/.claude/<dir> is already a symlink/junction pointing to the correct source:
cmd.exe //c "dir <target>\.claude\" | grep <dir> and look for <JUNCTION> markerreadlink <target>/.claude/<dir><dir>/ — already linked ✓b. Check if <target>/.claude/<dir> exists as a regular directory:
mv <target>/.claude/<dir> <target>/.claude/<dir>.bak<dir>/ — backed up existing to <dir>.bakc. Create the junction/symlink:
cmd.exe //c "mklink /J <target>\.claude\<dir> <framework>\.claude\<dir>"ln -s <framework>/.claude/<dir> <target>/.claude/<dir>d. Verify the link works by listing its contents: ls <target>/.claude/<dir>/
Ensure local directories exist. For each local directory (context, specs, reviews, input, references, hooks, handoffs, docs), create it if missing: mkdir -p <target>/.claude/<dir>
Strip project-scoped lessons. If <target>/.claude/context/lessons.md exists, read it and remove all entries that have scope: project or no scope tag (legacy entries are project-scoped by default). Keep only scope: framework entries. This prevents project-specific lessons from the Framework repo from leaking into target projects.
Clean up stale files. If <target>/.claude/context/instincts.md exists as a regular file (not via the rules/ symlink), delete it — rules/instincts.md is now provided through the symlink and having both causes duplication.
Report.
## Deploy complete
Target: <target-path>
| Directory | Status |
|-------------|---------------------------|
| skills/ | linked → Framework ✓ |
| agents/ | linked → Framework ✓ |
| rules/ | linked → Framework ✓ |
| commands/ | linked → Framework ✓ |
| context/ | local (kept as-is) ✓ |
| specs/ | local (kept as-is) ✓ |
| ... | ... |
Backups (if any): <list .bak dirs or "none">
The target project now receives framework updates automatically.
To update: pull changes in the Framework repo — all linked projects get them instantly.