explaingit

smallnest/goal-workflow

Analysis updated 2026-06-24

34HTMLAudience · developerComplexity · 2/5LicenseSetup · easy

TLDR

Collection of Claude Code skills that take a feature idea from PRD through spec, implementation, review, and shipped pull request via twelve slash commands.

Mindmap

mindmap
  root((goal-workflow))
    Inputs
      Feature idea
      Existing repo
      Issue link
    Outputs
      PRD
      Technical spec
      Pull request
      Refactored code
    Use Cases
      Drive feature delivery
      Run code review loop
      Refactor legacy Go
      Generate diagrams
    Tech Stack
      Claude Code
      Skills
      npx
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Drive a feature from PRD to merged pull request inside Claude Code

USE CASE 2

Run an automated code review with iterative fixes on a branch

USE CASE 3

Apply Fowler-style refactoring patterns to an existing codebase

USE CASE 4

Modernize older Go code with gofix-style rules

What is it built with?

Claude CodeHTMLMarkdown

How does it compare?

smallnest/goal-workflowzhaochamyu/japaneseonchainmihozip/google-workspace-admin-project-workflow
Stars343431
LanguageHTMLHTMLHTML
Setup difficultyeasyeasymoderate
Complexity2/51/52/5
Audiencedeveloperdeveloperops devops

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Assumes the npx skills tool and Claude Code are already configured on the machine.

MIT license, use, modify, and redistribute freely as long as you keep the copyright notice.

In plain English

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.

Copy-paste prompts

Prompt 1
Install smallnest/goal-workflow via npx skills add and run /prd to draft a PRD for a new feature
Prompt 2
Walk me through the prd to prd-to-spec to goal to review-it to ship-it flow on a small refactor task
Prompt 3
Use /modern-go on this legacy Go module and explain which rules fired
Prompt 4
Generate a UML and architecture diagram for this service using /insight-diagram

Frequently asked questions

What is goal-workflow?

Collection of Claude Code skills that take a feature idea from PRD through spec, implementation, review, and shipped pull request via twelve slash commands.

What language is goal-workflow written in?

Mainly HTML. The stack also includes Claude Code, HTML, Markdown.

What license does goal-workflow use?

MIT license, use, modify, and redistribute freely as long as you keep the copyright notice.

How hard is goal-workflow to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is goal-workflow for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.