CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Write a PRD for a physical hardware product — target cost (BOM and landed), industrial design constraints, regulatory certifications, reliability targets, serviceability, packaging, and forecast…
Install Hardware Prd
$ npx skills add mohitagw15856/pm-claude-skills --skill hardware-prd -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills hardware-prd --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/hardware-prd .claude/skills/hardware-prd && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hardware-prd" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hardware-prd into .claude/skills/hardware-prd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardware-prd", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hardware-prdType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill hardware-prd -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills hardware-prd --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/hardware-prd .agents/skills/hardware-prd && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hardware-prd" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hardware-prd into .agents/skills/hardware-prd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardware-prd", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill hardware-prd -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills hardware-prd --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/hardware-prd .cursor/skills/hardware-prd && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hardware-prd" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hardware-prd into .cursor/skills/hardware-prd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardware-prd", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/hardware-prd--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill hardware-prd -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills hardware-prd --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/hardware-prd .gemini/skills/hardware-prd && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hardware-prd" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hardware-prd into .gemini/skills/hardware-prd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardware-prd", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills hardware-prdInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill hardware-prd -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/hardware-prd .github/skills/hardware-prd && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hardware-prd" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hardware-prd into .github/skills/hardware-prd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardware-prd", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill hardware-prd -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills hardware-prd --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/hardware-prd .opencode/skills/hardware-prd && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hardware-prd" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/hardware-prd into .opencode/skills/hardware-prd/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardware-prd", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
hardware-prd- GitHub stars
- 1.4k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 624 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write a PRD for a physical hardware product — target cost (BOM and landed), industrial design constraints, regulatory certifications, reliability targets, serviceability, packaging, and forecast…
- Works in 10 steps: Overview & user — problem, user, use… → Requirements — numbered shall-statements… → Target cost stack — the four-layer table… → …
- Asked to write a hardware PRD
- SKILL.md covers What This Skill Produces, Required Inputs, Cost & Certification Framework and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Hardware Prd is an agent skill from mohitagw15856/pm-claude-skills. Write a PRD for a physical hardware product — target cost (BOM and landed), industrial design constraints, regulatory certifications, reliability targets, serviceability, packaging, and forecast assumptions. Use when asked to write a hardware PRD, spec a new device, define requirements for a physical product, or kick off an NPI program. Produces a complete hardware PRD with a cost stack, cert matrix, reliability spec, and EVT/DVT/PVT milestone targets.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering PRD writing. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to write a hardware PRD
- Spec a new device
- Define requirements for a physical product
- Kick off an NPI program
Example prompts
- “/hardware-prd”
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Overview & user — problem, user, use environment
- Requirements — numbered shall-statements grouped: functional, industrial design (size/weight/CMF limits), environmental
- Target cost stack — the four-layer table with numbers and margin math
- Regulatory & certification matrix — market × cert × owner × lead time
- Reliability & quality targets — MTBF, return-rate ceiling, abuse cases, ORT expectation
- Serviceability & repair — field-replaceable units, disassembly, spare-parts strategy
- Packaging — retail vs bulk, drop-test spec (e.g. ISTA 3A), dielines owner
- Forecast assumptions — Y1/lifetime units, MOQ implications, ramp shape
- Milestones — EVT/DVT/PVT/MP dates and what each gate must prove
- Open questions & assumptions — everything labelled [assumed — confirm]
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Hardware Prd loads about 1.3k tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 624 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 624 words, ~1,264 tokens.
Download SKILL.mdSave it as
.claude/skills/hardware-prd/SKILL.md (or your agent's skills folder).- name
- hardware-prd
- description
- Write a PRD for a physical hardware product — target cost (BOM and landed), industrial design constraints, regulatory certifications, reliability targets, serviceability, packaging, and forecast assumptions. Use when asked to write a hardware PRD, spec a new device, define requirements for a physical product, or kick off an NPI program. Produces a complete hardware PRD with a cost stack, cert matrix, reliability spec, and EVT/DVT/PVT milestone targets.
Hardware PRD Skill
A software PRD can ship wrong and patch later; a hardware PRD is cut into steel and soldered onto boards. This skill writes a PRD that forces the decisions that get expensive after tooling: cost targets with a full stack (not just BOM), certifications named per market, reliability as numbers, and forecast assumptions stated so the supply chain can be sized honestly.
What This Skill Produces
- A complete hardware PRD with numbered, testable requirements (shall-statements)
- A target cost stack: BOM → COGS → landed cost, with margin math
- A regulatory/certification matrix per target market
- Reliability, serviceability, and packaging requirements with acceptance numbers
- Forecast assumptions and the EVT/DVT/PVT milestones the schedule hangs on
Required Inputs
Ask for these if not provided; if the brief is thin, infer sensible values and label each one [assumed — confirm]:
- Product concept and user — what it is, who buys it, key use environment (indoor/outdoor, temp range, drop risk)
- Target retail price and channel — retail vs D2C changes the margin stack
- Target markets — determines the cert list (US, EU, UK, etc.)
- Power source — battery (chemistry, size) vs mains changes safety certs entirely
- Forecast — units for year 1 and lifetime, plus confidence
- Launch window and any hard date (e.g. holiday season)
Cost & Certification Framework
Cost stack — always build all four layers; never let "cost target" mean BOM alone:
| Layer | Contains |
|---|---|
| BOM | Components, PCBA, mechanicals, packaging materials |
| COGS | BOM + assembly/test labour + scrap/yield loss + factory overhead |
| Landed | COGS + freight + duty/tariff (HTS code, country of origin) + insurance |
| Margin check | Landed vs channel price after retailer margin (typ. 30–50% retail) |
Cert matrix — map each market to its certs. Typical starters: FCC Part 15B (unintentional) / 15C (Wi-Fi/BT radio), CE (RED, EMC, LVD), UKCA, safety UL/IEC 62368-1, RoHS/REACH/Prop 65, batteries UN 38.3 + IEC 62133. Flag any radio module choice that lacks modular certification — it adds months.
Reliability targets — state as numbers: MTBF (hours), warranty return rate ceiling (% in 12 months), lifetime (years/cycles), and the abuse cases (1 m drop, IP rating, operating temp range).
Output Format
Show full SKILL.md (291 more words)Show less
Hardware PRD: [product]
- Overview & user — problem, user, use environment
- Requirements — numbered shall-statements grouped: functional, industrial design (size/weight/CMF limits), environmental
- Target cost stack — the four-layer table with numbers and margin math
- Regulatory & certification matrix — market × cert × owner × lead time
- Reliability & quality targets — MTBF, return-rate ceiling, abuse cases, ORT expectation
- Serviceability & repair — field-replaceable units, disassembly, spare-parts strategy
- Packaging — retail vs bulk, drop-test spec (e.g. ISTA 3A), dielines owner
- Forecast assumptions — Y1/lifetime units, MOQ implications, ramp shape
- Milestones — EVT/DVT/PVT/MP dates and what each gate must prove
- Open questions & assumptions — everything labelled
[assumed — confirm]
Quality Checks
- Every requirement is testable — a DVT engineer could write a pass/fail test from it
- Cost target includes landed cost and survives the channel-margin math
- Every target market has its certs listed with lead times
- Reliability targets are numbers, not adjectives ("robust" is not a spec)
- Forecast assumptions are explicit enough to size tooling and MOQs against
- Battery products name chemistry and the UN 38.3 / IEC 62133 path
Anti-Patterns
- Do not state a cost target without saying which layer it is — "$40 target" that turns out to be BOM-only kills the margin at landed
- Do not write "certified for global markets" — name each market and each cert
- Do not spec reliability as "high quality" — give MTBF, return-rate ceiling, and abuse cases
- Do not omit serviceability — an unrepairable design is a warranty-cost decision, so make it consciously
- Do not hide forecast uncertainty — tooling cavitation and MOQs are bought against this number
- Do not refuse a thin brief — draft with labelled assumptions and list what must be confirmed before EVT
Example Trigger Phrases
- "Write a hardware PRD."
- "Spec a new device."
- "Define requirements for a physical product."
- "Kick off an NPI program."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/hardware-prd of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Hardware Prd next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hardware Prd this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.3k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Trellis Brainstormanjiemo/SunnyBeach | 178 | 7 repos | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Ralph Tui Create JSONsubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Trellis Brainstorm
anjiemo/SunnyBeach
Guides collaborative requirements discovery before implementation.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
Prd Generator
jamesrochabrun/skills
Generate comprehensive Product Requirements Documents (PRDs) for product managers.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Hardware Prd
What does Hardware Prd do?
Write a PRD for a physical hardware product — target cost (BOM and landed), industrial design constraints, regulatory certifications, reliability targets, serviceability, packaging, and forecast…. Hardware Prd is an agent skill from mohitagw15856/pm-claude-skills. Write a PRD for a physical hardware product — target cost (BOM and landed), industrial design constraints, regulatory certifications, reliability targets, serviceability, packaging, and forecast assumptions.
When should I use Hardware Prd?
Hardware Prd fits situations like: asked to write a hardware PRD; spec a new device; define requirements for a physical product; kick off an NPI program.
How do I install Hardware Prd in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill hardware-prd -a claude-code`. Or copy the skill folder (skills/hardware-prd in mohitagw15856/pm-claude-skills) into .claude/skills/hardware-prd in your project. Claude Code loads it when a task matches its description.
How do I install Hardware Prd in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill hardware-prd -a codex`. Or copy the skill folder (skills/hardware-prd in mohitagw15856/pm-claude-skills) into .agents/skills/hardware-prd in your project. Codex loads it when a task matches its description.
Can I use Hardware Prd in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill hardware-prd -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hardware-prd, .gemini/skills/hardware-prd, .github/skills/hardware-prd and .opencode/skills/hardware-prd in your project.
What does Hardware Prd need to run?
SKILL.md names no scripts, command-line tools or credentials: Hardware Prd is instructions for the agent only.
Does Hardware Prd access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Hardware Prd safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Hardware Prd use?
Hardware Prd is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Hardware Prd use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Hardware Prd?
Skills that share tags, products or a category with Hardware Prd: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hardware Prd?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.