1 · Governed delivery (free)
MIT skills on GitHub teach gates, charters, and status discipline. Top-of-funnel for engineering leads evaluating agentic delivery.
Free skills →Governed delivery for Cursor Teams & IDE Enterprise
Cursor now ships native governance — rules, hooks, and marketplace plumbing. What teams still lack is a repeatable methodology: when work may advance, what evidence counts as PASS, and who owns each gate. G0–G5 (planning) and B0–B6 (ship) define that discipline.
Skills teach governed delivery. Governed plugins enforce it.
Governed delivery (G0–G5 · B0–B6) starts free — MIT skills on GitHub. Enforcement is the paid layer: proprietary governed plugins with always-on rules, shell hooks, scaffolds, and optional CI. Same gates — skills advise when @-invoked; plugins govern every run.
Gate landscape
Planning gates (G) advance work; ship gates (B) block release until verified
flowchart LR
subgraph planning [Planning G0-G5]
G0[Charter] --> G1[Architecture]
G1 --> G2[Implementation]
G2 --> G3[Verification]
G3 --> G4[Documentation]
G4 --> G5[Release readiness]
end
subgraph ship [Ship B0-B6]
B0[Charter SSOT] --> B1[Install]
B1 --> B2[Lint]
B2 --> B3[Tests]
B3 --> B4[Build]
B4 --> B5[Verify]
B5 --> B6[Director sign-off]
end
G5 -.-> B0
Gate landscape — director-owned planning gates feed ship gates; plugins and hooks enforce B-series evidence on every run.
cursorpluginkits.com gate stack
├── Planning (G0–G5) … director / role owners
│ └── PASS or WAIVED row per gate
└── Ship (B0–B6) … verify-before-merge
└── hooks + optional CI (governed-builds plugin)
Planning gates — G0–G5
Director-owned hard stops before implementation advances
| Gate | Name | PASS criteria | Owner |
|---|---|---|---|
| G0 | Charter | Agent charter filled — scope, non-goals, target completeness | Director |
| G1 | Architecture | Stack table + diagram + related paths documented | Architecture |
| G2 | Implementation | Requested files exist; lints clean; no scope creep | Implementation |
| G3 | Verification | npm run verify (or charter command) exit 0 | Verification |
| G4 | Documentation | Docs map matches routes; headers + completeness ≥ charter | Documentation |
| G5 | Release readiness | Deploy doc updated; env template matches code; no secrets staged | Director |
Full reference: MIT skill @hierarchical-agent-orchestration
Ship gates — B0–B6
Verify-before-ship — agents cannot claim “done” without evidence
| Gate | Owner | PASS evidence |
|---|---|---|
| B0 | Human / agent | build-charter.md complete |
| B1 | Shell | Install log exit 0 |
| B2 | Linter | Lint exit 0 or charter waiver |
| B3 | Tests | Test command exit 0 |
| B4 | Build | Build command exit 0 |
| B5 | Verify | Verify command exit 0 |
| B6 | Director | Release row in LATEST; no secrets in git status |
Full reference: MIT skill @governed-builds
Three layers — not three products
2 · Governed plugins
Always-on rules, shell hooks, scaffolds, and CI — enforcement for G0–G5 / B0–B6.
Plugins from £49 →3 · Adoption (consultancy)
Teknoled-G implements the methodology in your repos, risk appetite, and Team Marketplace rollout — senior-led, not slide decks.
Consulting →Built by Teknoled-G
Who we are
Teknoled-G Limited (Co. #16749208) — AI integration consultancy. Methodology authored by Timothy R. McGuckin from client delivery work, not marketplace copy.
Early adopter programme
We are onboarding a small number of engineering teams for governed Cursor rollout. Named case studies when clients approve — apply for pilot.
Why gates matter now
Native Cursor governance handles plumbing. Gates handle accountability — auditable PASS/WAIVED rows, director ownership, and verify-before-merge culture.