Codex with ChatGPT Planning Loop
XiaoDuoYa/codex-with-chatgpt
Uses ChatGPT in the browser as the planning and review brain for a Codex session, with Codex keeping all execution and ChatGPT reading the workspace through a bridge.
Internal, hook-triggered: gathers existing MCP items and schema gate requirements to set the definition floor before planning.
Install Pre Plan Workflow
$ npx skills add jpicklyk/task-orchestrator --skill pre-plan-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jpicklyk/task-orchestrator pre-plan-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-plugins/task-orchestrator/skills/pre-plan-workflow .claude/skills/pre-plan-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pre-plan-workflow" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/claude-plugins/task-orchestrator/skills/pre-plan-workflow into .claude/skills/pre-plan-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-plan-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jpicklyk/task-orchestrator/tree/main/claude-plugins/task-orchestrator/skills/pre-plan-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jpicklyk/task-orchestrator --skill pre-plan-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jpicklyk/task-orchestrator pre-plan-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude-plugins/task-orchestrator/skills/pre-plan-workflow .agents/skills/pre-plan-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pre-plan-workflow" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/claude-plugins/task-orchestrator/skills/pre-plan-workflow into .agents/skills/pre-plan-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-plan-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jpicklyk/task-orchestrator --skill pre-plan-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jpicklyk/task-orchestrator pre-plan-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude-plugins/task-orchestrator/skills/pre-plan-workflow .cursor/skills/pre-plan-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pre-plan-workflow" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/claude-plugins/task-orchestrator/skills/pre-plan-workflow into .cursor/skills/pre-plan-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-plan-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jpicklyk/task-orchestrator.git --path claude-plugins/task-orchestrator/skills/pre-plan-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jpicklyk/task-orchestrator --skill pre-plan-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jpicklyk/task-orchestrator pre-plan-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude-plugins/task-orchestrator/skills/pre-plan-workflow .gemini/skills/pre-plan-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pre-plan-workflow" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/claude-plugins/task-orchestrator/skills/pre-plan-workflow into .gemini/skills/pre-plan-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-plan-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jpicklyk/task-orchestrator pre-plan-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jpicklyk/task-orchestrator --skill pre-plan-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude-plugins/task-orchestrator/skills/pre-plan-workflow .github/skills/pre-plan-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pre-plan-workflow" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/claude-plugins/task-orchestrator/skills/pre-plan-workflow into .github/skills/pre-plan-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-plan-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jpicklyk/task-orchestrator --skill pre-plan-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jpicklyk/task-orchestrator pre-plan-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude-plugins/task-orchestrator/skills/pre-plan-workflow .opencode/skills/pre-plan-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pre-plan-workflow" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/claude-plugins/task-orchestrator/skills/pre-plan-workflow into .opencode/skills/pre-plan-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-plan-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pre-plan-workflow- GitHub stars
- 207
- Token cost
- ~1.2k tokens
- SKILL.md length
- 612 words
- Files
- 1
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- MIT
At a glance
Internal, hook-triggered: gathers existing MCP items and schema gate requirements to set the definition floor before planning.
- Works in 3 steps: Check Existing MCP State → Discover Note Schema Requirements → Plan with MCP Awareness
- Tasks that involve MCP servers
- SKILL.md covers Step 1: Check Existing MCP State, Step 2: Discover Note Schema…, Step 3: Plan with MCP Awareness and Continue with Plan Mode
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pre Plan Workflow is an agent skill from jpicklyk/task-orchestrator. Internal, hook-triggered: gathers existing MCP items and schema gate requirements to set the definition floor before planning.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering MCP servers and Planning. It works with Model Context Protocol. The repository describes itself as: Server-enforced workflow discipline for AI agents. An MCP server providing persistent work items, dependency graphs, quality gates, and actor attribution. Schemas define what… The licence is MIT.
When your agent uses it
- Tasks that involve MCP servers
- Tasks that involve Planning
Example prompts
- “/pre-plan-workflow”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b688ea0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pre Plan Workflow loads about 1.2k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 612 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jpicklyk/task-orchestrator at commit b688ea0, republished under its MIT licence (© jpicklyk). 612 words, ~1,179 tokens.
Download SKILL.mdSave it as
.claude/skills/pre-plan-workflow/SKILL.md (or your agent's skills folder).- name
- pre-plan-workflow
- description
- Internal, hook-triggered: gathers existing MCP items and schema gate requirements to set the definition floor before planning.
- user-invocable
- false
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 scope first from the SessionStart context. A ## Project Scope section carries a project rootId (scopes reads and anchors); a ## Personal Scope section carries a personal root (anchors only; reads stay unscoped). Without session context, read .taskorchestrator/config.yaml's top-level project.rootId (a file read, not an MCP call), which yields a project rootId only.
Call the health check to see what's already tracked:
get_context()When a project rootId is known, pass it to scope the check to this project: get_context(ancestorId="<rootId>"). In personal scope, or when no rootId is known, call unscoped exactly as shown — this is the same behavior as before project scoping existed.
If active or stalled items exist:
- Identify items related to the current request — avoid planning work that duplicates what's already tracked
- For each relevant active item, call
get_context(itemId=...)to inspect:- Note schema — which notes are expected for this item's tags
- Gate status — which required notes are filled vs. missing, and whether the item can advance
- Guidance key —
guidanceKeynames the first unfilled required note; resolve its authoring guidance viaquery_items(operation="schema", itemId=...)
If no items exist (clean slate):
- The definition floor is simply "no existing MCP state to account for"
- Proceed with planning, but still check Step 2 for schema awareness
Show full SKILL.md (334 more words)Show less
Step 2: Discover Note Schema Requirements
Read the file named by the session context's Config: line when there is one, otherwise .taskorchestrator/config.yaml in the project root (this is a file read, not an MCP call):
- If the file exists, list the discovered schemas and their required notes per phase
- Schemas are defined under
work_item_schemas:(preferred) ornote_schemas:(legacy) - Each schema key (e.g.,
feature-implementation,bug-fix) is a type identifier — set it as the item'stypefield to activate gate enforcement. Tags can be used for additional categorization but are no longer the primary schema activator. - Required queue-phase notes define what documentation must exist before work starts
- Required work-phase notes define what must be captured during implementation
- Use
guidanceKeyfromget_context(itemId=...), resolved viaquery_items(operation="schema", itemId=...), to understand how to author each note
If no config file exists, the project has no note schemas — items will be schema-free with no gate enforcement. Proceed with planning normally.
Minimal config example:
work_item_schemas:
feature-task:
notes:
- key: task-scope
role: queue
required: true
- key: implementation-notes
role: work
required: trueUse schemas to inform the plan: When a schema applies, each planned task should:
- Note which schema type will be applied at materialization (e.g.,
type: "feature-task") - Account for required notes — plan sections should naturally produce content that maps to required note keys
- Respect dependency ordering — which tasks block others (these become
BLOCKSedges)
Step 3: Plan with MCP Awareness
Structure the plan knowing it will be materialized into MCP items after approval:
- Each planned task should map to one work item with clear boundaries — a single unit of work a subagent can own
- Account for dependency ordering — which tasks block others (these become
BLOCKSedges) - Consider the hierarchy — a root container item with child task items is the standard pattern
Continue with Plan Mode
The prerequisite is complete. Now proceed with plan mode's normal workflow — explore the codebase, understand existing patterns, and design your implementation approach. Use the definition floor from Steps 1-3 to inform your plan.
Once the plan is approved, the post-plan hook will guide you through materialization and implementation dispatch. Do not materialize before approval.
© jpicklyk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in claude-plugins/task-orchestrator/skills/pre-plan-workflow of jpicklyk/task-orchestrator.
Open the folder on GitHubat commit b688ea0
Compare with similar skills
Pre Plan Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pre Plan Workflow this skilljpicklyk/task-orchestrator | 207 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Codex with ChatGPT Planning LoopXiaoDuoYa/codex-with-chatgpt | 7.1k | — | ~11k | Automated safety check: Notes | MIT | |
| Agentic Tool Integrationsamugit83/redamon | 2.9k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Upload Artifactclosedloop-ai/claude-plugins | 122 | — | ~1.4k | Automated safety check: Notes | Apache-2.0 | |
| Spring PlanningAmplicode/spring-skills | 126 | — | ~3.7k | Automated safety check: Pass | None | |
| MCP Server Builderanthropics/skills | 180k | 62 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Agentic Tool Integration
samugit83/redamon
Wiring a new tool the AI agent can call (not the recon pipeline): the tool registry, the phase map, the hardcoded dispatch chokepoint, and the duplicated execution paths that make a tool work in…
Upload Artifact
closedloop-ai/claude-plugins
Upload a file as a ClosedLoop document (PRD, implementation plan, feature, or template).
Spring Planning
Amplicode/spring-skills
Create structured implementation plan in docs/plans/. An agent skill from Amplicode/spring-skills.
- Official
MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
More from jpicklyk/task-orchestrator
All 28 skills in this repoTask Orchestrator Server Setup
jpicklyk/task-orchestrator
Walks through how to launch and reach the MCP Task Orchestrator server container: transport, REST API, port publishing, config mounts and config-sync.
Run Wave
jpicklyk/task-orchestrator
Resolves ready MCP work items into a run plan, shows it to you, then executes it through the Workflow tool or direct subagent dispatch, with post-run verification.
Adopt Project Scope Migration
jpicklyk/task-orchestrator
Migrates an existing unscoped Task Orchestrator database to the project-scoping convention in place, creating one project anchor root and re-parenting work trees under it after a mandatory dry run.
Bulk Task Completion
jpicklyk/task-orchestrator
Completes or cancels a whole feature subtree, a named list of items, or a batch of stale work items at once, previewing the impact and warning before force-completing anything active.
Task Orchestrator Item Creator
jpicklyk/task-orchestrator
Creates an MCP work item from conversation context, anchoring it under the right container, inferring type and priority and pre-filling the required notes.
Work Item Dependency Manager
jpicklyk/task-orchestrator
Views, creates, deletes and diagnoses BLOCKS, IS_BLOCKED_BY and RELATES_TO links between MCP work items, including why an item cannot start.
Related
Works with
Categories
Questions about Pre Plan Workflow
What does Pre Plan Workflow do?
Internal, hook-triggered: gathers existing MCP items and schema gate requirements to set the definition floor before planning. Pre Plan Workflow is an agent skill from jpicklyk/task-orchestrator. Internal, hook-triggered: gathers existing MCP items and schema gate requirements to set the definition floor before planning.
When should I use Pre Plan Workflow?
Pre Plan Workflow fits situations like: tasks that involve MCP servers; tasks that involve Planning.
How do I install Pre Plan Workflow in Claude Code?
Run `npx skills add jpicklyk/task-orchestrator --skill pre-plan-workflow -a claude-code`. Or copy the skill folder (claude-plugins/task-orchestrator/skills/pre-plan-workflow in jpicklyk/task-orchestrator) into .claude/skills/pre-plan-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Pre Plan Workflow in Codex?
Run `npx skills add jpicklyk/task-orchestrator --skill pre-plan-workflow -a codex`. Or copy the skill folder (claude-plugins/task-orchestrator/skills/pre-plan-workflow in jpicklyk/task-orchestrator) into .agents/skills/pre-plan-workflow in your project. Codex loads it when a task matches its description.
Can I use Pre Plan Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jpicklyk/task-orchestrator --skill pre-plan-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pre-plan-workflow, .gemini/skills/pre-plan-workflow, .github/skills/pre-plan-workflow and .opencode/skills/pre-plan-workflow in your project.
What does Pre Plan Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Pre Plan Workflow is instructions for the agent only.
Does Pre Plan Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Pre Plan Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pre Plan Workflow use?
Pre Plan Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pre Plan Workflow use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pre Plan Workflow?
Skills that share tags, products or a category with Pre Plan Workflow: Codex with ChatGPT Planning Loop (XiaoDuoYa/codex-with-chatgpt, 7.1k stars), Agentic Tool Integration (samugit83/redamon, 2.9k stars), Upload Artifact (closedloop-ai/claude-plugins, 122 stars) and Spring Planning (Amplicode/spring-skills, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pre Plan Workflow?
jpicklyk (a GitHub user) maintains it in jpicklyk/task-orchestrator, which has 207 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 6, 2026.
Source: jpicklyk/task-orchestrator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.