explainx.ai
workshops ↗
Productivity

parallel-agent-contracts

When launching parallel agents for code implementation, prevent type duplication.

parcadei/continuous-claude-v3Updated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

3.7K

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill parallel-agent-contracts

0

installs

0

this week

3.7K

stars

View on GitHub
parallelagentcontracts
0 commentsJoin discussion →

Installation Guide

How to use parallel-agent-contracts on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your machine
  • ›Node.js 16+ with npm — verify with node --version
  • ›Active project directory where you want to add parallel-agent-contracts
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill parallel-agent-contracts

Fetches parallel-agent-contracts from parcadei/continuous-claude-v3 and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/parallel-agent-contracts

Restart Cursor to activate parallel-agent-contracts. Access via /parallel-agent-contracts in your agent's command palette.

⚠

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

›View source on GitHub›Skills CLI docs›About Cursor›What are agent skills?

Documentation

Parallel Agent Type Contracts

When launching parallel agents for code implementation, prevent type duplication.

Required in Every Agent Prompt

1. Verification Command (MANDATORY)

## Before Marking Complete
Run verification:
\`\`\`bash
npx tsc --noEmit 2>&1 | head -20
\`\`\`
If ANY type errors exist, fix them before completing.

2. Grep-Before-Create

## Before Creating Any Type/Interface
First check if it exists:
\`\`\`bash
grep -r "interface YourTypeName\|type YourTypeName" src/
\`\`\`
If found, import it. NEVER duplicate existing types.

3. Canonical Type Map

Include relevant entries from this map in agent prompts:

Type Owner File Import From
NormalizedTool src/sdk/agent.ts './agent'
ToolCall src/sdk/agent.ts './agent'
ToolResult src/sdk/agent.ts './agent'
ToolDefinition src/sdk/agent.ts './agent'
Message src/sdk/types.ts './types'
ContentBlock src/sdk/types.ts './types'
TokenUsage src/sdk/types.ts './types'
ProviderAdapter src/sdk/providers/index.ts './providers'
RiggClient src/sdk/client.ts './client'

Prompt Template

When spawning implementation agents:

# Task: [Description]

## Type Ownership (DO NOT recreate)
- [List relevant types from canonical map]

## Before Creating New Types
Run: `grep -r "interface TypeName" src/` - if exists, import it.

## Before Marking Complete
Run: `npx tsc --noEmit 2>&1 | head -20`
Fix all type errors before completing.

## Your Implementation
[Actual task description]

Why This Works

  1. Type checker is the contract - tsc catches conflicts automatically
  2. Grep is fast - 1 second to check if type exists
  3. Explicit ownership - No ambiguity about where types live
  4. Fail fast - Agent can't claim "done" with broken types

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

✓

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

✓

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • ›Claude Desktop or compatible AI client
  • ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • ›Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Steps

  1. 1Install product management skill
  2. 2Start with user story generation for known feature
  3. 3Progress to competitive analysis: research 2-3 competitors
  4. 4Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5Draft stakeholder communications and refine based on feedback
  6. 6Build template library for recurring PM tasks
  7. 7Share effective prompts with product team

Common Pitfalls

  • ⚠Not validating competitive research—verify facts before sharing
  • ⚠Accepting user stories without involving engineering team
  • ⚠Over-relying on frameworks without qualitative judgment
  • ⚠Not customizing outputs to company culture and communication style
  • ⚠Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • −Don't publish competitive analysis without fact-checking
  • −Don't finalize user stories without engineering review
  • −Don't make prioritization decisions solely on AI scoring
  • −Don't skip customer validation of generated requirements
  • −Don't ignore company-specific context and culture

💡 Pro Tips

  • ★Provide context: company goals, constraints, customer feedback
  • ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • ★Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use when

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid when

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Related Skills

premortem

197

parcadei/continuous-claude-v3

Productivitysame repo

grill-me

386

mattpocock/skills

Productivitysame category

deslop

118

cursor/plugins

Productivitysame category

framer-motion

98

pproenca/dot-skills

Productivitysame category

write-a-prd

91

mattpocock/skills

Productivitysame category

travel-planner

90

ailabs-393/ai-labs-claude-skills

Productivitysame category

Reviews

4.6★★★★★29 reviews
  • M
    Mia Bansal★★★★★Dec 16, 2024

    I recommend parallel-agent-contracts for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • D
    Dhruvi Jain★★★★★Dec 4, 2024

    parallel-agent-contracts fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • O
    Oshnikdeep★★★★★Nov 23, 2024

    Registry listing for parallel-agent-contracts matched our evaluation — installs cleanly and behaves as described in the markdown.

  • I
    Isabella Mensah★★★★★Nov 7, 2024

    Keeps context tight: parallel-agent-contracts is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • I
    Isabella Garcia★★★★★Oct 26, 2024

    parallel-agent-contracts is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • G
    Ganesh Mohane★★★★★Oct 14, 2024

    parallel-agent-contracts reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • I
    Isabella Johnson★★★★★Sep 17, 2024

    Solid pick for teams standardizing on skills: parallel-agent-contracts is focused, and the summary matches what you get after install.

  • O
    Olivia Jain★★★★★Sep 17, 2024

    We added parallel-agent-contracts from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • S
    Sakshi Patil★★★★★Sep 5, 2024

    I recommend parallel-agent-contracts for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • N
    Nikhil Smith★★★★★Sep 5, 2024

    parallel-agent-contracts fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 29

1 / 3

Discussion

Comments — not star reviews
  • No comments yet — start the thread.