Pre-Plan Workflow

Pre-Plan Workflow 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 Pre-Plan Workflow

Copy Pre-Plan Workflow 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/pre-plan-workflow ~/.claude/skills/pre-plan-workflow

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/pre-plan-workflow/SKILL.md in jpicklyk/task-orchestrator
Installs to: ~/.claude/skills/pre-plan-workflow
Collection: One of 25 skills cataloged from this repository
Category: Automation — 1956 skills

What Pre-Plan Workflow does

Pre-Plan Workflow gathers existing MCP items and schema requirements before planning. Use it when entering plan mode to avoid duplicate work and account for required notes and gates.

Pre-Plan Workflow is cataloged under Automation on DirSkills. Pre-Plan Workflow comes from a repository tagged ai-coding-assistant, ai-development, ai-harness, ai-memory and ai-tools.

Documentation

README

Excerpt

Pre-Plan Workflow — Definition Floor

When entering plan mode, use the MCP to set the definition floor before writing your plan.

The definition floor is the baseline of existing work, documentation requirements, and gate constraints that the plan must account for.

If MCP is unreachable: Proceed with planning based on conversation context. Note in the plan that MCP state could not be verified — existing work may overlap. Re-check after MCP reconnects.

Step 1: Check Existing MCP State

Resolve the project rootId first: check session context for a rootId injected by the SessionStart hook, or read .taskorchestrator/config.yaml's top-level project.rootId (a file read, not an MCP call).

Call the health check to see what's already tracked:

get_context()

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

Frequently asked about Pre-Plan Workflow

What else does jpicklyk publish alongside Pre-Plan Workflow?
Pre-Plan Workflow is one of 25 skills that DirSkills catalogs from jpicklyk/task-orchestrator, the repository it ships in. Its siblings there include API Compatibility Review, Adopt Project Scope and Batch Complete. Each one is a separate skill with its own page in this directory, installs the same way Pre-Plan Workflow 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 Pre-Plan Workflow compare to other Automation skills?
Pre-Plan Workflow ranks #1732 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 Pre-Plan Workflow against them. Open each page to compare what they document and how they install.