cursor-implement-exec-plan

Delegates a checked-in ExecPlan to Cursor Agent with Composer 2.5 for implementation.

2|Updated May 6, 2026
One-click install
npx skills add https://github.com/bpcakes/jig-skills --skill cursor-implement-exec-plan-bpcakes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cursor-implement-exec-plan
Source: https://github.com/bpcakes/jig-skills/tree/main/plugins/jig-exec-plans/skills/cursor-implement-exec-plan
Command: npx skills add https://github.com/bpcakes/jig-skills --skill cursor-implement-exec-plan-bpcakes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? It hands off implementation of a checked-in ExecPlan to Cursor Agent when the user explicitly requests Cursor, avoiding vague chat-based delegation and unmanaged long-running agent sessions. ## Core Features & Use Cases - Controlled Delegation: Launches cursor-agent with a stable implementation prompt, defaulting to the composer-2.5 model, only when Cursor is explicitly requested. - Scoped Execution: Supports whole-plan or single-milestone implementation, optional isolated Git worktrees, and extra user instructions passed through to Cursor. - Verified Continuation: Tracks live sessions, verifies worktree checkouts via Git, reconciles ExecPlan progress records, and continues remaining work without duplicate launches. - Use Case: A user with a committed ExecPlan in plans/feature.md asks to implement it with Cursor; the skill runs the bundled launcher, monitors the session, validates results, and reports files changed and remaining items. ## Quick Start Ask the agent to implement the ExecPlan at plans/feature.md using Cursor Agent and report the changed files and validation results.

Frequently Asked Questions about cursor-implement-exec-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement an ExecPlan with Cursor Agent?

Provide the path to a checked-in ExecPlan Markdown file and explicitly request Cursor implementation. The skill runs the bundled launcher, which invokes cursor-agent with the composer-2.5 model and a structured implementation prompt.

How do I implement only one milestone of an ExecPlan?

Pass the milestone name through the launcher's --milestone option. Cursor then completes only that named milestone and its acceptance criteria, without implementing later milestones.

Can Cursor Agent run in an isolated Git worktree?

Yes, the launcher supports a --worktree option that creates an isolated Cursor worktree. The ExecPlan must be committed or otherwise available in the worktree base, and the launcher verifies the registered checkout via git worktree list.

What happens if cursor-agent is not installed or the model is unavailable?

The launcher fails with an explicit error if cursor-agent is missing from PATH or the requested model is not listed by cursor-agent --list-models. It does not silently fall back to a different implementation agent.

When is force mode used with cursor-agent?

Force mode passes --force to cursor-agent for unattended command approval, but only when the user explicitly asked for unattended, force, or yolo-style execution. It is never enabled by default.