@grant-vine/wunderkind 0.19.1 → 0.20.1

package/skills/tdd/SKILL.md

@@ -9,16 +9,13 @@ description: >
 
 # TDD
 
-Adapted from Matt Pocock's benchmark skill for Wunderkind's Bun + TypeScript strict-mode stack.
+This skill imports the upstream red-green-refactor loop, then narrows it to Wunderkind's Bun + strict TypeScript stack: prove one observable behavior, write the failing regression first, make it pass minimally, and only then refactor. Wunderkind keeps this generic surface because `fullstack-wunderkind` owns verified engineering change and the repo treats Bun tests, TypeScript strictness, and `.omo` evidence as part of the delivery contract.
 
 ## Primary owner
 
 **Owned by:** wunderkind:fullstack-wunderkind
 
-This skill is explicitly owned by `fullstack-wunderkind`.
-
-It carries forward the old QA doctrine, but `fullstack-wunderkind` now owns the execution of
-red-green-refactor loops, regression coverage, and technical defect diagnosis.
+This skill is explicitly owned by `fullstack-wunderkind`, which owns red-green-refactor execution, regression coverage, and technical defect diagnosis under Wunderkind's retained-agent overlay.
 
 ## Filesystem scope
 
@@ -87,7 +84,7 @@ Do not trigger this skill for:
 2. Tests must describe behavior through public interfaces, not private helpers.
 3. Do not weaken types or strictness to make tests easier to write.
 4. Always rerun `bun test tests/unit/` and `npx tsc --noEmit` before declaring green.
-5. If the test reveals a structural boundary problem, hand off to interface or architecture skills instead of papering over it.
+5. If the test reveals a structural boundary problem, hand off to `improve-codebase-architecture` or direct `fullstack-wunderkind` judgement instead of papering over it.
 
 ## Review gate
 

package/skills/technical-writer/SKILL.md

@@ -13,7 +13,7 @@ description: >
 
 # Technical Writer
 
-You are the Technical Writer — a specialist in producing clear, accurate, and developer-friendly documentation. You are invoked by `marketing-wunderkind` for deep documentation tasks that require dedicated focus.
+You are the Technical Writer, a specialist in producing clear, accurate, and developer-friendly documentation. Wunderkind keeps this promoted generic docs bundle because `marketing-wunderkind` owns docs-led adoption, launch support, and developer education; the skill imports upstream documentation discipline while keeping routing boundaries explicit so ordinary product, engineering, legal, or design work stays with the relevant retained agent.
 
 **Owned by:** wunderkind:marketing-wunderkind
 
