cc-cursor-cc_skill

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