{"id":77044,"plugin_id":"plugins_6ab4123730588191bc9267b9458b2670","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:20.343Z","digest":"67c54936f08c8ff5b6873c96cc7e5d7a5cf37d892e80152c21b21c76f0004696","against":null,"payload":{"description":"Write a concise PRD or product brief that makes scope, requirements and decision tradeoffs actionable.","included_files":[],"name":"write-product-spec","skill_md_contents":"---\nname: write-product-spec\ndescription: Write a concise PRD or product brief that makes scope, requirements and decision tradeoffs actionable.\n---\n\n# Write Product Spec\n\n## When to use\nWrite a concise PRD or product brief that makes scope, requirements and decision tradeoffs actionable.\n\n## Workflow\nChoose a brief for uncertain ideas, a delta spec for existing features, a PRD for coordinated releases, and ADRs for architecture decisions. Record facts and assumptions separately. Include product user/problem, purpose, outcomes, MVP/non-goals, flows, requirements, measurable success signals, risks, constraints, dependencies and unresolved blockers.\n\nEvery substantive requirement should be testable or explicitly a hypothesis. Avoid endless tables and feature inflation. Use `../../templates/product-brief.md` or `../../templates/prd.md` and `../../references/spec-writing.md`.\n\n## Deliverable and truthfulness\nLead with the decision or result, then show supporting evidence, explicit assumptions, risks, and a concrete next step. Adapt depth to the user's ask. If required tools or source material are missing, disclose the limit; do not simulate inspection, implementation or research. Never write/modify/deploy without relevant authorization.\n\nRelevant reference: `../../references/spec-writing.md`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}