Pm spec
Skill nexu-io/open-design/plugins/_official/examples/pm-spec
π¨ The open-source Claude Design alternative. π₯οΈ Local-first desktop app. πΌοΈ Your coding agent becomes the design engine: prototypes, landing pages, dashboards, slides, images & video β real files, HTML/PDF/PPTX/MP4 export. π€ Claude Code / Codex / Cursor / Gemini / OpenCode / Qwen & 20+ CLIs via BYOK.
npx -y skills add nexu-io/open-design --skill pm-specAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Product spec / PRD as a single page β problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions "PRD", "spec", "product spec", "feature brief", or "ιζ±ζζ‘£".
SKILL.md
1.5 KB, as published. Nobody here has run it
Product Spec Skill
Produce a one-page product spec / PRD.
Workflow
- Read the active DESIGN.md.
- Identify the feature + audience from the brief.
- Layout:
- Header strip: title, status pill (Draft / Review / Approved), date, owner.
- Three-line summary at the top β what, who, why now.
- "Problem" panel with one paragraph and a quote from a customer or internal partner.
- "Goals & non-goals" two-column block.
- "Success metrics" table with metric / target / measurement.
- "User stories" list with as-a / I-want / so-that format.
- "Scope" milestone tracker (3β4 phases).
- "Open questions" with assignee chips.
- One inline
<style>, semantic HTML, accent used twice max.
Output contract
<artifact identifier="spec-name" type="text/html" title="Spec Title">
<!doctype html>...</artifact>