home / skills / chachamaru127 / claude-code-harness / cc-cursor-cc

cc-cursor-cc skill

/skills/cc-cursor-cc

This skill orchestrates brainstorming transfer between Claude Code and Cursor PM to validate plans and update Plans.md for seamless handoffs.

npx playbooks add skill chachamaru127/claude-code-harness --skill cc-cursor-cc

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.1 KB
---
name: cc-cursor-cc
description: "Cursor PMでアイデアを検証し、Plans.mdを更新してバトンタッチ。2-Agentワークフロー対応。"
description-en: "Validates brainstormed ideas with Cursor PM, updates Plans.md, then handoff back. 2-Agent workflow support."
description-ja: "Cursor PMでアイデアを検証し、Plans.mdを更新してバトンタッチ。2-Agentワークフロー対応。"
allowed-tools: ["Read", "Write", "Edit", "Bash"]
user-invocable: false
---

# CC-Cursor-CC Skill (Plan Validation Round Trip)

Supports the flow of sending brainstormed content from Claude Code to **Cursor (PM)** for feasibility validation.

## Prerequisites

This skill assumes **2-agent operation**.

| Role | Agent | Description |
|------|-------|-------------|
| **PM** | Cursor | Validate plans, update Plans.md |
| **Impl** | Claude Code | Brainstorming, implementation |

## Execution Flow

### Step 1: Extract Brainstorming Context

Extract from recent conversation:
1. **Goal** (feature/purpose)
2. **Technology choices**
3. **Decisions made**
4. **Undecided items**
5. **Concerns**

### Step 2: Add Provisional Tasks to Plans.md

```markdown
## 🟠 Under Validation: {{Project}} `pm:awaiting-validation`

### Provisional Tasks (To Validate)
- [ ] {{task1}} `awaiting-validation`
- [ ] {{task2}} `awaiting-validation`

### Undecided Items
- {{item1}} → **Requesting PM decision**
```

### Step 3: Generate Validation Request for Cursor

Generate text to copy-paste to Cursor:

```markdown
## 📋 Plan Validation Request

**Goal**: {{summary}}

**Provisional tasks**:
1. {{task1}}
2. {{task2}}

### ✅ Requesting Cursor (PM) to:
1. Validate feasibility
2. Break down tasks
3. Decide undecided items
4. Update Plans.md (awaiting → cc:TODO)
```

### Step 4: Guide Next Action

1. Copy & paste request to **Cursor**
2. Run `/plan-with-cc` in Cursor
3. Cursor updates Plans.md
4. Cursor runs `/handoff-to-claude`
5. Copy & paste back to **Claude Code**

## Overall Flow

```
Claude Code (Brainstorm)
    ↓ /cc-cursor-cc
Cursor (PM validates & breaks down)
    ↓ /handoff-to-claude
Claude Code (/work implements)
```

Overview

This skill coordinates a plan-validation handoff between Claude Code (implementation) and Cursor (PM) in a 2-agent workflow. It captures brainstorming context, injects provisional tasks into Plans.md, and prepares a validation request that the PM can act on. The goal is to close the loop: get feasibility feedback, have Cursor update Plans.md, and return a clarified plan to Claude Code for implementation.

How this skill works

The skill extracts goal, tech choices, decisions, undecided items, and concerns from recent conversation. It writes a provisional “under validation” section into Plans.md with awaiting-validation tasks and lists undecided items needing PM decisions. Then it generates a concise, copy-pasteable validation request for Cursor that asks the PM to validate feasibility, break down tasks, decide undecided items, and update Plans.md. Finally, it guides the operator through the handoff steps to close the round trip.

When to use it

  • After an internal Claude Code brainstorming session that produced tasks or design proposals
  • When you need a product/PM feasibility check before implementation
  • When Plans.md must reflect provisional tasks awaiting PM review
  • When two-agent coordination is required (Cursor PM + Claude Code Impl)
  • Before starting significant implementation work to prevent rework

Best practices

  • Keep the extracted context focused: state the goal, tech choices, decisions, undecided items, and concerns in short bullet form
  • Add only clear provisional tasks to Plans.md labeled `awaiting-validation` to avoid clutter
  • Use the generated markdown verbatim when messaging Cursor to minimize misunderstandings
  • Ask Cursor to run `/plan-with-cc` and `/handoff-to-claude` so Plans.md transitions cleanly from awaiting to actionable
  • Keep the handoff loop tight: copy Cursor’s updated Plans.md back into Claude Code promptly for implementation

Example use cases

  • After generating feature ideas in Claude Code, create provisional tasks and request Cursor validation before coding
  • When multiple technical options exist, surface undecided items for PM choice and feasibility review
  • For milestone planning: mark work as `pm:awaiting-validation` to prevent premature implementation
  • When cross-functional review is needed to break large brainstorm tasks into concrete tickets

FAQ

Does this skill require a specific repository structure?

No specific repo layout is required, but it expects a Plans.md file that Cursor and Claude Code will read and update.

Can this be used with more than two agents?

The skill is designed for a 2-agent workflow (Cursor PM and Claude Code Impl). Extending to more agents may require adapting the handoff steps.