Install any skill in seconds. Free to start, no credit card required.
Get Started Free →coco-research/pmstudio-init
Use when starting a new project, onboarding to an existing product, or setting up a documentation ecosystem for any initiative. Scaffolds the standard document set, folder structure, project memory, and doc-sync config. Works for software products, consulting engagements, platform implementations, and governance programs.
Passed 18 of 21 test cases with the skill, and 6 of 21 without it.
and 21 more in the full report
13 fixed6 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our enterprise architecture committee requires an Architecture Review Board deck prior to go-live for our payment gateway integration. Which slash command generates this presentation, and what default slide format does it output?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies /arb-review as the presentation command. | Missed | Passed |
| Specifies 11 slides as the presentation slide count. | Missed | Passed |
The instructions your model reads when the skill loads.
Every project needs the same core set of interconnected documents. This skill scaffolds a complete documentation ecosystem from day one so that:
/project-docs init — Scaffold a new project from scratch/project-docs init --type consulting — Use consulting template (meetings-heavy)/project-docs init --type product — Use product template (PRD-heavy)/project-docs init --type implementation — Use implementation template (vendor + config)/project-docs audit — Check an existing project against the standard and report gapsEvery project should have these 16 document types organized in 6 categories. Not every project needs all 16 — the skill asks which ones apply and only scaffolds what's needed. Documents 11-16 are generated on demand via dedicated slash commands in the pm-ops skill category.
These are authoritative — all other documents derive from them.
| # | Document | File Pattern | Purpose | Update Trigger |
|---|---|---|---|---|
| 1 | PRD / Requirements | PRD/ or Requirements/ | What we're building and why | Decisions, research findings, stakeholder feedback |
| 2 | Project Memory | CLAUDE.local.md | AI context — architecture, decisions, recent changes | Every session (auto-maintained) |
Raw inputs that feed the root documents. These are append-only — never edited after creation.
| # | Document | File Pattern | Purpose | Update Trigger |
|---|---|---|---|---|
| 3 | Meeting Notes | Meeting-Notes/YYYY-MM-DD-Name.md | Decisions, action items, context from calls | After every meeting |
| 4 | Research | Research/Topic-Name.md | Deep dives, competitive analysis, technical research | As needed |
test cases passed, vs 6 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.