Fetches explore 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/explore
Restart Cursor to activate explore. Access via /explore 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.
Meta-skill for exploring an internal codebase at varying depths. READ-ONLY workflow - no code changes.
Usage
/explore <depth> [options]
Question Flow (No Arguments)
If the user types just /explore with no or partial arguments, guide them through this question flow. Use AskUserQuestion for each phase.
Phase 0: Workflow Selection
question:"How would you like to explore?"header:"Explore"options:-label:"Help me choose (Recommended)"description:"I'll ask questions to pick the right exploration depth"-label:"Quick - fast overview"description:"Chain: tldr tree → tldr structure (~1 min)"-label:"Deep - comprehensive analysis"description:"Chain: onboard → tldr → research → document (~5 min)"-label:"Architecture - layers & dependencies"description:"Chain: tldr arch → call graph → layer mapping (~3 min)"
Mapping:
"Help me choose" → Continue to Phase 1-4 questions
"Quick" → Set depth=quick, skip to Phase 2 (scope)
"Deep" → Set depth=deep, skip to Phase 2 (scope)
"Architecture" → Set depth=architecture, skip to Phase 2 (scope)
If Answer is Unclear (via "Other"):
question:"I want to understand how deep you want to explore. Did you mean..."header:"Clarify"options:-label:"Help me choose"description:"Not sure - guide me through questions"-label:"Quick - fast overview"description:"Just want to see what's here"-label:"Deep - comprehensive analysis"description:"Need thorough understanding"-label:"Neither - let me explain differently"description:"I'll describe what I need"
Phase 1: Exploration Goal
question:"What are you trying to understand?"header:"Goal"options:-label:"Get oriented in the codebase"description:"Quick overview of structure"-label:"Understand how something works"description:"Deep dive into specific area"-label:"Map the architecture"description:"Layers, dependencies, patterns"-label:"Find where something is"description:"Locate specific code/functionality"
Mapping:
"Get oriented" → quick depth
"Understand how" → deep depth
"Map architecture" → architecture depth
"Find where" → quick with --focus
Phase 2: Scope
question:"What area should I focus on?"header:"Focus"options:-label:"Entire codebase"description:"Explore everything"-label:"Specific directory or module"description:"I'll specify the path"-label:"Specific concept/feature"description:"e.g., 'authentication', 'API routes'"
If "Specific directory" or "Specific concept" → ask follow-up for the path/keyword.
Phase 3: Output Format
question:"What should I produce?"header:"Output"options:-label:"Just tell me what you find"description:"Interactive summary in chat"-label:"Create a documentation file"description:"Write to thoughts/shared/docs/"-label:"Create handoff for implementation"description:"Prepare context for coding agent"
Mapping:
"Documentation file" → --output doc
"Handoff for implementation" → --output handoff
Phase 4: Entry Point (Architecture only)
If architecture depth selected:
question:"Where should I start the analysis?"header:"Entry point"options:-label:"Auto-detect (main, cli, app)"description:"Find common entry points"-label:"Specific function/file"description:"I'll specify the entry point"
Summary Before Execution
Based on your answers, I'll run:
**Depth:** deep
**Focus:** "authentication"
**Output:** handoff
**Path:** src/
Proceed? [Yes / Adjust settings]
›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
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
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
1Basic: user stories, feature specs, status updates
