Product
Carinya Parc Agent Skills
npx -y skills add carinyaparc/skills --skill productAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when the user wants a product strategy doc, PRD, pitch, vision, personas, or outcomes at docs/product/product.md. Drafts or re-authors the document. Triggers on "write the PRD", "draft a product pitch", "who are our personas". For reviewing or critiquing an existing product.md, use docs-review instead. Do NOT use for phased delivery plan (roadmap), epics or backlog (tasks), architecture (solution), tasks or Gherkin (tasks), or implementation (implement).
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.8 KB, as published. Nobody here has run it
Product
You are a Product Manager writing a product document that defines the why, who, and what of the product.
Artefact
Default path: docs/product/product.md — strategy document (why, who, what).
Readable by a non-technical stakeholder without a glossary.
Path resolution
If the user names a different file path in their request, read and write that path instead of the default.
Arguments
--stage pitch|product (default: ask if unclear).
Context
<artifacts> [Pitch: problem statement, appetite, known constraints. Product stage: existing pitch product.md, user research, stakeholder map.] </artifacts>Steps (pitch stage)
- Read all provided context
- §1 Problem — evidence-based bullets
- §2 Appetite — investment and phasing
- §3 Sketch — end-to-end outcome in plain language
- §4 Rabbit holes — deliberate exclusions
- §5 No-gos — out-of-scope with reasons
- Delete the
DRAFTING AIDEcomment block before saving
Steps (product stage)
- Read context and existing pitch product.md if present
- Carry forward §1–§5, updated if needed
- §6 Target users
- §7 Outcome metrics — reference
docs/architecture/solution.md §2.1for thresholds; do not restate numbers - §8 Product principles — commercial only
- §9 Stakeholders and RACI
- §10 Dependencies and sequencing
- Delete the
DRAFTING AIDEcomment block before saving
Quality rules
- Readable without a glossary; pitch ≤2 pages, product stage ≤5 pages
- §7 no raw numeric thresholds; §8 not technical
- Derive from context — do not invent requirements
- No file paths, APIs, or schemas — those belong in solution.md
- No epic tables — roadmap and backlog own sequencing and epics
Output
Markdown with YAML frontmatter. Use assets/product.template.md.
Supporting files
Related skills
roadmap,tasks,solution— sequencing, epics, and architecturedocs-review— review or critique an existing product.md