What's shipped, what's in flight, and what's deferred. Canonical planning lives in
/Users/zakelfassi/.claude/plans/linear-gathering-hamming.md(not checked in — it's a working document).
v0.3.0 (2026-04-13) — skdd doctor + skdd import + VS Code extension scaffold + visual identity + docs site scaffold + community files. See CHANGELOG.md for the full list.
SkDD is being built in named tranches (P0 → P5). Each tranche ships as a batch of commits.
| Tranche | Scope | Status |
|---|---|---|
| P0 — Correctness bugs | legacy-handle rename holes, broken README steps, missing .gitignore, broken anchors, missing scripts in examples |
✅ Shipped (v0.1.0) |
| P1 — Onboarding UX | docs/configuration.md, quick-start rewrite, CONTRIBUTING.md, terminology glossary, examples polish |
✅ Shipped (v0.1.0) |
| P2 — Tooling | skdd CLI (init/validate/forge/list/sync), registry JSON format, inter-skill composition spec, vendored spec snapshot, CI, pre-commit |
✅ Shipped (v0.1.0) |
| P3 — Platform integrations | .colony.json manifest, 11 harness integration docs, Claude Code plugin scaffold |
✅ Shipped (v0.1.0) |
| Canonical + mirror pattern | skdd link, fs-link.ts, sync-state.ts, canonical default in init/forge, 11 docs updated |
✅ Shipped (v0.2.0) |
| E — Alpha features | skdd doctor, skdd import, VS Code extension scaffold, SchemaStore PR prep |
✅ Shipped (v0.3.0) |
| F — Shareability | Logo/wordmark SVGs, Mermaid diagrams, README badges, docs/why-skdd.md, Starlight docs site |
✅ Shipped (v0.3.0) |
| G — Community scaffolding | SECURITY, CoC, CODEOWNERS, issue/PR templates, FUNDING, CHANGELOG, ROADMAP | ✅ Shipped (v0.3.0) |
| H — CLI depth + quality bar | skdd stats, search, migrate, compose, link --watch, completion, ESLint/Prettier, Changesets, e2e tests, SkddError class, man pages |
⏸ Deferred |
| P4 — Strategy / Ecosystem | Marketplace submissions, RFC upstream for lifecycle metadata, security doc, SkDD rename debate, governance | ⏸ Deferred |
These have to be flipped in the repo Settings UI. Checked as they land:
- Social preview image — upload
.github/social-preview.png(1280×640) via GitHub Settings → Social preview - GitHub Discussions — enable at Settings → Features → Discussions, then pin a "Welcome / RFC" post
- Repo topics — add
agent-skills,claude-code,codex,cursor,agentskills-io,skills-driven-development,ai-agents,cli,typescript,skill-colony - GitHub Pages — Settings → Pages → Source = "GitHub Actions" (enables the
deploy-docs.ymlworkflow output) - Branch protection on
main— require PR review + passing CI (once there's more than one maintainer) - Secrets —
NPM_TOKENforpublish-skills.ymlonce we're ready to publish to npm
None committed. When the dust settles, candidates include:
- Marketplace submissions — SkillsMP, Skills.sh, ClawHub, LobeHub, Claude Code Plugin Marketplace
- SchemaStore.org PR — submit
.colony.jsonusingdocs/schemastore-submission.mdas the draft body - Upstream RFC to agentskills.io for the SkDD lifecycle metadata profile (
forged-by,usage-count,last-used,status, etc.) - Content ingestion for the docs site — decide between per-build copy, symlink, or a Starlight content loader, and wire
site/to consume the repo'sdocs/directory - VS Code extension publish — package
extensions/vscodeas a.vsixand submit to the VS Code Marketplace skdd migrate— one-shot converter from flat per-harness layout to canonical + mirrorskdd link --watch— fs watcher for continuous syncSkddErrorclass + documented exit codes — better CI ergonomics- Integration tests — end-to-end tests that spawn the built binary (
cli/test/e2e/)
Things SkDD is deliberately not doing. If you want these, SkDD is not the right project:
- A runtime that executes skills (your harness does that)
- A hosted colony registry or server-side skill index
- A review gate on every skill creation (SkDD's bias is forge-then-evolve)
- Semantic/AI-based skill search (the registry is plain text; search is up to the harness)
- A governance body — SkDD is currently a solo-maintained project; governance docs arrive only if the community does
- Small feature: open an issue with the feature request template
- Big feature or methodology change: file an RFC via the RFC template or open a draft PR with
[RFC]in the title - New skill: use the new skill template
- Security issue: use GitHub's private advisory flow — see SECURITY.md