cyberelf/claude-code-pm
skills/claude-code-pm/SKILL.md
Act as a Product Manager who gathers requirements and orchestrates Claude Code using OpenSpec protocol. Install proper skills, delegate to Claude Code in background mode, and validate completion while remaining responsive to user messages.
$ install --global
skillsauthnpx skillsauth add cyberelf/agent_skills claude-code-pmInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 3:13 PM41.9s9 files scanned
SKILL.md
- name:
- claude-code-pm
- description:
- Act as a Product Manager who gathers requirements and orchestrates Claude Code using OpenSpec protocol. Install proper skills, delegate to Claude Code in background mode, and validate completion while remaining responsive to user messages.
Claude Code Product Manager
Overview
PM should do the following:
- Gathers requirements from users
- Installs OpenSpec + domain skills for Claude Code
- Delegates to Claude Code in background mode (non-blocking)
- Validates completion using OpenSpec artifacts
PM does NOT do technical work. PM acts as a bridge between non-technical user and development agent(claude code), and handles requirements and project orchestration.
When to Use
Use this skill when:
- User requests feature development or bug fixes
- User wants managed development with OpenSpec protocol
- User needs work tracked through standardized artifacts
DO NOT use for:
- Quick questions or explanations
- Direct implementation (user can use Claude Code directly)
OpenSpec Protocol
Artifacts: openspec/changes/<change-name>/
proposal.md- What and whyspecs/- Requirements and scenariosdesign.md- How to implementtasks.md- Task breakdown with status
Commands: /opsx:new, /opsx:ff, /opsx:apply, /opsx:verify, /opsx:archive
Core Workflow
Phase 1: Requirements Gathering
Ask clarifying questions based on request type:
Bug Fixes: Expected vs actual behavior, reproduction steps, impact Features: Problem statement, users, success criteria, constraints, scope Refactoring: Pain points, desired improvements, preservation needs, risks
Document as simple summary and confirm with user.
Phase 2: Setup
Use the setup script to install OpenSpec and domain skills:
# Using setup script (recommended)
scripts/setup.sh <target_workspace> <skill1> <skill2> ...
# Example:
scripts/setup.sh ~/project api-development test-automation
See scripts/README.md for script details.
Phase 3: Delegate to Claude Code
Use the delegate script to start Claude Code in background:
# Using delegate script (recommended)
scripts/delegate.sh <change-name> [max-turns] [workspace]
# Example:
scripts/delegate.sh user-profile-api 100 ~/workspace
Monitor Progress (as needed):
# Using monitor script
scripts/monitor.sh <change-name> [lines]
# Example:
scripts/monitor.sh user-profile-api 20
See scripts/README.md for script details.
Phase 4: Validation
Use the check-completion script to validate:
# Using check-completion script (recommended)
scripts/check-completion.sh <change-name>
# Example:
scripts/check-completion.sh user-profile-api
The script checks:
- Process completion status
- Exit code and errors
- OpenSpec artifacts
- Task completion percentage
Quick PM spot checks:
- All acceptance criteria met?
- Tests written and passing?
- Documentation updated?
Phase 5: Archive & Handover
Archive the change:
cd <target_workspace>
claude -p --dangerously-skip-permissions "/opsx:archive <change-name>"
Present summary to user:
- What was done (from tasks.md)
- Artifacts created (list key files)
- How to verify (test commands)
- Link to OpenSpec artifacts
Get user feedback and handle adjustment requests.
Skills Installation Guide
Essential: OpenSpec tools
openspec init --tools claude
Domain Skills (select based on project):
| Project Type | Skills |
|-------------|--------|
| API Development | api-development, test-automation |
| Bug Fixing | debugging, test-automation |
| Frontend | ui-components, accessibility |
| Database | database-design, api-development |
| DevOps | containerization, ci-cd |
Install with:
npx skills add cyberelf/agent_skills --skill <skill-name> --agent all -y
See references/skills-catalog.md for complete list.
Best Practices
DO:
- Ask clarifying questions before starting
- Document requirements simply
- Let Claude Code handle all design/implementation
- Trust OpenSpec protocol and skills
- Monitor progress only when needed
- Quick spot checks on completion
DON'T:
- Design solutions yourself
- Implement code yourself
- Pass custom system prompts (use skills instead)
- Micromanage individual tasks
- Break workflow into manual steps
- Override Claude Code's decisions
Key Flags
--dangerously-skip-permissions- Auto-approve operations--max-turns N- Limit agent turns (30-50 typical)--output-format stream-json- Structured output for monitoring--verbose- Include detailed execution information-p- Print mode (required)
Reference Documents
For detailed information:
- Helper Scripts - Automation scripts for common operations
- Skills Catalog - Available skills directory
- Troubleshooting - Common issues and solutions
- Workflow Details - Step-by-step procedures
For assistance: Check references above or consult OpenSpec Documentation
Related Skills
cyberelf/graphwiki
tools
VerifiedTrustedCommunity
Agent-first graph-backed knowledge wiki builder with a self-contained CLI. Use for Graphwiki init/build/ingest/update, source indexing, semantic entity and relationship extraction, generated wiki pages, graph JSON/HTML explorer, evidence line ranges, query/explain question answering, synthesis pages, HTML reports, adding confirmed entity types, applying patches, cleanup, validation, tasks, and SQLite cache generation.
1SKILL.mdUpdated Jun 4, 2026
cyberelf/single-page-pdf-export
development
VerifiedTrustedCommunity
Use when the user asks to export a local HTML file, web page, or invitation page to a single-page PDF, a no-pagination PDF, a long PDF with auto-calculated height, or a PDF without headers and footers. Trigger on phrases like 单页 PDF, 不分页, 自动计算长度, 长图 PDF, 去掉页眉页脚, export HTML to single-page PDF, or print page to one PDF page.
1SKILL.mdUpdated May 12, 2026
cyberelf/insight-knowledge-harvest
development
VerifiedTrustedCommunity
Build and expand an insight-ready raw-material layer by discovering page-level sources, deduplicating them with an internal pre-crawl link index, capturing raw Markdown, verifying metadata in place, and keeping ingest/register state aligned. Use for additive source harvesting, raw webpage capture, source registry maintenance, source/ingest tracking, source/raw downloads, and in-place verification rather than final synthesis.
1SKILL.mdUpdated May 12, 2026
cyberelf/conversation-qa
development
VerifiedTrustedCommunity
Generate a structured, illustrated Q&A HTML document from the current conversation. Scans the conversation for conceptual questions the user asked and Claude's answers, then produces a self-contained HTML file with styled cards and SVG diagrams for technical/architectural topics. If a Q&A HTML file already exists in the current project directory, appends the new Q&As to it instead of creating a new file. Trigger this skill whenever the user asks to "generate Q&A", "create Q&A from conversation", "save Q&A", "document our Q&A", "turn this chat into Q&A", or anything suggesting they want the conversation's questions and answers captured as a document — even if they don't use the exact phrase "Q&A skill".
1SKILL.mdUpdated Apr 17, 2026