agentic-workflow▌
parcadei/continuous-claude-v3 · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Standard multi-agent pipeline for implementation tasks.
Agentic Workflow Pattern
Standard multi-agent pipeline for implementation tasks.
Architecture Principles
- Use
run_in_background: truefor all agents to keep main context minimal - Use
Tasktool (neverTaskOutput) to avoid receiving full agent transcripts - Agents write outputs to
.claude/cache/agents/<stage>/for injection into subsequent agents - Main conversation is pure orchestration — no heavy lifting, only coordination
Workflow Stages
1. Research Agent
Task(subagent_type="oracle", run_in_background=true, prompt="""
Query NIA Oracle (via /nia-docs skill) to verify approach and gather best practices.
Output to: .claude/cache/agents/oracle/<task>-research.md
""")
- Enforce NIA as the research layer
- Output: Research findings
2. Planning Agent
Task(subagent_type="plan-agent", run_in_background=true, prompt="""
Read: .claude/cache/agents/oracle/<task>-research.md
Use RP-CLI to analyze the target codebase section.
Generate implementation plan informed by research.
Output to: .claude/cache/agents/plan-agent/<task>-plan.md
""")
- Receives: Research agent output as context
- Output: Implementation plan
3. Validation Agent
Task(subagent_type="validate-agent", run_in_background=true, prompt="""
Read: .claude/cache/agents/plan-agent/<task>-plan.md
Read: .claude/cache/agents/oracle/<task>-research.md
Review plan against research findings and best practices.
Output to: .claude/cache/agents/validate-agent/<task>-validated.md
""")
- Reviews plan against research
- Output: Validated plan with amendments
4. Implementation Agent
Task(subagent_type="agentica-agent", run_in_background=true, prompt="""
Read: .claude/cache/agents/validate-agent/<task>-validated.md
Read: .claude/cache/agents/oracle/<task>-research.md
TDD approach: Write failing tests FIRST, then implement.
Run tests to verify.
Output summary to: .claude/cache/agents/implement-agent/<task>-implementation.md
""")
- Receives: Validated plan + research context
- TDD: Failing tests first
- Output: Implementation + tests
5. Review Agent
Task(subagent_type="review-agent", run_in_background=true, prompt="""
Read: .claude/cache/agents/implement-agent/<task>-implementation.md
Read: .claude/cache/agents/validate-agent/<task>-validated.md
Read: .claude/cache/agents/oracle/<task>-research.md
Cross-reference implementation against plan and research.
Run tests to confirm passing.
Output to: .claude/cache/agents/review-agent/<task>-review.md
""")
- Cross-references all artifacts
- Confirms tests pass
- Output: Review summary
Agent Progress Monitoring
# Watch for system reminders:
# "Agent a42a16e progress: 6 new tools used, 88914 new tokens"
# Poll for output files:
find .claude/cache/agents -name "*.md" -mmin -5
# Check task file size growth:
wc -c /tmp/claude/.../tasks/<id>.output
Stuck detection:
- Progress reminders stop arriving
- Task output file size stops growing
- Expected output file not created after reasonable time
Directory Structure
.claude/cache/agents/
├── oracle/
│ └── <task>-research.md
├── plan-agent/
│ └── <task>-plan.md
├── validate-agent/
│ └── <task>-validated.md
├── implement-agent/
│ └── <task>-implementation.md
└── review-agent/
└── <task>-review.md
Key Rules
- Never use TaskOutput - floods context with 70k+ token transcripts
- Always run_in_background=true - isolates agent context
- File-based handoff - each agent reads previous agent's output file
- Poll, don't block - check file system for outputs, don't wait
- TDD in implementation - failing tests first, then make them pass
Source
- Session 2026-01-01: SDK Phase 3 implementation using this pattern
How to use agentic-workflow on Cursor
AI-first code editor with Composer
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 agentic-workflow
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches agentic-workflow from GitHub repository parcadei/continuous-claude-v3 and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate agentic-workflow. Access the skill through slash commands (e.g., /agentic-workflow) 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
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.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 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▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★72 reviews- ★★★★★Emma Kapoor· Dec 24, 2024
We added agentic-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Dhruvi Jain· Dec 20, 2024
Solid pick for teams standardizing on skills: agentic-workflow is focused, and the summary matches what you get after install.
- ★★★★★Amina Khanna· Dec 16, 2024
agentic-workflow fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Li Harris· Dec 12, 2024
agentic-workflow has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Oshnikdeep· Nov 11, 2024
We added agentic-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Evelyn Singh· Nov 7, 2024
agentic-workflow has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Isabella White· Nov 3, 2024
agentic-workflow fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Michael Gonzalez· Oct 26, 2024
Solid pick for teams standardizing on skills: agentic-workflow is focused, and the summary matches what you get after install.
- ★★★★★Isabella Srinivasan· Oct 22, 2024
We added agentic-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ganesh Mohane· Oct 2, 2024
agentic-workflow fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 72