Pragmatic Growth workflow skills for Claude Code — define-goal (plain-language wants → measurable goal contracts, run now via /goal or queued in docs/goals), dispatch (factory orchestrator for the docs/goals queue), and loop-architect (design autonomous loop contracts).
Use when the user states something they want — a goal, wish, feature, fix, or annoyance ("I want…", "set a goal", "/define-goal"), asks to clarify success criteria or turn fuzzy intent into a measurable objective, OR hands over a document with multiple items (bug report doc, feedback list, meeting notes) to convert. Also use to add work to the docs/goals queue. Defines goals only; never starts the implementation work.
Factory dispatcher — use when the user says "/dispatch", "run the factory", wants the docs/goals queue worked, or wants to work one specific queued goal in this session ("work goal 005"). Shepherds factory PRs through review, claims queued goals, and spawns one isolated implementer agent per goal. Designed to run as `/loop 15m /dispatch`; iterations are idempotent, and parallel sessions are safe. Works in any repo with a docs/goals/ queue. Orchestrates only — never implements in its own context.
Use when the user wants to automate, schedule, or run work autonomously/remotely — setting up a /goal, /loop, routine, channel, or long unattended run, or asking "how do I keep Claude working on X". Designs the loop contract (prompt + verification + stop conditions) instead of just running the task.
Pragmatic Growth workflow skills for Claude Code, distributed via the
pragmatic-growth marketplace.
A skills-only plugin — no MCP servers, no commands, no hooks. Three skills that together form a plain-language → autonomous-execution pipeline backed by a file-based goal queue:
| Skill | What it does |
|---|---|
| define-goal | Shapes plain-language wants ("I want…", /define-goal) — or whole documents of them — into measurable goal contracts. Hands back a copy-pasteable /goal line to run now, or queues a goal file in the repo's docs/goals/ directory. Never implements. |
| dispatch | Factory orchestrator. Shepherds factory PRs through review, claims queued goals from docs/goals/index.yaml, and spawns one isolated implementer agent per goal. Designed to run as /loop 15m /dispatch. |
| loop-architect | Designs the loop contract (prompt + verification + stop conditions) for autonomous, scheduled, or long unattended runs instead of just firing off the task. |
The intended flow: capture wants with define-goal (queued into
docs/goals/) → work the queue with dispatch → keep it running
unattended with a loop designed by loop-architect.
Goals live in the target repo, not on GitHub — no issue-body size limits, no label bootstrap, versioned with the code. PRs remain the review and merge surface.
docs/goals/
├── index.yaml # config + queue state — status lives ONLY here
├── 001-<slug>.md # goal contracts — content only, never status
└── done/ # archived completed goal files
Statuses: not_started → in_progress → completed, plus blocked
(with a reason). The index's config: block sets the integration
branch (base: — main, staging, or any other; goals branch from it and
merge back to it), the merge policy (pr = human merges, auto = the
factory rebases, re-verifies, and merges back itself), the parallelism
cap (wip:), the model for spawned code agents (model: — inherit,
sonnet, or haiku to stretch weekly limits), and repo-wide skills:
every implementer must invoke; goal files add goal-specific skills:
and a type: (bug | feature | chore) that shapes the contract in
frontmatter.
define-goal creates goal files and index entries; status writes go
through dispatch's claim protocol (pull → flip → commit → push, with
push acceptance on the base branch as the arbiter), so parallel
sessions can safely work the same queue. Implementer agents work in
isolated worktrees branched from origin/<base> and never touch
docs/goals/ at all.
# Add the marketplace, then install the plugin
/plugin marketplace add pragmaticgrowth/pg-plugin
/plugin install pg-plugin@pragmatic-growth
Once installed, the skills surface namespaced as pg-plugin:define-goal,
pg-plugin:dispatch, and pg-plugin:loop-architect. They activate
automatically when the conversation matches their description, or invoke
them directly: /define-goal, /dispatch.
pg-plugin/
├── .claude-plugin/
│ ├── plugin.json # plugin manifest
│ └── marketplace.json # pragmatic-growth marketplace
└── skills/
├── define-goal/SKILL.md
├── dispatch/
│ ├── SKILL.md
│ ├── references/herdr-mode.md # config.execution: herdr contract
│ └── scripts/ # vendored herdr ops kit (pm.py, MIT)
└── loop-architect/SKILL.md
MIT
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub pragmaticgrowth/pg-plugin --plugin pg-pluginUnity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Plugin-safe Claude Code distribution of Antigravity Awesome Skills with 1,561 supported skills.
Comprehensive C4 architecture documentation workflow with bottom-up code analysis, component synthesis, container mapping, and context diagram generation