Claude Code plugin marketplace for PRD workflow and utilities
npx claudepluginhub itzsaga/cc-prdFull PRD workflow system with research, planning, and implementation capabilities
A portable plugin marketplace for Claude Code, featuring a comprehensive PRD (Product Requirements Document) workflow system.
This marketplace provides plugins that extend Claude Code with structured workflows, commands, and automation. The flagship plugin is prd-workflow, which offers a complete system for creating, planning, and implementing product requirements.
Ensure you have the required dependencies installed. See DEPENDENCIES.md for detailed installation instructions.
Required:
jq - JSON parsingyq - YAML parsingcheck-jsonschema - Schema validationOptional:
glow - Markdown renderingmacOS (Homebrew):
brew install jq yq
pip install check-jsonschema
Ubuntu/Debian:
apt install jq
snap install yq # or: pip install yq
pip install check-jsonschema
Arch Linux:
pacman -S jq yq
pip install check-jsonschema
Once Claude Code supports plugin marketplaces, you can install via:
/plugin marketplace add /path/to/jackbot-ai
/plugin install prd-workflow
Until then, you can manually symlink or copy the plugin contents to your Claude configuration.
A complete PRD workflow system with three main phases:
# Create a new PRD
/prd create my-feature
# Plan an existing PRD (research and task definition)
/prd plan my-feature
# Work on a planned PRD (implementation)
/prd work my-feature
# Check PRD status (scripts are relative to the skill directory)
scripts/list-prds.sh
scripts/task-status.sh my-feature
cc-prd/
├── .claude-plugin/
│ └── marketplace.json # Marketplace catalog
├── plugins/
│ └── prd-workflow/ # PRD workflow plugin
│ ├── .claude-plugin/
│ │ └── plugin.json # Plugin configuration
│ ├── agents/ # Subagent definitions
│ ├── commands/ # Custom commands
│ ├── hooks/ # Validation hooks
│ ├── skills/ # Skill definitions
│ ├── specs/ # JSON schemas
│ └── scripts/ # Utility scripts
├── README.md
└── DEPENDENCIES.md
The prd-researcher agent uses Exa MCP tools for web research. To enable:
EXA_API_KEY environment variableWithout Exa, the research features will gracefully degrade with appropriate error messages.
Hooks automatically validate tasks.yaml and research.yaml files when edited. They require jq, yq, and check-jsonschema to be installed.
If dependencies are missing, hooks will log a warning but won't block operations.
PRDs are stored in .claude/prds/<prd-name>/:
.claude/prds/my-feature/
├── PRD.md # Main requirements document
├── tasks.yaml # Task definitions
├── research.yaml # Research questions (optional)
├── log.md # Implementation log
└── specs/ # Task specification files
└── task-name.md
Scripts are located in plugins/prd-workflow/skills/prd/scripts/ and are invoked relative to the skill directory.
| Script | Description |
|---|---|
scripts/list-prds.sh | List all PRDs with status |
scripts/task-status.sh <prd> | Get task counts by status |
scripts/get-task.sh <prd> <task> | Get full task details |
scripts/list-prd-draft-tasks.sh <prd> | List tasks needing specs |
scripts/list-defined-tasks.sh <prd> | List tasks ready to implement |
scripts/update-task-status.sh <prd> <task> <status> | Update task status |
scripts/research-status.sh <prd> | Get research completion status |
scripts/get-unanswered-research.sh <prd> | Get pending research questions |
Adapted from fullykubed/nixos-config - converted from NixOS-specific configuration to a portable plugin format.
MIT
Development marketplace for Superpowers core skills library
Harness-native ECC skills, hooks, rules, MCP conventions, and operator workflows
Open Design — local-first design app exposed to coding agents over MCP. Install once with your agent's plugin command and projects/files/skills are reachable through stdio.