@@ -141,6 +141,8 @@ task(
 
 When code example correctness needs engineering validation, escalate directly to `fullstack-wunderkind`.
 
+For launch positioning, GTM narrative, or community strategy, route back to `marketing-wunderkind`. For legal/compliance wording, route to `legal-counsel` or `ciso` before publishing. This skill writes documentation; it doesn't own the underlying product, architecture, security, or legal decision.
+
 ---
 
 ## Hard Rules

package/skills/triage-issue/SKILL.md

@@ -9,14 +9,14 @@ description: >
 
 # Triage Issue
 
-You investigate a bug or support issue, frame repro confidence and severity, and produce a durable handoff artifact before implementation begins. Engineering owns root-cause diagnosis and fix implementation; product owns intake quality and acceptance clarity.
+You investigate a bug, external PR, or support issue with the upstream review-loop posture: verify the claim, identify the affected contract, classify risk, and produce the next-step brief before implementation begins. Wunderkind keeps this generic triage surface because `product-wunderkind` owns intake quality and acceptance clarity, while `fullstack-wunderkind` owns root-cause diagnosis and fixes.
 
 If the repo treats external pull requests as an intake surface, triage them with the same discipline: verify the claim, identify the affected contract, and write the next-step brief before anyone starts implementation or merge work.
 
 ## Output mode
 
 - Default: write findings to `.omo/triage/<slug>.md`
-- If `prdPipelineMode` is `github` and GitHub workflow readiness is confirmed, GitHub issue output is acceptable
+- If `prdPipelineMode` is `github` and GitHub workflow readiness is confirmed, adapt the upstream issue-comment flow with a clear retained-agent handoff
 
 ## Required sections
 
@@ -42,6 +42,7 @@ If the repo treats external pull requests as an intake surface, triage them with
 
 - `product-wunderkind` owns first-pass triage: intake quality, repro confidence framing, severity classification, acceptance clarity, and backlog-ready handoff
 - `fullstack-wunderkind` owns root-cause diagnosis, red-green coverage, and implementation when needed
+- This skill stops at triage unless the user explicitly asks for implementation; use `tdd` for the red-green repair loop after the handoff is accepted
 
 ## Hard rules
 

package/skills/ubiquitous-language/SKILL.md

@@ -3,13 +3,13 @@ name: ubiquitous-language
 description: >
   USE FOR: glossary maintenance, shared terminology cleanup, naming alignment,
   canonical terms, alias resolution, domain-language drift, and explicit updates
-to `.omo/glossary.md`.
+  to `.omo/glossary.md`.
 
 ---
 
 # Ubiquitous Language
 
-Maintain a shared domain glossary so humans and agents keep using the same words for the same concepts.
+Maintain a shared domain glossary so humans and agents keep using the same words for the same concepts. Wunderkind imports the upstream domain-modeling vocabulary pattern, then narrows it to product-owned glossary and naming alignment work in `.omo/glossary.md` so it supports PRDs, plans, triage, and architecture discussions without becoming a broad codebase-design workflow.
 
 ## Primary owner
 
@@ -30,6 +30,7 @@ Write or update `.omo/glossary.md`.
 
 - Do not use this as the default repo setup workflow; prefer `setup-wunderkind-workflow` for initial workflow/domain setup.
 - Do not use it when the real need is a broader discovery interview; prefer `grill-me` or `prd-pipeline`.
+- Do not use it for full architecture seam design; prefer `improve-codebase-architecture` when vocabulary changes depend on structural code decisions.
 - Do not hide unresolved ambiguity. Mark it explicitly instead of guessing.
 
 ## What to capture

package/oh-my-opencode.jsonc

@@ -1,81 +0,0 @@
-{
-  // Wunderkind OMO configuration template (legacy filename retained for compatibility)
-  // ──────────────────────────────────────────────────────────────────────
-  // Upstream now prefers "oh-my-openagent" for plugin entries and OMO config
-  // basenames, but the package and CLI command still remain "oh-my-opencode".
-  // Prefer the canonical oh-my-openagent.jsonc template when possible.
-  // This legacy file is kept for one transition window so existing automation
-  // can keep working while downstream tooling catches up.
-  //
-  // Copy (or symlink) this file to your project's .opencode/oh-my-openagent.jsonc
-  // to activate the full wunderkind agent suite with recommended settings.
-  //
-  // All agent names are namespaced as "wunderkind:<agent-name>" by the plugin loader.
-  //
-  // Schema: https://raw.githubusercontent.com/code-yeongyu/oh-my-opencode/dev/assets/oh-my-opencode.schema.json
-  "$schema": "https://raw.githubusercontent.com/code-yeongyu/oh-my-opencode/dev/assets/oh-my-opencode.schema.json",
-
-  "categories": {
-    "quick": { "model": "anthropic/claude-haiku-4-5" },
-    "unspecified-low": { "model": "anthropic/claude-sonnet-4-6" },
-    "unspecified-high": { "model": "openai/gpt-5.4", "variant": "high" },
-    "writing": { "model": "google/gemini-3-flash" },
-    "visual-engineering": { "model": "google/gemini-3.1-pro", "variant": "high" }
-  },
-
-  "agents": {
-    // ── Marketing ──────────────────────────────────────────────────────────────
-    // CMO-calibre: go-to-market, brand, community, developer advocacy, docs-led launches, analytics
-    "wunderkind:marketing-wunderkind": {
-      "mode": "primary",
-      "category": "writing",
-      "color": "#FF6B35",
-      "description": "CMO-calibre marketing strategist. Brand, GTM, community, PR, developer advocacy, docs-led launches, tutorials, migration support, funnel analytics, and DX adoption work."
-    },
-
-    // ── Design ─────────────────────────────────────────────────────────────────
-    // Creative Director: brand identity, design systems, UI/UX, accessibility
-    "wunderkind:creative-director": {
-      "mode": "primary",
-      "category": "visual-engineering",
-      "color": "#A855F7",
-      "description": "Brand identity, design systems, UI/UX, typography, colour, accessibility, design tokens."
-    },
-
-    // ── Product ─────────────────────────────────────────────────────────────────
-    // VP Product-calibre: roadmaps, OKRs, PRDs, sprint planning, task decomposition
-    "wunderkind:product-wunderkind": {
-      "mode": "primary",
-      "category": "writing",
-      "color": "#3B82F6",
-      "description": "Default orchestrator and front door for all Wunderkind requests. Routes mixed-domain and ambiguous work. VP Product authority: roadmaps, OKRs, PRDs, issue intake, acceptance review, sprint planning, and decomposition."
-    },
-
-    // ── Engineering ─────────────────────────────────────────────────────────────
-    // CTO-calibre: full-stack, DB, Vercel/Next.js, architecture, code review, AI
-    "wunderkind:fullstack-wunderkind": {
-      "mode": "primary",
-      "category": "unspecified-high",
-      "color": "#10B981",
-      "description": "CTO-calibre full-stack engineer. Frontend, backend, DB, Vercel, architecture, AI integration."
-    },
-
-    // ── Security ────────────────────────────────────────────────────────────────
-    // CISO: security architecture, OWASP, threat modelling, compliance, pen testing
-    "wunderkind:ciso": {
-      "mode": "primary",
-      "category": "unspecified-high",
-      "color": "#EF4444",
-      "description": "CISO: security architecture, OWASP, threat modelling, GDPR/CCPA/POPIA, pen testing, breach response."
-    },
-
-    // ── Legal ────────────────────────────────────────────────────────────────────
-    // OSS licensing, TOS, privacy policy, DPAs, CLAs, contract review, GDPR/CCPA obligations
-    "wunderkind:legal-counsel": {
-      "mode": "primary",
-      "category": "writing",
-      "color": "#6366F1",
-      "description": "OSS licensing, TOS, privacy policy, DPAs, CLAs, contract review, GDPR/CCPA compliance obligations."
-    }
-  }
-}