@grant-vine/wunderkind 0.4.0 → 0.8.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "wunderkind",
-  "version": "0.4.0",
-  "description": "Wunderkind — specialist AI agents for any software product team, built as an oh-my-opencode addon",
+  "version": "0.8.0",
+  "description": "Wunderkind \u2014 specialist AI agents for any software product team, built as an oh-my-openagent addon",
   "main": "dist/index.js"
 }

package/README.md

@@ -1,15 +1,58 @@
 # Wunderkind
 
-Wunderkind — specialist AI agent addon for OpenCode that extends your team with eight professional agents covering marketing, design, product, engineering, brand building, QA, operations, and security.
+Wunderkind — specialist AI agent addon for OpenCode that extends your team with 12 professional agents covering marketing, design, product, engineering, brand building, QA, operations, security, devrel, legal, support, and data analysis.
 
-**Requires OpenCode.** This package cannot be used standalone.
+**Requires [OpenCode](https://opencode.ai) and [oh-my-openagent](https://github.com/code-yeongyu/oh-my-openagent).** This package cannot be used standalone.
+
+> [!IMPORTANT]
+> **Breaking change (0.7.0)**: This is a pre-1.0 release. Older installs are not supported. Please ensure you are using the latest version of both Wunderkind and oh-my-openagent.
+
+---
+
+## CLI
+
+Wunderkind provides a tiered CLI for installation, project setup, and health checks.
+
+| Command | Purpose | Modifies |
+|---|---|---|
+| `wunderkind install` | Registers the plugin in OpenCode | `opencode.json` (Global or Project) |
+| `wunderkind init` | Bootstraps a project with soul files | `.wunderkind/`, `AGENTS.md`, `.sisyphus/` |
+| `wunderkind doctor` | Read-only diagnostics | None |
+| `wunderkind gitignore` | Adds AI traces to `.gitignore` | `.gitignore` |
+
+---
+
+## Install vs Init
+
+Wunderkind distinguishes between **installing** the plugin and **initializing** a project:
+
+1. **Install** (`wunderkind install`): Adds `@grant-vine/wunderkind` to your OpenCode configuration. This makes the agents available to your AI assistant. You typically do this once globally.
+2. **Init** (`wunderkind init`): Prepares the current directory for high-context agent work. It creates the `.wunderkind/` configuration directory, the `AGENTS.md` project knowledge base, and optional documentation output folders.
 
 ---
 
 ## Install
 
-### Interactive TUI
-The recommended way to install Wunderkind is using the interactive TUI. Run the following command in your project directory:
+### Have Your Agent Install This
+
+Copy this prompt to your AI assistant (Claude, Copilot, Cursor, etc.):
+
+```
+Please install and configure @grant-vine/wunderkind by following the instructions at:
+https://raw.githubusercontent.com/grant-vine/wunderkind/main/docs/guide/installation.md
+```
+
+For agents that can run shell commands directly:
+
+```bash
+curl -s https://raw.githubusercontent.com/grant-vine/wunderkind/main/docs/guide/installation.md
+```
+
+The guide contains all flags for non-interactive install so the agent can run a single command without prompts.
+
+---
+
+### Interactive TUI (recommended)
 
 ```bash
 bunx @grant-vine/wunderkind
@@ -22,13 +65,21 @@ npx @grant-vine/wunderkind
 ```
 
 The TUI will guide you through:
-1. Selecting the install scope (Global vs Project).
-2. Configuring your project context: region, industry, and data-protection regulations.
-3. Tailoring agent personalities and your team's culture baseline.
+1. Installing oh-my-openagent if it isn't already (runs its own setup flow first).
+2. Selecting the install scope (Global vs Project).
+3. Configuring your project context: region, industry, and data-protection regulations.
+4. Tailoring agent personalities and your team's culture baseline.
 
 ### Non-interactive install
+
 For CI/CD or scripted environments, use the `install` command with the `--no-tui` flag.
 
+> **oh-my-openagent must already be installed** before running non-interactive mode. If it isn't, install it first:
+> ```bash
+> bunx oh-my-opencode install --no-tui --claude=yes --gemini=no --copilot=yes
+> ```
+> See the [oh-my-openagent docs](https://github.com/code-yeongyu/oh-my-openagent) for all available options.
+
 ```bash
 bunx @grant-vine/wunderkind install --no-tui \
   --scope=global \
@@ -49,6 +100,68 @@ bunx @grant-vine/wunderkind install --no-tui \
 
 ---
 
+## Init
+
+Initialize the current directory as a Wunderkind project to enable advanced features like Documentation Output and agent context persistence.
+
+```bash
+wunderkind init [options]
+```
+
+### Options
+
+| Option | Description | Default |
+|---|---|---|
+| `--docs-path <path>` | Relative path for agent docs output | `./docs` |
+| `--docs-history-mode <mode>` | Update style for documentation | `overwrite` |
+| `--no-docs` | Disable documentation output | (false) |
+| `--no-tui` | Skip interactive prompts | (false) |
+
+`wunderkind init` creates the following project "soul files":
+- `.wunderkind/wunderkind.config.jsonc` — Project-specific configuration
+- `AGENTS.md` — Project knowledge base for agents
+- `.sisyphus/` — Directory for agent planning, notepads, and evidence
+- `<docsPath>/README.md` — Auto-generated documentation index (if enabled)
+
+### Documentation History Modes
+
+| Mode | Description |
+|---|---|
+| `overwrite` | Replaces the file contents each time (default) |
+| `append-dated` | Appends a new dated section to the file |
+| `new-dated-file` | Creates a new file with a date suffix |
+| `overwrite-archive` | Overwrites the current file and archives the old one |
+
+---
+
+## Doctor
+
+Run diagnostics to verify your installation, configuration, and project health.
+
+```bash
+wunderkind doctor
+```
+
+`wunderkind doctor` reports:
+- Installed version and scope (Global vs Project)
+- Location of configuration files
+- Presence and status of project soul files (in a project context)
+- Current Documentation Output configuration and index status
+
+`wunderkind doctor` is strictly read-only and makes no changes to your filesystem.
+
+---
+
+## Documentation Output
+
+When enabled, agents can persist their decisions and strategies to your project's docs folder.
+
+1. **Enable** via `wunderkind init --docs-path ./docs`
+2. **Configure** in `.wunderkind/wunderkind.config.jsonc` via `docsEnabled`, `docsPath`, and `docHistoryMode`.
+3. **Index** via `/docs-index`. This is a **prompt-text slash command** that agents respond to (not a CLI command). Running `/docs-index` instructs agents to scan your documentation folder and regenerate the `<docsPath>/README.md` index.
+
+---
+
 ## Install Scope
 
 | Scope | Description |
@@ -56,20 +169,28 @@ bunx @grant-vine/wunderkind install --no-tui \
 | `global` (default) | Adds the plugin to `~/.config/opencode/opencode.json`. Agents are available in all projects. |
 | `project` | Adds the plugin to `./opencode.json` (created if missing). Agents are limited to the current project. |
 
+Wunderkind writes its own agent config to a separate file — it never modifies your existing oh-my-openagent configuration. Removing Wunderkind leaves oh-my-openagent intact.
+
 ---
 
 ## Agents
 
-| Agent Key | Role | Model |
+| Agent Key | Role | Category |
 |---|---|---|
-| `wunderkind:marketing-wunderkind` | CMO-calibre strategist | claude-sonnet-4-5 |
-| `wunderkind:creative-director` | Brand & UI/UX lead | gemini-2.0-flash |
-| `wunderkind:product-wunderkind` | VP Product | claude-sonnet-4-5 |
-| `wunderkind:fullstack-wunderkind` | CTO-calibre engineer | claude-sonnet-4-5 |
-| `wunderkind:brand-builder` | Community, PR, thought leadership | claude-sonnet-4-5 |
-| `wunderkind:qa-specialist` | TDD, coverage, user story review | claude-sonnet-4-5 |
-| `wunderkind:operations-lead` | SRE/SLO, runbooks, incident response | claude-sonnet-4-5 |
-| `wunderkind:ciso` | Security architecture, OWASP, compliance | claude-sonnet-4-5 |
+| `wunderkind:marketing-wunderkind` | CMO-calibre strategist | writing |
+| `wunderkind:creative-director` | Brand & UI/UX lead | visual-engineering |
+| `wunderkind:product-wunderkind` | VP Product | writing |
+| `wunderkind:fullstack-wunderkind` | CTO-calibre engineer | unspecified-high |
+| `wunderkind:brand-builder` | Community, PR, thought leadership | writing |
+| `wunderkind:qa-specialist` | TDD, coverage, user story review | unspecified-high |
+| `wunderkind:operations-lead` | SRE/SLO, runbooks, incident response | unspecified-high |
+| `wunderkind:ciso` | Security architecture, OWASP, compliance | unspecified-high |
+| `wunderkind:devrel-wunderkind` | Developer relations and advocacy | writing |
+| `wunderkind:legal-counsel` | Legal and regulatory compliance | writing |
+| `wunderkind:support-engineer` | Technical support and troubleshooting | writing |
+| `wunderkind:data-analyst` | Data analysis and insights | writing |
+
+Agent models are determined by category inheritance configured in `oh-my-opencode.jsonc`. Each agent maps to a category (`writing`, `unspecified-high`, or `visual-engineering`) and inherits the model defined in the top-level `categories` section of that file.
 
 ---
 
@@ -88,62 +209,23 @@ bunx @grant-vine/wunderkind install --no-tui \
 
 ---
 
-## Memory Commands
-
-Manage agent memories stored in `.wunderkind/memory/` using the `memory` subcommand.
-
-```bash
-# Save a note to an agent's memory
-wunderkind memory take-note --agent ciso --note "All production database access must go through the jump box."
-
-# Search an agent's memories
-wunderkind memory search --agent ciso --query "database access"
-
-# Show memory count and stats for all agents
-wunderkind memory count
-
-# Show stats for a specific agent
-wunderkind memory count --agent ciso
-
-# Check the health of the configured memory adapter
-wunderkind memory status
-
-# Start memory services (required for mem0 adapter)
-wunderkind memory start
-
-# Analyze and preview stale memories for an agent
-wunderkind memory reduce-noise --agent ciso
-
-# Actually remove stale entries
-wunderkind memory reduce-noise --agent ciso --confirm
-
-# Export all memories to a zip file in .wunderkind/exports/
-wunderkind memory export
-
-# Import memories from a backup zip
-wunderkind memory import backup.zip --strategy merge
-```
-
-### Import Strategies
-- `merge` (default): Adds new memories from the zip without removing existing ones.
-- `overwrite`: Clears existing memories before importing from the zip.
-
----
-
 ## Configuration
 
-Wunderkind uses a hierarchical configuration system.
+Wunderkind uses a hierarchical configuration system. The per-project config is merged on top of the global baseline at runtime — project values take precedence.
+
+| File | Scope |
+|---|---|
+| `~/.wunderkind/wunderkind.config.jsonc` | Global baseline (applies to all projects) |
+| `.wunderkind/wunderkind.config.jsonc` | Per-project override |
 
-- **Global baseline**: `~/.wunderkind/wunderkind.config.jsonc`
-- **Per-project override**: `.wunderkind/wunderkind.config.jsonc`
+Edit either file directly to change any value after install. The installer pre-fills both files with the values you provided during setup.
 
-### Configuration Structure
-The `wunderkind.config.jsonc` file allows you to tailor agents to your project context:
+### Configuration Reference
 
 ```jsonc
 // Wunderkind configuration — edit these values to tailor agents to your project context
 {
-  // Geographic region — e.g. "South Africa", "United States", "United Kingdom"
+  // Geographic region — e.g. "South Africa", "United States", "United Kingdom", "Australia"
   "region": "South Africa",
   // Industry vertical — e.g. "SaaS", "FinTech", "eCommerce", "HealthTech"
   "industry": "SaaS",
@@ -159,14 +241,30 @@ The `wunderkind.config.jsonc` file allows you to tailor agents to your project c
   "orgStructure": "flat",
 
   // Agent personalities — controls each agent's default character archetype
+  // CISO: "paranoid-enforcer" | "pragmatic-risk-manager" | "educator-collaborator"
   "cisoPersonality": "pragmatic-risk-manager",
+  // CTO/Fullstack: "grizzled-sysadmin" | "startup-bro" | "code-archaeologist"
   "ctoPersonality": "code-archaeologist",
+  // CMO/Marketing: "data-driven" | "brand-storyteller" | "growth-hacker"
   "cmoPersonality": "data-driven",
+  // QA: "rule-enforcer" | "risk-based-pragmatist" | "rubber-duck"
   "qaPersonality": "risk-based-pragmatist",
+  // Product: "user-advocate" | "velocity-optimizer" | "outcome-obsessed"
   "productPersonality": "outcome-obsessed",
+  // Operations: "on-call-veteran" | "efficiency-maximiser" | "process-purist"
   "opsPersonality": "on-call-veteran",
+  // Creative Director: "perfectionist-craftsperson" | "bold-provocateur" | "pragmatic-problem-solver"
   "creativePersonality": "pragmatic-problem-solver",
-  "brandPersonality": "authentic-builder"
+  // Brand Builder: "community-evangelist" | "pr-spinner" | "authentic-builder"
+  "brandPersonality": "authentic-builder",
+
+  // Documentation Output (Init-only customizations)
+  // "true" | "false"
+  "docsEnabled": false,
+  // Relative path (e.g. "./docs", "./documentation")
+  "docsPath": "./docs",
+  // "overwrite" | "append-dated" | "new-dated-file" | "overwrite-archive"
+  "docHistoryMode": "overwrite"
 }
 ```
 
@@ -174,41 +272,25 @@ The `wunderkind.config.jsonc` file allows you to tailor agents to your project c
 
 ## Directory Structure
 
-### Project Local
-```
-.wunderkind/            # per-project directory (should be gitignored)
-  wunderkind.config.jsonc
-  memory/               # file adapter storage
-  memory.db             # sqlite adapter storage
-  exports/              # memory export zips
-```
+### Per-project (gitignored automatically)
 
-### Global Shared
 ```
-~/.wunderkind/          # global shared directory
-  wunderkind.config.jsonc
-  docker-compose.vector.yml
-  docker-compose.mem0.yml
+.wunderkind/
+  wunderkind.config.jsonc     # per-project config override
 ```
 
----
-
-## Memory Adapters
-
-Wunderkind supports four memory adapters for agent persistence:
+### Global (`~/.wunderkind/`)
 
-1. **`file`** (default): Stores memories as flat files in `.wunderkind/memory/`.
-2. **`sqlite`**: Stores memories in a local `.wunderkind/memory.db` database.
-3. **`vector`**: Uses Qdrant for vector-based semantic search.
-4. **`mem0`**: Advanced memory management using the mem0 framework.
-
-**Note**: Vector and mem0 adapters use a shared instance with project namespacing via a project slug derived from your `package.json` name.
+```
+~/.wunderkind/
+  wunderkind.config.jsonc     # global config baseline
+```
 
 ---
 
 ## Manual Installation
 
-To manually add Wunderkind to your OpenCode configuration, update the `plugin` array in your `opencode.json` or `opencode.jsonc` file:
+To manually add Wunderkind to your OpenCode configuration, update the `plugin` array in your `opencode.json`:
 
 ```json
 {
@@ -218,9 +300,22 @@ To manually add Wunderkind to your OpenCode configuration, update the `plugin` a
 
 ---
 
+## Gitignore
+
+Run this command to ensure `.wunderkind/` and other AI tooling directories are gitignored in your project:
+
+```bash
+wunderkind gitignore
+```
+
+This adds `.wunderkind/`, `AGENTS.md`, `.sisyphus/`, and `.opencode/` to your `.gitignore` if they aren't already present.
+
+---
+
 ## Requirements
 
 - [OpenCode](https://opencode.ai)
+- [oh-my-openagent](https://github.com/code-yeongyu/oh-my-openagent)
 - Node.js 18+ or Bun 1+
 
 ---

package/agents/brand-builder.md

@@ -6,7 +6,7 @@ description: >
 
 # Brand Builder — Soul
 
-You are the **Brand Builder**. Before acting, read `wunderkind.config.jsonc` and load:
+You are the **Brand Builder**. Before acting, read `.wunderkind/wunderkind.config.jsonc` and load:
 - `brandPersonality` — your character archetype:
   - `community-evangelist`: Community is infrastructure. Invest in it consistently, show up constantly, and treat members as the most valuable asset. People first, always.
   - `pr-spinner`: Narrative is everything. Every story angle, every journalist relationship, every moment of earned media leverage matters. Craft the message relentlessly.
@@ -14,8 +14,6 @@ You are the **Brand Builder**. Before acting, read `wunderkind.config.jsonc` and
 - `teamCulture` and `orgStructure` — adjust communication formality and conflict resolution style accordingly.
 - `region` — prioritise local community platforms, events, industry forums, and cultural nuances.
 
-Read `.wunderkind/memory/brand-builder.md` (if present) — project-specific brand community decisions, PR contacts, platform presence, and audience context you have accumulated. When you learn something new, call `wunderkind_take_note`. To recall past knowledge, call `wunderkind_search_memories`. Load the `wunderkind:memory-manager` skill for full memory command reference.
-
 ---
 
 # Brand Builder
@@ -48,7 +46,7 @@ Your north star: *build the brand by doing the work publicly and being genuinely
 - Identify relevant product forums, Slack communities, Discord servers, subreddits, LinkedIn groups
 - Engagement strategy for each: how to add value before asking for anything
 - Weekly networking cadence: who to connect with, what to share, what conversations to enter
-- Conference and event calendar: which events matter, which are worth sponsoring vs attending vs speaking at — read `wunderkind.config.jsonc` for `region` and `industry` to prioritise regionally relevant events
+- Conference and event calendar: which events matter, which are worth sponsoring vs attending vs speaking at — read `.wunderkind/wunderkind.config.jsonc` for `region` and `industry` to prioritise regionally relevant events
 - Partnership opportunities: integration partners, content collaborators, co-marketing
 
 ### PR & Brand Narrative
@@ -102,7 +100,7 @@ Audit the current community presence across all platforms.
 ### `/forum-research <industry/product>`
 Find the highest-value forums, communities, and events for a given domain.
 
-**First**: read `wunderkind.config.jsonc` for `region` and `industry` to filter for regionally relevant communities and events. If blank, return a globally diverse list.
+**First**: read `.wunderkind/wunderkind.config.jsonc` for `region` and `industry` to filter for regionally relevant communities and events. If blank, return a globally diverse list.
 
 ```typescript
 task(
@@ -220,6 +218,55 @@ task(
 
 ---
 
+---
+
+## Persistent Context (.sisyphus/)
+
+When operating as a subagent inside an oh-my-openagent workflow (Atlas/Sisyphus), you will receive a `<Work_Context>` block specifying plan and notepad paths. Always honour it. When operating independently, use these conventions.
+
+**Read before acting:**
+- Plan: `.sisyphus/plans/*.md` — READ ONLY. Never modify. Never mark checkboxes. The orchestrator manages the plan.
+- Notepads: `.sisyphus/notepads/<plan-name>/` — read for inherited context, community growth patterns, and narrative decisions.
+
+**Write after completing work:**
+- Learnings (community engagement tactics that worked, PR angles that landed, forum contributions that drove results): `.sisyphus/notepads/<plan-name>/learnings.md`
+- Decisions (platform prioritisation, narrative choices, partnership decisions): `.sisyphus/notepads/<plan-name>/decisions.md`
+- Blockers (pending approvals, legal reviews, missing spokesperson availability): `.sisyphus/notepads/<plan-name>/issues.md`
+
+**APPEND ONLY** — never overwrite notepad files. Use Write with the full appended content or append via shell. Never use the Edit tool on notepad files.
+
+## Documentation Output (Static Reference)
+
+When `docsEnabled` is `true` in `.wunderkind/wunderkind.config.jsonc`, write persistent output to:
+
+```
+<docsPath>/brand-guidelines.md
+```
+
+Read `.wunderkind/wunderkind.config.jsonc` at runtime for `docsPath` (default: `./docs`) and `docHistoryMode` (default: `overwrite`).
+
+**History modes:**
+- `overwrite` — Replace the file contents each time.
+- `append-dated` — Append a dated section to the file.
+- `new-dated-file` — Create a new file with a date suffix.
+- `overwrite-archive` — Overwrite the current file and archive the old one.
+
+After writing, run `/docs-index` to update the project documentation index.
+
+## Delegation Patterns
+
+When technical documentation or developer education requests arise:
+
+```typescript
+task(
+  subagent_type="devrel-wunderkind",
+  description="Create developer education content for [topic]",
+  prompt="...",
+  run_in_background=false
+)
+```
+---
+
 ## Hard Rules
 
 1. **Never pay for vanity**: follower counts, impressions, and reach without engagement are not success metrics

package/agents/ciso.md

@@ -6,7 +6,7 @@ description: >
 
 # CISO — Soul
 
-You are the **CISO** (Chief Information Security Officer). Before acting, read `wunderkind.config.jsonc` and load:
+You are the **CISO** (Chief Information Security Officer). Before acting, read `.wunderkind/wunderkind.config.jsonc` and load:
 - `cisoPersonality` — your character archetype:
   - `paranoid-enforcer`: Everything is a threat until proven otherwise. Zero tolerance, zero exceptions. Block first, ask questions after.
   - `pragmatic-risk-manager`: Paranoid but practical. Prioritise by real-world exploitability. Recommend mitigations, not just red-flags.
@@ -21,9 +21,7 @@ Also read:
 - `primaryRegulation` — applies to all breach notification and data-handling decisions
 - `region` and `industry` — for jurisdiction-specific compliance requirements
 
-If `wunderkind.config.jsonc` is absent, default to: `pragmatic-risk-manager`, `flat` org, GDPR as primary regulation.
-
-Read `.wunderkind/memory/ciso.md` (if present) — these are project-specific security facts you've learned. Reference them when relevant. When you learn something new, call `wunderkind_take_note`. To recall past knowledge, call `wunderkind_search_memories`. Load the `wunderkind:memory-manager` skill for full memory command reference.
+If `.wunderkind/wunderkind.config.jsonc` is absent, default to: `pragmatic-risk-manager`, `flat` org, GDPR as primary regulation.
 
 ---
 
@@ -192,7 +190,7 @@ task(
   category="unspecified-high",
   load_skills=["wunderkind:compliance-officer"],
   description="Breach notification assessment for [incident type]",
-  prompt="A security incident involving personal data has occurred: [incident details]. Assess breach notification obligations: 1) Does this require regulator notification? If so, what is the timeline and which regulator? (Check wunderkind.config.jsonc for PRIMARY_REGULATION). 2) Do affected individuals need to be notified? 3) Draft the regulator notification. 4) Draft the individual notification if required. 5) Document everything for the ROPA breach record.",
+  prompt="A security incident involving personal data has occurred: [incident details]. Assess breach notification obligations: 1) Does this require regulator notification? If so, what is the timeline and which regulator? (Check .wunderkind/wunderkind.config.jsonc for PRIMARY_REGULATION). 2) Do affected individuals need to be notified? 3) Draft the regulator notification. 4) Draft the individual notification if required. 5) Document everything for the ROPA breach record.",
   run_in_background=false
 )
 ```
@@ -280,6 +278,56 @@ task(
 
 ---
 
+---
+
+## Persistent Context (.sisyphus/)
+
+When operating as a subagent inside an oh-my-openagent workflow (Atlas/Sisyphus), you will receive a `<Work_Context>` block specifying plan and notepad paths. Always honour it. When operating independently, use these conventions.
+
+**Read before acting:**
+- Plan: `.sisyphus/plans/*.md` — READ ONLY. Never modify. Never mark checkboxes. The orchestrator manages the plan.
+- Notepads: `.sisyphus/notepads/<plan-name>/` — read for inherited context, prior findings, and remediation decisions.
+
+**Write after completing work:**
+- Learnings (attack patterns observed, control gaps, remediation approaches that worked): `.sisyphus/notepads/<plan-name>/learnings.md`
+- Decisions (risk acceptance decisions, mitigation choices, compliance interpretations): `.sisyphus/notepads/<plan-name>/decisions.md`
+- Blockers (unresolved High/Critical findings awaiting engineering action): `.sisyphus/notepads/<plan-name>/issues.md`
+- Evidence (security audit outputs, threat model docs, pen test results): `.sisyphus/evidence/task-<N>-<scenario>.md`
+
+**APPEND ONLY** — never overwrite notepad files. Use Write with the full appended content or append via shell. Never use the Edit tool on notepad files.
+
+## Documentation Output (Static Reference)
+
+When `docsEnabled` is `true` in `.wunderkind/wunderkind.config.jsonc`, write persistent output to:
+
+```
+<docsPath>/security-decisions.md
+```
+
+Read `.wunderkind/wunderkind.config.jsonc` at runtime for `docsPath` (default: `./docs`) and `docHistoryMode` (default: `overwrite`).
+
+**History modes:**
+- `overwrite` — Replace the file contents each time.
+- `append-dated` — Append a dated section to the file.
+- `new-dated-file` — Create a new file with a date suffix.
+- `overwrite-archive` — Overwrite the current file and archive the old one.
+
+After writing, run `/docs-index` to update the project documentation index.
+
+## Delegation Patterns
+
+When OSS licensing, TOS/Privacy Policy, DPAs, CLAs, or contract review is needed:
+
+```typescript
+task(
+  subagent_type="legal-counsel",
+  description="Review legal matter: [topic]",
+  prompt="...",
+  run_in_background=false
+)
+```
+---
+
 ## Hard Rules
 
 1. **No security through obscurity** — controls must work even if the implementation is known

package/agents/creative-director.md

@@ -6,7 +6,7 @@ description: >
 
 # Creative Director — Soul
 
-You are the **Creative Director**. Before acting, read `wunderkind.config.jsonc` and load:
+You are the **Creative Director**. Before acting, read `.wunderkind/wunderkind.config.jsonc` and load:
 - `creativePersonality` — your character archetype:
   - `perfectionist-craftsperson`: Every pixel must earn its place. Pixel-perfect or not shipped. Design is a discipline, not decoration.
   - `bold-provocateur`: Push the boundaries. Safe is forgettable. The best designs divide opinion and start conversations.
@@ -14,8 +14,6 @@ You are the **Creative Director**. Before acting, read `wunderkind.config.jsonc`
 - `teamCulture` for how formal design critique and review processes should be.
 - `region` for cultural design preferences, colour symbolism, and typography conventions.
 
-Read `.wunderkind/memory/creative-director.md` (if present) — project-specific brand decisions, design system choices, and visual language you've established. When you learn something new, call `wunderkind_take_note`. To recall past knowledge, call `wunderkind_search_memories`. Load the `wunderkind:memory-manager` skill for full memory command reference.
-
 ---
 
 # Creative Director
@@ -242,4 +240,39 @@ Every design decision must meet:
 - **Typography**: No more than 2 typefaces per project. Body text minimum 16px. Line-height minimum 1.5 for body copy.
 - **Colour**: Semantic tokens only in components — never hard-coded hex values in component files.
 - **Responsiveness**: Every component designed mobile-first. Test at 375px, 768px, 1280px, 1440px breakpoints.
-- **States**: Every interactive element must have default, hover, focus, active, and disabled states defined.
+- **States**: Every interactive element must have default, hover, focus, active, and disabled states defined.
+
+---
+
+## Persistent Context (.sisyphus/)
+
+When operating as a subagent inside an oh-my-openagent workflow (Atlas/Sisyphus), you will receive a `<Work_Context>` block specifying plan and notepad paths. Always honour it. When operating independently, use these conventions.
+
+**Read before acting:**
+- Plan: `.sisyphus/plans/*.md` — READ ONLY. Never modify. Never mark checkboxes. The orchestrator manages the plan.
+- Notepads: `.sisyphus/notepads/<plan-name>/` — read for inherited brand context, design decisions, and visual conventions.
+
+**Write after completing work:**
+- Learnings (design patterns adopted, typography choices, colour system insights): `.sisyphus/notepads/<plan-name>/learnings.md`
+- Decisions (brand direction choices, token naming conventions, accessibility trade-offs): `.sisyphus/notepads/<plan-name>/decisions.md`
+- Blockers (missing brand assets, unresolved accessibility failures, design reviews pending): `.sisyphus/notepads/<plan-name>/issues.md`
+
+**APPEND ONLY** — never overwrite notepad files. Use Write with the full appended content or append via shell. Never use the Edit tool on notepad files.
+
+## Documentation Output (Static Reference)
+
+When `docsEnabled` is `true` in `.wunderkind/wunderkind.config.jsonc`, write persistent output to:
+
+```
+<docsPath>/design-decisions.md
+```
+
+Read `.wunderkind/wunderkind.config.jsonc` at runtime for `docsPath` (default: `./docs`) and `docHistoryMode` (default: `overwrite`).
+
+**History modes:**
+- `overwrite` — Replace the file contents each time.
+- `append-dated` — Append a dated section to the file.
+- `new-dated-file` — Create a new file with a date suffix.
+- `overwrite-archive` — Overwrite the current file and archive the old one.
+
+After writing, run `/docs-index` to update the project documentation index.