sub-agents

parcadei/continuous-claude-v3 · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill sub-agents
0 commentsdiscussion
summary

Create specialized AI agents with isolated contexts for specific tasks.

skill.md

Sub-Agents Reference

Create specialized AI agents with isolated contexts for specific tasks.

When to Use

  • "How do I create a sub-agent?"
  • "Configure agent tools"
  • "What built-in agents exist?"
  • "Agent model selection"
  • "Agent chaining patterns"

Quick Start

Interactive (Recommended)

/agents

Opens menu to create, edit, and manage agents.

Manual Creation

mkdir -p .claude/agents
cat > .claude/agents/reviewer.md << 'EOF'
---
name: reviewer
description: Code review specialist. Use proactively after code changes.
tools: Read, Grep, Glob, Bash
model: sonnet
---

You are a senior code reviewer focusing on quality and security.

## Review Checklist
- Code clarity and naming
- Error handling
- Security vulnerabilities
- Test coverage
EOF

CLI-Based

claude --agents '{
  "reviewer": {
    "description": "Code reviewer",
    "prompt": "Review for quality and security",
    "tools": ["Read", "Bash"],
    "model": "sonnet"
  }
}'

Agent File Format

---
name: agent-name
description: When/why to use this agent
tools: Read, Edit, Bash      # Optional, inherits all if omitted
model: sonnet                 # sonnet, haiku, claude-opus-4-5-20251101, inherit
---

System prompt content here...

Configuration Fields

Field Required Options
name Yes lowercase, hyphens
description Yes When to use
tools No Tool list (inherits all if omitted)
model No sonnet, haiku, claude-opus-4-5-20251101, inherit

Built-In Agents

Agent Model Tools Purpose
General-purpose Sonnet All Complex multi-step tasks
Plan Sonnet Read-only Plan mode research
Explore Haiku Read-only Fast codebase search

Model Selection

Model Speed Best For
Haiku Fastest Search, quick lookups
Sonnet Fast Most tasks (default)
Opus Slower Complex reasoning

Tool Combinations

# Code Reviewer (read-only)
tools: Read, Grep, Glob, Bash

# Debugger
tools: Read, Edit, Bash, Grep, Glob

# Implementer
tools: Read, Write, Edit, Bash, Glob

Example Agents

Code Reviewer

---
name: code-reviewer
description: Reviews code for quality and security. Use after code changes.
tools: Read, Grep, Glob, Bash
model: sonnet
---

Review code for:
- Security vulnerabilities
- Code quality issues
- Missing error handling
- Test coverage gaps

Output findings by priority: Critical > Warning > Suggestion

Debugger

---
name: debugger
description: Debug errors and test failures.
tools: Read, Edit, Bash, Grep, Glob
model: inherit
---

Debugging process:
1. Capture error details
2. Identify failure location
3. Form hypotheses
4. Test and verify
5. Implement fix

File Locations

Type Location Priority
Project .claude/agents/ Highest
User ~/.claude/agents/ Lower

Advanced Patterns

Resumable Agents

[Agent returns agentId: "abc123"]

# Later: resume with context
claude -r "abc123" "Continue analysis"

Agent Chaining

Use code-analyzer to find issues,
then use optimizer to fix them

Best Practices

  1. Single responsibility - One clear purpose per agent
  2. Restrict tools - Only grant what's needed
  3. Clear descriptions - Action-oriented, include "proactively"
  4. Version control - Check .claude/agents/ into git
how to use sub-agents

How to use sub-agents 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 development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add sub-agents
2

Execute installation 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 sub-agents

The skills CLI fetches sub-agents from GitHub repository parcadei/continuous-claude-v3 and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/sub-agents

Reload or restart Cursor to activate sub-agents. Access the skill through slash commands (e.g., /sub-agents) or your agent's skill management interface.

Security & Verification 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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

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

Installation Steps

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

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.743 reviews
  • Mia Reddy· Dec 24, 2024

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

  • Pratham Ware· Dec 12, 2024

    Registry listing for sub-agents matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Dhruvi Jain· Dec 8, 2024

    We added sub-agents from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Luis Sethi· Dec 8, 2024

    Useful defaults in sub-agents — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Oshnikdeep· Nov 27, 2024

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

  • Luis Garcia· Nov 27, 2024

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

  • Luis Thompson· Nov 23, 2024

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

  • Ama Gonzalez· Nov 15, 2024

    sub-agents is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Ganesh Mohane· Oct 18, 2024

    sub-agents is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Omar Sharma· Oct 18, 2024

    sub-agents reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 43

1 / 5