groundwork

groundwork is a skill for Claude Code from ikenga-hq/ikenga-pkgs. It costs 416 tokens per session (5,798 once invoked), scanned A, original, Apache-2.0.

A planning skill that creates and maintains a folder of connected documents for research, design, project plans, task tracking, and coordinated execution.

In plain words
What is it for?
Use it to organize complex software projects, marketing campaigns, or organizational changes from the initial goal through coordinated work and verification.
Why use it?
It keeps decisions, research, tasks, and agent work linked over time, so repeated planning updates the existing material instead of replacing it.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool; mentions Claude Code.

Good fit Use it to organize complex software projects, marketing campaigns, or organizational changes from the initial goal through coordinated work and verification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ikenga-hq/ikenga-pkgs/groundwork
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ikenga-hq/ikenga-pkgs --skill groundwork
Clone the repo
git clone --depth 1 https://github.com/ikenga-hq/ikenga-pkgs

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for groundwork

README.md
[![agentmods](https://agentmods.dev/badge/skills/ikenga-hq/ikenga-pkgs/groundwork.svg)](https://agentmods.dev/skills/ikenga-hq/ikenga-pkgs/groundwork)
Your own site
<a href="https://agentmods.dev/skills/ikenga-hq/ikenga-pkgs/groundwork"><img src="https://agentmods.dev/badge/skills/ikenga-hq/ikenga-pkgs/groundwork.svg" alt="Measured on agentmods" height="20"></a>
Per session 416 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,798 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00416 $0.05798
Opus 5 $0.00208 $0.02899
Sonnet 5 $0.00083 $0.01160
Haiku 4.5 $0.00042 $0.00580

Measured 7d ago against content hash e2c7361b33d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

groundwork scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (profiles/_shared/templates/artifact/orchestrate.workflow.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/skills/groundwork/skills/groundwork/SKILL.md · 275 lines

How it starts

The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.

groundwork — research → plan → orchestrate → act, packaged

This file is a router. Each action and each agent role lives in its own file under actions/ and agents/; load on demand. The state mechanism (.groundwork.json, fences, hash-diff, IDs) is fully specified in lib/state.md — every action obeys it. Read lib/state.md before doing anything that writes to disk.

The full design lives in plans/groundwork/01-plan.md; locked decisions in plans/groundwork/04-discussion.md (Rounds 1–4). This skill is the executable form of that plan.


What groundwork is for

Stripped to one sentence: a stateless action-set that scaffolds and maintains a folder of living planning documents, with traceable IDs threading plan → tracking → orchestration → board, so re-runs augment instead of clobber and a multi-agent kickoff falls out the back end. Originated from the com.ikenga.studio planning workflow; generalized so it works for non-code, non-Ikenga work too.

Surface model:

Surface What it is Trigger
Scaffolder (init) First-run interview + folder skeleton drop User has a goal but no plan folder
Action: research Researcher agent fills 02/03 After scaffolder, or to refresh
Action: design Produces ≥2 comparable designs/*.html for the current phase, locks one Visual/UX work, profile-gated
Action: subplan Scaffolds a focused NN-*.md from one of three archetypes (diff-plan / decision-doc / bug-doc) A hard piece needs its own focused doc (critical-path PR plan, between-round deliberation, postmortem)
Action: review Reviewer agent → new Round in 04 → re-sync via IDs Recurring, highest-value
Action: clarify Readiness gate before orchestrate Before kickoff
Action: orchestrate Generates 09-orchestration.md from 05 When ready to kick off
Action: refresh-board (Re)generates artifact/board.html & artifact/explorer.html and opens/returns artifact/explorer.html Whenever board falls behind
Action: refresh-living-spec Regenerates the spec-state fence inside artifact/index.html (Phasing/Decisions/Risks tabs) from .groundwork.json + 04 + 05 + 01 §Risks When the living-spec's auto tabs fall behind
Action: explorer (Re)generates artifact/explorer.html — a file-tree + tabbed viewer (with search) of the whole plan folder; sibling to the board (opens it as a tab) Browse the plan's files as one navigable view
Action: plans-index (Re)generates <plans-dir>/_index.html — a cross-plan dashboard: one card per plan with status rollups + drill-in to each plan's explorer/board See every plan in a project at once
Action: issue-sync Provisions & syncs native Git forge issues (GitHub/GitLab) for WP-NNs Remote status tracking & PR integration
Action: status Read-only freshness + ID + design-coverage + sub-plan report Anytime

Read the full file on GitHub · 275 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 275 lines · 416 tokens per session scan A e2c7361b33d6

Subscribe to this mod's changes

groundwork is a skill published in the GitHub repository ikenga-hq/ikenga-pkgs (0 stars, last pushed today), licensed Apache-2.0. It adds 416 tokens to every session and 5,798 once invoked, about $0.0021 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens