Adopt Project Scope

Adopt Project Scope is an Automation skill for Claude Code, published by jpicklyk in task-orchestrator.

206 stars20 forkson jpicklyk/task-orchestratorAdded 2026/09/05Repository updated 2026/08/04

ai-coding-assistantai-developmentai-harnessai-memoryai-toolsclaudeclaude-codeclaude-desktopcontext-persistencedeveloper-toolsharness-engineeringharness-frameworkmcpmcp-servermodel-context-protocoltask-managementvibe-codingworkflow-automation

Install in seconds

Install Adopt Project Scope

Copy Adopt Project Scope into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/jpicklyk/task-orchestrator/tree/main/claude-plugins/task-orchestrator/skills/adopt-project-scope ~/.claude/skills/adopt-project-scope

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/jpicklyk/task-orchestrator.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: claude-plugins/task-orchestrator/skills/adopt-project-scope/SKILL.md in jpicklyk/task-orchestrator
Installs to: ~/.claude/skills/adopt-project-scope
Collection: One of 25 skills cataloged from this repository
Category: Automation — 1956 skills

What Adopt Project Scope does

Adopt Project Scope migrates an existing unscoped Task Orchestrator database to project scoping in place. It creates or attaches a project root, re-parents existing work trees, and writes the root UUID to config.yaml when setting up a workspace for multiple projects.

Adopt Project Scope is cataloged under Automation on DirSkills. Adopt Project Scope comes from a repository tagged ai-coding-assistant, ai-development, ai-harness, ai-memory and ai-tools.

Documentation

README

Excerpt

Adopt Project Scope — In-Place Migration to Project Scoping

Take an existing, unscoped database (many depth-0 roots, no project anchor) and migrate it in place to the project-scoping convention: one type=project root that owns the workspace's work trees, with its UUID written back to .taskorchestrator/config.yaml under a project: block. Global containers (retrospectives, observations) stay at depth 0; test artifacts are flagged for cleanup, never moved or deleted.

This is a destructive-by-execution skill: the EXECUTE step re-parents real items. It defaults to a dry run and never mutates anything without an explicit confirmation. The only thing it ever deletes is its own throwaway server-probe tree.

This is the opening of the README. Read the full README on GitHub.

Commands Adopt Project Scope provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

/work-summary
/batch-complete
/mcp

Frequently asked about Adopt Project Scope

What else does jpicklyk publish alongside Adopt Project Scope?
Adopt Project Scope is one of 25 skills that DirSkills catalogs from jpicklyk/task-orchestrator, the repository it ships in. Its siblings there include API Compatibility Review, Batch Complete and Configure Server. Each one is a separate skill with its own page in this directory, installs the same way Adopt Project Scope does, and is maintained by jpicklyk in that same repository. The rest of the collection is listed on the jpicklyk/task-orchestrator page.
How does Adopt Project Scope compare to other Automation skills?
Adopt Project Scope ranks #1723 by stars among the 1956 Automation skills in this catalog. The most-starred ones next to it are Autonomous Loops, Autonomous Agent Harness and Automation Audit Ops. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Adopt Project Scope against them. Open each page to compare what they document and how they install.