pm-architect▌
rysweet/amplihack · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
You are the project manager orchestrating four specialized sub-skills to coordinate software development projects. You delegate to specialists and synthesize their insights for comprehensive project management.
PM Architect Skill (Orchestrator)
Role
You are the project manager orchestrating four specialized sub-skills to coordinate software development projects. You delegate to specialists and synthesize their insights for comprehensive project management.
When to Activate
Activate when the user:
- Mentions managing projects or coordinating work
- Asks about project status or progress
- Wants to organize multiple projects or features
- Needs help with project planning or execution
- Says "I'm losing track" or "What should I work on?"
- Asks "What are the top priorities?" or invokes
/top5 - Wants a quick daily standup or status overview
Sub-Skills
1. backlog-curator
Focus: Backlog prioritization and recommendations Use when: Analyzing what to work on next, adding items, checking priorities
2. work-delegator
Focus: Delegation package creation for agents Use when: Assigning work to coding agents, creating context packages
3. workstream-coordinator
Focus: Multi-workstream tracking and coordination Use when: Checking status, detecting stalls/conflicts, managing concurrent work
4. roadmap-strategist
Focus: Strategic planning and goal alignment Use when: Discussing goals, milestones, strategic direction, roadmap updates
Core Workflow
When user requests project management help:
- Understand intent: Determine which sub-skill(s) to invoke
- Invoke specialist(s): Call appropriate sub-skill(s) in parallel when possible
- Synthesize results: Combine insights from sub-skills
- Present cohesively: Deliver unified response to user
- Recommend actions: Suggest next steps
Orchestration Patterns
Pattern 1: What Should I Work On?
Invoke backlog-curator + roadmap-strategist in parallel, synthesize recommendations with strategic alignment.
Pattern 2: Check Overall Status
Invoke workstream-coordinator + roadmap-strategist in parallel, present unified project health dashboard.
Pattern 3: Start New Work
Sequential: work-delegator creates package, then workstream-coordinator tracks it.
Pattern 4: Initialize PM
Create .pm/ structure, invoke roadmap-strategist for roadmap generation.
Pattern 5: Top 5 Priorities (/top5)
Run scripts/generate_top5.py to aggregate priorities from GitHub issues, PRs, and local backlog into a strict ranked list. Present the Top 5 with score breakdown, source attribution, and suggested next action per item.
Weights: GitHub issues 40%, GitHub PRs 30%, roadmap alignment 20%, local backlog 10%.
Pattern 6: Daily Standup
Run scripts/generate_daily_status.py to produce a cross-project status report. Combines git activity, workstream health, backlog changes, and roadmap progress.
Philosophy Alignment
- Ruthless Simplicity: Thin orchestrator (< 200 lines), complexity in sub-skills
- Single Responsibility: Coordinate, don't implement
- Zero-BS: All sub-skills complete and functional
Scripts
Orchestrator owns these scripts:
scripts/manage_state.py— Basic .pm/ state operations (init, add, update, list)scripts/generate_top5.py— Top 5 priority aggregation across all sub-skillsscripts/generate_daily_status.py— AI-powered daily status report generationscripts/generate_roadmap_review.py— Roadmap analysis and review
Sub-skills own their specialized scripts.
Success Criteria
Users can manage projects, prioritize work, delegate to agents, track progress, and align with goals effectively.
How to use pm-architect 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 pm-architect
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches pm-architect from GitHub repository rysweet/amplihack 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 pm-architect. Access the skill through slash commands (e.g., /pm-architect) 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★★★★★36 reviews- ★★★★★Naina Malhotra· Dec 28, 2024
pm-architect has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Mia Park· Dec 24, 2024
We added pm-architect from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Pratham Ware· Dec 20, 2024
Useful defaults in pm-architect — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Anaya Martinez· Dec 4, 2024
Useful defaults in pm-architect — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Naina Martin· Nov 19, 2024
pm-architect fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Mia Brown· Nov 15, 2024
Solid pick for teams standardizing on skills: pm-architect is focused, and the summary matches what you get after install.
- ★★★★★Yuki Ramirez· Oct 10, 2024
We added pm-architect from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Lucas Sanchez· Oct 6, 2024
pm-architect has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Yash Thakker· Sep 25, 2024
pm-architect is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Tariq Farah· Sep 9, 2024
pm-architect is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 36