initiative
Skill2 starsChanged 5 months agoMITView on GitHub
Author or amend a multi-quarter initiative — the program-level artifact above per-feature specs. Use for 3+ month efforts spanning multiple specs, multiple teams, or multiple quarters. An 18-month migration is one initiative; a 2-day feature is not. Spec template's `complexity: XL` should split into an initiative + multiple specs.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- schmitthub/clawkertheir own version, first seen Nov 5, 2026
- 4erkashin/skillstheir own version, first seen Sep 7, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- schmitthub/clawker★ 59same name
- 4erkashin/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository60 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- analyzeSkill
- animation-disciplineSkill
- api-versioningSkill
- autopilotSkill
- browser-e2eSkill
- characterizeSkill
- clarifySkill
- codemodSkill
- constitution-compactSkill
- constitutionSkill
- context-budgetSkill
- creative-webSkill
- db-migrationSkill
- debugSkill
- detect-stackSkill
- dispatch-criteriaSkill
- dreamSkill
- experimentSkill
- fastapiSkill
- flag-cleanupSkill
- flag-rolloutSkill
- flask-realtimeSkill
- framework-detectorSkill
- front-end-designSkill
- grill-meSkill
- handoffSkill
- image-generationSkill
- implementSkill
- instinctSkill
- loopSkill
- nextjsSkill
- observabilitySkill
- okr-alignSkill
- parallel-swarmSkill
- pivotSkill
- planSkill
- pr-bodySkill
- prime-disciplineSkill
- prod-observabilitySkill
- react-nodeSkill
- react-viteSkill
- release-trainSkill
- researchSkill
- reviewSkill
- security-guardSkill
- self-healSkill
- shipSkill
- skill-creatorSkill
- specifySkill
- tailwind-disciplineSkill
- tasksSkill
- tdd-loopSkill
- token-budgetSkill
- typographySkill
- verify-loopSkill
- verifySkill
- wip-checkpointSkill
- <kebab-case-skill-name>Skill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Rule of thumb: if the spec template's complexity: XL feels right *and* the work spans 2+ quarters, that's an initiative.
- Distinctive: line 52
Every initiative links a KR: No KR? Either you don't need this initiative or your OKRs are wrong.
- Very specific: line 62
Update roadmap.md to reflect.
- Very specific: line 63
Write a .claude/memory/decisions/ entry capturing the program-level lessons.
- Very specific: line 64
Update OKRs.md — close out KR if applicable.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Initiative
The artifact above the spec. Bind multi-quarter programs into a coherent thread.
When to create an initiative vs. a spec
| Signal | Spec | Initiative |
| Effort | days–weeks | quarter–year+ |
| Owners | 1-2 engineers | 3+ engineers, sometimes multiple teams |
| Phases | maybe (in plan.md) | required (multiple specs, gated) |
| KR alignment | 1 KR | 1+ KRs |
| Code reach | bounded feature | platform-wide |
| External dependencies | rare | common (legal, vendor, regulatory) |
| Decision cadence | once | monthly review |
Rule of thumb: if the spec template's complexity: XL feels right and the work spans 2+ quarters, that's an initiative. Split it.
Process
ALL initiatives use the [[grill-me]] skill for discovery — the decisions cascade. Picking a KR shapes phase breakdown shapes flag namespace shapes spec catalog. Batched questions force premature commitment. Round 5 A2.
- Invoke
grill-mewith branch order: KR alignment → success metric → phase 0 → phase 1+ → flag namespace → risk register. One question at a time, recommendation + reasoning per question. - Define phases — each phase ships independently. P0/P1/P2/...; each phase has an exit criterion. Output: filled
## Phasestable. - Catalog specs — list specs that already exist + specs needed. Output: filled
## Spec catalog. - Risk register — top 5 risks, mitigation, owner. Output: filled
## Risks. - Flag policy — flag namespace, owner, default cleanup window. Output: filled
## Feature flag policy. - Save —
initiatives/active/<id>-<slug>.mdfrominitiatives/templates/initiative.md. - Cross-link — update
roadmap.md, link KRs inOKRs.md.
In AUTOPILOT context (Cloud Routine / --bg): grill-me uses recommendations as defaults and surfaces [OQ-pending-operator-review] in the handoff. Initiative status becomes draft-autopilot-needs-review, not approved.
Commands
/initiative create <slug>— grill-me-driven authoring (one-at-a-time, recommendation per question)/initiative status <id>— phase progress, % done, risk health/initiative close <id>— mark shipped/abandoned, archive/initiative supersede <id> --by <new-id>— link supersession
Hard rules
- Every initiative links a KR. No KR? Either you don't need this initiative or your OKRs are wrong. Don't paper over.
- Phases must ship independently. "Phase 1: scaffolding" is not shippable. Rewrite.
- Risks have owners. A risk without an owner is a wish.
- Flag namespace is declared. Without it, flags collide across initiatives.
- Spec catalog stays current. Architect agent updates it when authoring/closing a spec under the initiative.
When an initiative closes
- Mark
status: shipped(orabandoned/superseded). - Move
initiatives/active/<file>→initiatives/archive/. - Update
roadmap.mdto reflect. - Write a
.claude/memory/decisions/entry capturing the program-level lessons. - Update
OKRs.md— close out KR if applicable.
References
- Spec Kit (per-feature spec): https://github.com/github/spec-kit
- Shape Up (cycles): https://basecamp.com/shapeup
- Now/Next/Later roadmaps: https://www.romanpichler.com/blog/the-goal-oriented-product-roadmap/
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

