agentleFS
maxwell2732maxwell2732/claudecode-research-harness-workflow/skills/workflow-guide/SKILL.md

workflow-guide

Skill42 starsChanged 6 days agoMITView on GitHub

Explicit helper for Cursor PM ↔ Claude Code two-agent workflow guidance. Do NOT load for: solo implementation, workflow setup, handoff execution, or general process coaching.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If CI fails 3 times in a row:

    line 136

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Workflow Guide Skill

A skill providing guidance on the Cursor ↔ Claude Code 2-agent workflow.


Trigger Phrases

This skill is invoked by the following phrases:

  • "Tell me about the workflow"
  • "How do I collaborate with Cursor?"
  • "Explain the work process"
  • "How should I proceed?"
  • "how does the workflow work?"
  • "explain 2-agent workflow"

Overview

This skill explains the role assignment and collaboration method between Cursor (PM) and Claude Code (Worker).


2-Agent Workflow

Role Assignment

AgentRoleResponsibilities
CursorPM (Project Manager)Task assignment, review, production deploy decisions
Claude CodeWorkerImplementation, testing, CI fixes, staging deploy

Workflow Diagram

┌─────────────────────────────────────────────────────────┐
│                    Cursor (PM)                          │
│  - Add tasks to Plans.md                                │
│  - Delegate work to Claude Code (/handoff-to-claude)    │
│  - Review completion reports                            │
│  - Make production deploy decisions                     │
└─────────────────────┬───────────────────────────────────┘
                      │ Task delegation
                      ▼
┌─────────────────────────────────────────────────────────┐
│                  Claude Code (Worker)                   │
│  - Execute tasks with /work (parallel execution)        │
│  - Implement → Test → Commit                            │
│  - Auto-fix CI failures (up to 3 times)                 │
│  - Completion report with /handoff-to-cursor            │
└─────────────────────┬───────────────────────────────────┘
                      │ Completion report
                      ▼
┌─────────────────────────────────────────────────────────┐
│                    Cursor (PM)                          │
│  - Review changes                                       │
│  - Verify on staging                                    │
│  - Execute production deploy (after approval)           │
└─────────────────────────────────────────────────────────┘

Task Management with Plans.md

Marker List

MarkerMeaningSet by
pm:requestedRequested by PM (compatible: cursor:requested)PM (Cursor/PM Claude)
cc:TODOClaude Code not startedEither
cc:WIPClaude Code in progressClaude Code
cc:doneClaude Code completeClaude Code
pm:confirmedPM confirmation complete (compatible: cursor:confirmed)PM (Cursor/PM Claude)
cursor:requested(compatible) Same as pm:requestedCursor
cursor:confirmed(compatible) Same as pm:confirmedCursor
blockedBlockedEither

Task State Transitions

pm:requested → cc:WIP → cc:done → pm:confirmed

Key Commands

Claude Code Side

CommandPurpose
/harness-initProject setup
/plan-with-agentPlanning/task breakdown
/workTask execution (parallel execution supported)
/handoff-to-cursorCompletion report (to Cursor PM)
/sync-statusStatus check

Skills (Auto-invoked in Conversation)

SkillTrigger Example
handoff-to-pm"Report completion to PM"
handoff-to-impl"Hand off to implementation"

Cursor Side (For Reference)

CommandPurpose
/handoff-to-claudeDelegate tasks to Claude Code
/review-cc-workReview completion reports

CI/CD Rules

Claude Code's Scope of Responsibility

  • ✅ Up to staging deploy
  • ✅ Auto-fix CI failures (up to 3 times)
  • ❌ Production deploy is prohibited

3-Strike Rule

If CI fails 3 times in a row:

  1. Stop auto-fix
  2. Generate escalation report
  3. Defer decision to Cursor

Frequently Asked Questions

Q: What if Cursor is not available?

A: Even when working alone, task management with Plans.md is recommended. Perform production deploys manually and carefully.

Q: What if a task is unclear?

A: Request clarification from Cursor, or use /sync-status to organize the current state.

Q: What if CI keeps failing?

A: Do not auto-fix more than 3 times; escalate to Cursor.


Related Documents

  • AGENTS.md - Detailed role assignments
  • CLAUDE.md - Claude Code specific configuration
  • Plans.md - Task management file

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.