project-product-skills
A cross-agent kit with 42 operating skills plus one router skill for running projects and products: decisions, requirements, discovery, deli
Open source Open in the app JSON README (API)
About
A cross-agent kit with 42 operating skills plus one router skill for running projects and products: decisions, requirements, discovery, delivery, launch, PRINCE2 documentation, workshops, and team rituals.
Details
- Kind
- Plugins
- Topic
- No topic detected
- Publisher
- danielpradilla
- Origin
- gemini
- Category
- ferramentas
- Version
- 1.0.0
- Last push
- 2026-05-18T21:10:39Z
- Repository state
- ativo
- Language
- PowerShell
- License
- MIT
- Added
- 2026-08-30 14:13:39
- Updated
- 2026-08-30 14:13:39
- Origin id
danielpradilla/project-product-skills
README
# Project + Product Skills This is a practical skill kit for the weekly work of running projects and products across Codex, Claude Code, and Gemini CLI. It is built around the typical documents and decisions you'll need to make to keep the ball rolling: meeting notes, status briefs, product requirements, interviews, roadmap narratives, prioritization, delivery planning, workshops, offsites, onboarding plans, and PRINCE2 project packs. Give an AI agent enough structure to produce useful operating artifacts without turning every request into a runaway task. Most of these skills are meant to create something you can paste into a working doc, review with a team, or use in a project meeting. This repo is inspired by Mohit Aggarwal's open-source Claude skills library. I took a handful of ideas, reshaped the collection around what I consider a typical workflow, and packaged this version for Codex, Claude Code, and Gemini CLI. ## Install ### macOS or Linux Codex: ```bash cd /Users/dpradilla/dev/project-product-skills ./scripts/install-codex.sh ``` Claude Code: ```bash cd /Users/dpradilla/dev/project-product-skills ./scripts/install-claude.sh ``` Gemini CLI: ```bash cd /Users/dpradilla/dev/project-product-skills ./scripts/install-gemini.sh ``` ### Windows PowerShell Codex: ```powershell .\scripts\install-codex.ps1 ``` Claude Code: ```powershell .\scripts\install-claude.ps1 ``` Gemini CLI: ```powershell .\scripts\install-gemini.ps1 ``` The macOS/Linux installers symlink skills into the agent skill folder. The Windows installers copy skills by default because symlinks can require Developer Mode or elevated permissions. Installers also support explicit modes: ```bash ./scripts/install-codex.sh --link ./scripts/install-codex.sh --copy ./scripts/install-claude.sh --link ./scripts/install-claude.sh --copy ``` On Windows, add `-UseSymlinks` if Developer Mode or elevated permissions allow symlinks: ```powershell .\scripts\install-codex.ps1 -UseSymlinks .\scripts\install-claude.ps1 -UseSymlinks ``` ## Maintenance Check the repo: ```bash ./scripts/validate.sh ./scripts/doctor.sh ``` Update after pulling new changes: ```bash ./scripts/update.sh ./scripts/update.sh codex --link ./scripts/update.sh claude --copy ``` Uninstall local skill copies or links: ```bash ./scripts/uninstall-codex.sh ./scripts/uninstall-claude.sh ./scripts/uninstall-gemini.sh ``` Windows equivalents exist for each script as `.ps1` files. ## Requirements - Git, if you are cloning the repo. - Codex, Claude Code, or Gemini CLI depending on which agent you use. - Bash on macOS/Linux. - PowerShell on Windows. - Node.js if you want to run the Bash validation script. - Gemini CLI on your `PATH` if you use the Gemini installer. ## Test It After installing, restart the agent and try: ```text Use product-requirements-blueprint to draft requirements for a customer onboarding dashboard. ``` Or: ```text Use prince2-documentation-map to list the management products needed for a medium-risk software project. ``` ## Skill Set For a browseable table with descriptions, see [SKILLS.md](SKILLS.md). ### Choose The Workflow - `project-product-router` ### Run The Work - `decision-meeting-notes` - `delivery-status-brief` - `stakeholder-decision-note` - `executive-product-note` - `workshop-runbook` - `team-offsite-agenda` ### Define The Product - `product-requirements-blueprint` - `technical-alignment-brief` - `outcome-map` - `roadmap-story-brief` - `roadmap-review-outline` - `strategic-story-builder` ### Learn From Customers - `discovery-conversation-guide` - `interview-signal-synthesis` - `research-evidence-brief` - `assumption-risk-ledger` - `job-to-be-done-map` ### Make Better Decisions - `metric-architecture` - `product-health-diagnostic` - `retention-diagnostic` - `dashboard-decision-brief` - `market-landscape-scan` - `priority-decision-system` - `learning-experiment-plan` - `pricing-packaging-brief` ### Deliver And Launch - `delivery-commitment-map` - `sprint-kickoff-brief` - `retrospective-insight-brief` - `handoff-readiness-brief` - `launch-readiness-review` - `launch-control-checklist` - `market-activation-plan` ### Run PRINCE2 Projects - `prince2-startup-brief` - `prince2-initiation-pack` - `prince2-direction-gate-brief` - `prince2-stage-control-pack` - `prince2-product-delivery-pack` - `prince2-stage-boundary-pack` - `prince2-closure-pack` - `prince2-documentation-map` ### Build The Team - `role-interview-kit` - `team-onboarding-plan` ## How I Use It When a product review is messy, I use `roadmap-story-brief`. When a project is drifting, I use `delivery-status-brief`. When the team has too many opinions and not enough evidence, I use `assumption-risk-ledger`. When a launch feels vague, I use `launch-readiness-review`. When a governed project needs structure, I use `prince2-documentation-map` first and then the phase-specific PRINCE2 skill.