Write and maintain Markdown product specification documents with frontmatter versioning.
npx skills add https://github.com/polikeiji/skills --skill product-spec-polikeiji
Please help me install this Agent Skill. Skill: product-spec Source: https://github.com/polikeiji/skills/tree/main/skills/product-spec Command: npx skills add https://github.com/polikeiji/skills --skill product-spec-polikeiji
This Skill helps you turn vague feature ideas into clear, maintainable product specifications that define what a product should do. It is designed for teams that need a shared source of truth for requirements, behavior, and user-facing outcomes.
Ask the Skill to write or update a product specification for the feature you want documented, and it will create a structured spec in docs/specs/ and update the index when needed.
High-intent search queries and answers about installing and using this skill.
To write a product spec, provide the feature idea and the Skill generates a structured Markdown document in docs/specs/ defining product behavior, user-facing requirements, and edge cases. It organizes specifications with frontmatter versioning and behavior-focused sections for stakeholders.
Maintaining version history in feature documentation is handled through organized Markdown specs with frontmatter versioning and changelogs. The Skill structures documents in docs/specs/ to track updates and ensure stakeholders reference the correct product spec version.
Yes, you can generate a PRD focused on product behavior by requesting a product specification. The Skill drafts stakeholder-ready descriptions that define what the product should do, capturing purpose, behavior, and ownership rather than implementation details.
To keep a spec library index up to date, the Skill automatically maintains docs/specs/README.md when creating or updating product specifications. This ensures the full index of feature documentation remains synchronized, browsable, and easy to understand.
Spec writing with this approach produces stakeholder-ready descriptions by organizing requirements into readable Markdown documents. It captures user-facing outcomes and product behavior clearly, serving as a shared source of truth for teams needing structured feature documentation.
zhengfranTransform ambiguous product ideas into user-approved design specifications.
Yukine5377Convert elicitation Q&A Markdown lists into BA interview DOCX documents.
ThiagoVitaleArchive completed milestones and update project documentation for the next version.
rkz91Transforms meeting transcripts into structured notes with extracted actions, decisions, and flagged impacts.
