wtf is goal-workflow?

This repository ships a set of Claude Code skills that try to cover the full path from a feature idea to a merged pull request. The README diagrams the flow as /prd to /prd-to-spec to /goal to /review-it to /ship-it. The idea is that each step is a separate slash command you invoke inside Claude Code, and each one carries the work forward from where the previous step left it. Installation is a single command, npx skills add smallnest/goal-workflow, which assumes the npx skills tool is already configured on the user's machine. The repository is published under the MIT license. The README lists twelve skills in total. The five core workflow ones are /prd to generate a product requirements document and break it into issues, /prd-to-spec to turn the PRD into a technical spec, /goal to implement an issue end to end (noted as built into Claude Code), /review-it to run an automated code review with iterative fixes, and /ship-it to commit, open a pull request, merge, and close the issue. The other seven skills sit alongside as utilities. /note-it captures implementation notes per issue. /humanize-it tries to remove AI traces from documents. /listenhub-tts sends text to speech through ListenHub. /insight-diagram produces UML and architecture diagrams. /code-to-spec works in reverse, generating a spec from an existing project. /refactor applies refactoring patterns drawn from the Fowler catalog. /modern-go applies more than thirty-five gofix-style rules to update older Go code. The repository lists HTML as its primary language because the bulk of the source is the documentation site under docs/, with the entry point at docs/index.html for the full usage guide. The README is short and points the reader to that site for the longer explanation of each skill.