When launching parallel agents for code implementation, prevent type duplication.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionparallel-agent-contractsExecute the skills CLI command in your project's root directory to begin installation:
Fetches parallel-agent-contracts from parcadei/continuous-claude-v3 and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate parallel-agent-contracts. Access via /parallel-agent-contracts in your agent's command palette.
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.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
3.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3.7K
stars
When launching parallel agents for code implementation, prevent type duplication.
## Before Marking Complete
Run verification:
\`\`\`bash
npx tsc --noEmit 2>&1 | head -20
\`\`\`
If ANY type errors exist, fix them before completing.
## 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.
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' |
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]
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
parcadei/continuous-claude-v3
mattpocock/skills
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend parallel-agent-contracts for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
parallel-agent-contracts fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for parallel-agent-contracts matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: parallel-agent-contracts is the kind of skill you can hand to a new teammate without a long onboarding doc.
parallel-agent-contracts is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
parallel-agent-contracts reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: parallel-agent-contracts is focused, and the summary matches what you get after install.
We added parallel-agent-contracts from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend parallel-agent-contracts for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
parallel-agent-contracts fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 29