spec-kit-product

Make the product documents that `/speckit.product.*` commands generate read like a person wrote them, not a model. Use this skill whenever a generated `product/00-info.md`, `10-spec.md`, `20-plan.md`, or `30-design.md` reads robotic, formulaic, or "AI-generated"; whenever the user asks to humanize, naturalize, de-slop, soften, or polish product prose; right after running a `/speckit.product.*` command when the output feels stiff; and when authoring the product commands or the humanization guide. The practices themselves live in the shipped `templates/humanization-guide.md`; this skill is the contributor-side tool that applies and maintains them. Reach for it even when the user does not say the word "humanize" but clearly wants the product docs to sound human.

Keep the user-facing extension docs (the wiki under docs/, the public website under web/, plus the root README and CHANGELOG) in sync with what the extension actually does. Invoke whenever someone asks to update the docs, sync the wiki, refresh the website, audit docs for drift, document a new command, or after any change under commands/, templates/, extension.yml, or catalog.json. Use it before merging structural changes, even if the user only said 'update the docs' in passing. It writes for the person who USES the extension: what each command does, how to run it, what it produces, and how the pieces fit together. It never documents how the repo is built or released; that lives in CONTRIBUTING.md.