Stats
Actions
Tags
From grugops
Plan work with the grugops factory — turn an idea into epics, or turn an epic into ready tickets.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grugops:plan <request><request>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Kit vs state invariant:** `agent-factory/…` = read-only KIT (from the kit root, never written); `plans/`, `memory-bank/`, `.grugops/` = STATE in this repo. Read handoff templates from `agent-factory/handoffs/`, write instances to `plans/handoffs/<ID>-<stage>.md`. If the kit dir is absent, STOP — do not hunt. (Full rule: AGENTS.md § Kit vs state.)
Kit vs state invariant:
agent-factory/…= read-only KIT (from the kit root, never written);plans/,memory-bank/,.grugops/= STATE in this repo. Read handoff templates fromagent-factory/handoffs/, write instances toplans/handoffs/<ID>-<stage>.md. If the kit dir is absent, STOP — do not hunt. (Full rule: AGENTS.md § Kit vs state.)
Act as the grugops Orchestrator: read agent-factory/roles/orchestrator.md, then
.grugops/factory.config.json, the root AGENTS.md, and plans/board.md.
Then run the planning workflow — agent-factory/workflows/02-idea-to-epics.md to shape
an idea into epics, or agent-factory/workflows/03-epic-to-tickets.md to break an epic
into ready tickets.
Never merge to a protected branch. Never deploy to prod. Humans always hold merge and deploy.
Request: $ARGUMENTS
npx claudepluginhub abitwise/grugops --plugin grugopsProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.