@fro.bot/systematic 1.23.2 → 2.0.0

package/README.md

@@ -15,7 +15,7 @@
 
 <br>
 
-**[Overview](#overview)** · **[Quick Start](#quick-start)** · **[Skills](#skills)** · **[Agents](#agents)** · **[Commands](#commands)** · **[CLI](#cli)** · **[Configuration](#configuration)** · **[Development](#development)**
+**[Overview](#overview)** · **[Quick Start](#quick-start)** · **[Skills](#skills)** · **[Agents](#agents)** · **[CLI](#cli)** · **[Configuration](#configuration)** · **[Development](#development)**
 
 </div>
 
@@ -38,11 +38,11 @@ Most AI coding assistants respond to requests without structure or methodology.
 
 ### Key Features
 
-- **Structured Skills** — Pre-built workflows for brainstorming, planning, and code review
-- **Specialized Agents** — Purpose-built subagents for architecture, security, and performance
+- **Structured Skills** — Pre-built workflows for brainstorming, planning, code review, and more
+- **Specialized Agents** — Purpose-built subagents for architecture, security, performance, and research
 - **Zero Configuration** — Works immediately after installation via config hooks
-- **Extensible** — Add project-specific skills and commands alongside bundled ones
-- **Batteries Included** — 11 skills, 24 agents, and 9 commands ship with the npm package
+- **Extensible** — Add project-specific skills and agents alongside bundled ones
+- **Batteries Included** — 48 skills and 29 agents ship with the npm package
 - **CLI Tooling** — Inspect, list, and convert assets from the command line
 
 ## Quick Start
@@ -62,7 +62,7 @@ Install the plugin by adding it to your OpenCode configuration (`~/.config/openc
 }
 ```
 
-Restart OpenCode to activate the plugin. All bundled skills, agents, and commands will be available immediately.
+Restart OpenCode to activate the plugin. All bundled skills and agents will be available immediately.
 
 > [!NOTE]
 > Systematic uses OpenCode's `config` hook to automatically register all bundled content. No manual file copying required.
@@ -80,9 +80,8 @@ ocx add systematic/brainstorming
 ocx add systematic/agent-architecture-strategist
 
 # Or install bundles
-ocx add systematic/skills     # All 11 skills
-ocx add systematic/agents     # All 24 agents
-ocx add systematic/commands   # All 9 commands
+ocx add systematic/skills     # All 48 skills
+ocx add systematic/agents     # All 29 agents
 
 # Or use a profile (requires --global registry)
 ocx registry add https://fro.bot/systematic --name systematic --global
@@ -110,21 +109,52 @@ Once verified, explore these guides to master the Systematic workflow:
 
 ## Skills
 
-Skills are structured workflows that guide the AI through systematic engineering processes. They're loaded via the `systematic_skill` tool.
+Skills are structured workflows that guide the AI through systematic engineering processes. They're loaded via the `systematic_skill` tool and invocable as slash commands (e.g., `/ce:brainstorm`).
+
+### Core Workflows
+
+The Compound Engineering loop — the heart of Systematic:
+
+| Skill | Description |
+|-------|-------------|
+| `ce:brainstorm` | Explore requirements through collaborative dialogue before planning |
+| `ce:plan` | Transform feature descriptions into structured implementation plans |
+| `ce:review` | Perform exhaustive code reviews using multi-agent analysis |
+| `ce:work` | Execute work plans efficiently while maintaining quality |
+| `ce:compound` | Document recently solved problems to compound team knowledge |
+| `ce:ideate` | Generate and critically evaluate grounded improvement ideas |
+| `ce:compound-refresh` | Refresh stale learnings and pattern docs against current codebase |
+
+### Development Tools
 
 | Skill | Description |
 |-------|-------------|
 | `using-systematic` | Bootstrap skill — teaches the AI how to discover and use other skills |
-| `brainstorming` | Collaborative design workflow for exploring ideas before planning |
 | `agent-browser` | Browser automation using Vercel's agent-browser CLI |
 | `agent-native-architecture` | Design systems where AI agents are first-class citizens |
+| `create-agent-skill` | Expert guidance for writing and refining OpenCode skills |
 | `compound-docs` | Capture solved problems as categorized documentation |
-| `create-agent-skills` | Expert guidance for writing and refining skills |
-| `document-review` | Refine brainstorm or plan documents before proceeding to the next workflow step |
+| `document-review` | Refine requirements or plan documents before proceeding |
+| `deepen-plan` | Enhance a plan with parallel research for each section |
 | `file-todos` | File-based todo tracking with status and dependency management |
-| `frontend-design` | Create distinctive, production-grade frontend interfaces with high design quality |
+| `frontend-design` | Create distinctive, production-grade frontend interfaces |
 | `git-worktree` | Manage git worktrees for isolated parallel development |
-| `orchestrating-swarms` | Coordinate multi-agent swarms, parallel reviews, and pipeline workflows |
+| `orchestrating-swarms` | Coordinate multi-agent swarms and pipeline workflows |
+| `lfg` | Full autonomous engineering workflow — plan, then execute |
+
+### Specialized Skills
+
+| Skill | Description |
+|-------|-------------|
+| `dhh-rails-style` | Write Ruby and Rails code in DHH's distinctive 37signals style |
+| `andrew-kane-gem-writer` | Write Ruby gems following Andrew Kane's proven patterns |
+| `dspy-ruby` | Build type-safe LLM applications with DSPy.rb |
+| `every-style-editor` | Review and edit copy for style guide compliance |
+| `gemini-imagegen` | Generate and edit images using the Gemini API |
+| `proof` | Create, edit, and share markdown documents via Proof |
+| `rclone` | Upload, sync, and manage files across cloud storage providers |
+
+> **[View all 48 skills →](https://fro.bot/systematic/reference/skills/)**
 
 ### How Skills Work
 
@@ -151,9 +181,15 @@ Agents are specialized subagents with pre-configured prompts and expertise. They
 
 | Agent | Purpose |
 |-------|---------|
-| `design-implementation-reviewer` | Verify UI implementations match Figma design specifications |
-| `design-iterator` | Systematic UI/UX refinement through iterative screenshots and improvements |
-| `figma-design-sync` | Detect and fix visual differences between web implementation and Figma designs |
+| `design-implementation-reviewer` | Visually compare live UI against Figma designs and report discrepancies |
+| `design-iterator` | Iteratively refine UI design through screenshot-analyze-improve cycles |
+| `figma-design-sync` | Detect and fix visual differences between web implementation and Figma |
+
+### Docs Agents
+
+| Agent | Purpose |
+|-------|---------|
+| `ankane-readme-writer` | Create or update README files following Ankane-style template for Ruby gems |
 
 ### Research Agents
 
@@ -161,7 +197,8 @@ Agents are specialized subagents with pre-configured prompts and expertise. They
 |-------|---------|
 | `best-practices-researcher` | Research external best practices, documentation, and examples for any technology |
 | `framework-docs-researcher` | Gather framework documentation and best practices |
-| `git-history-analyzer` | Archaeological analysis of git history to trace code evolution and understand patterns |
+| `git-history-analyzer` | Archaeological analysis of git history to trace code evolution and patterns |
+| `issue-intelligence-analyst` | Analyze GitHub issues to surface recurring themes, pain patterns, and severity trends |
 | `learnings-researcher` | Search past solutions in docs/solutions/ to surface institutional knowledge |
 | `repo-research-analyst` | Research repository structure, documentation, conventions, and implementation patterns |
 
@@ -176,10 +213,13 @@ Agents are specialized subagents with pre-configured prompts and expertise. They
 | `data-migration-expert` | Validate data migrations, backfills, and production data transformations |
 | `deployment-verification-agent` | Produce Go/No-Go deployment checklists with verification queries and rollback procedures |
 | `dhh-rails-reviewer` | Brutally honest Rails code review from DHH's perspective |
-| `kieran-rails-reviewer` | High quality bar Rails code review for conventions, clarity, and maintainability |
+| `julik-frontend-races-reviewer` | Review JavaScript and Stimulus code for race conditions and timing issues |
+| `kieran-python-reviewer` | High quality bar Python review for Pythonic patterns, type safety, and maintainability |
+| `kieran-rails-reviewer` | High quality bar Rails review for conventions, clarity, and maintainability |
 | `kieran-typescript-reviewer` | High quality bar TypeScript review for type safety, modern patterns, and maintainability |
 | `pattern-recognition-specialist` | Detect design patterns, anti-patterns, and code smells |
 | `performance-oracle` | Performance analysis, bottleneck identification, scalability |
+| `schema-drift-detector` | Detect unrelated schema.rb changes by cross-referencing against included migrations |
 | `security-sentinel` | Security audits, vulnerability assessment, OWASP compliance |
 
 ### Workflow Agents
@@ -199,35 +239,12 @@ Agents are invoked via OpenCode's `@mention` syntax or `task`:
 @architecture-strategist Review the authentication refactoring in this PR
 ```
 
-Or programmatically in skills/commands:
+Or programmatically in skills:
 
 ```
 task(subagent_type="architecture-strategist", prompt="Review...")
 ```
 
-## Commands
-
-Commands are slash-invokable shortcuts that trigger workflows or actions.
-
-### Workflow Commands
-
-| Command | Description |
-|---------|-------------|
-| `/workflows:brainstorm` | Explore requirements through collaborative dialogue |
-| `/workflows:plan` | Create detailed implementation plans |
-| `/workflows:review` | Run code review with specialized agents |
-| `/workflows:work` | Execute planned work systematically |
-| `/workflows:compound` | Document recently solved problems to build team knowledge |
-
-### Utility Commands
-
-| Command | Description |
-|---------|-------------|
-| `/systematic:lfg` | Full autonomous engineering workflow — plan, then execute |
-| `/systematic:create-agent-skill` | Create a new skill with expert guidance |
-| `/systematic:deepen-plan` | Enhance a plan with parallel research for each section |
-| `/systematic:agent-native-audit` | Audit code for agent-native architecture patterns |
-
 ## CLI
 
 Systematic includes a CLI for inspecting and converting assets outside of OpenCode.
@@ -280,7 +297,6 @@ Configuration is loaded from multiple locations and merged (later sources overri
 {
   "disabled_skills": ["git-worktree"],
   "disabled_agents": [],
-  "disabled_commands": [],
   "bootstrap": {
     "enabled": true
   }
@@ -291,23 +307,20 @@ Configuration is loaded from multiple locations and merged (later sources overri
 |--------|------|---------|-------------|
 | `disabled_skills` | `string[]` | `[]` | Skills to exclude from registration |
 | `disabled_agents` | `string[]` | `[]` | Agents to exclude from registration |
-| `disabled_commands` | `string[]` | `[]` | Commands to exclude from registration |
 | `bootstrap.enabled` | `boolean` | `true` | Inject the `using-systematic` guide into system prompts |
 | `bootstrap.file` | `string` | — | Custom bootstrap file path (overrides default) |
 
 ### Project-Specific Content
 
-Add your own skills, agents, and commands alongside bundled ones:
+Add your own skills and agents alongside bundled ones:
 
 ```
 .opencode/
 ├── skills/
 │   └── my-skill/
 │       └── SKILL.md
-├── agents/
-│   └── my-agent.md
-└── commands/
-    └── my-command.md
+└── agents/
+    └── my-agent.md
 ```
 
 Project-level content takes precedence over bundled content with the same name.
@@ -333,7 +346,7 @@ flowchart TB
     A --> C[tool hook]
     A --> D[system.transform hook]
 
-    B --> E[Merge bundled agents/commands/skills into OpenCode config]
+    B --> E[Merge bundled agents and skills into OpenCode config]
     C --> F[Register systematic_skill tool]
     D --> G[Inject bootstrap prompt into every conversation]
 
@@ -346,11 +359,11 @@ flowchart TB
     style G fill:#0f0f23,stroke:#F5A623,color:#B2F5EA
 ```
 
-1. **`config` hook** — Discovers and merges bundled skills, agents, and commands into your OpenCode configuration. Existing config takes precedence over bundled content. Skills are registered as commands with the `systematic:` prefix.
+1. **`config` hook** — Discovers and merges bundled skills and agents into your OpenCode configuration. Existing config takes precedence over bundled content. Skills are registered as slash commands with the `systematic:` prefix.
 2. **`tool` hook** — Registers the `systematic_skill` tool, which lists available skills in its XML description and loads skill content on demand.
 3. **`system.transform` hook** — Injects the "Using Systematic" bootstrap guide into system prompts, teaching the AI how to discover and invoke skills.
 
-This architecture ensures skills, agents, and commands are available immediately without manual setup.
+This architecture ensures skills and agents are available immediately without manual setup.
 
 ## Development
 
@@ -398,18 +411,19 @@ systematic/
 │       ├── skill-loader.ts   # Skill content loading + formatting
 │       ├── skills.ts         # Skill discovery
 │       ├── agents.ts         # Agent discovery
-│       ├── commands.ts       # Command discovery
+│       ├── commands.ts       # Command discovery (backward compat)
 │       ├── frontmatter.ts    # YAML frontmatter parsing
 │       ├── manifest.ts       # Upstream sync manifest tracking
 │       ├── validation.ts     # Agent config validation + type guards
 │       └── walk-dir.ts       # Recursive directory walker
-├── skills/                   # 11 bundled skills (SKILL.md files)
-├── agents/                   # 24 bundled agents (4 categories)
-├── commands/                 # 9 bundled commands (with workflows/ subdir)
+├── skills/                   # 48 bundled skills (SKILL.md files)
+├── agents/                   # 29 bundled agents (5 categories)
 ├── docs/                     # Starlight documentation site
+├── registry/                 # OCX registry config + profiles
+├── scripts/                  # Build and utility scripts
 ├── tests/
-│   ├── unit/                 # Unit tests
-│   └── integration/          # Integration tests
+│   ├── unit/                 # 13 unit test files
+│   └── integration/          # 2 integration test files
 └── dist/                     # Build output
 ```
 
@@ -435,7 +449,7 @@ See [`AGENTS.md`](./AGENTS.md) for detailed development guidelines, code style c
 
 ## Converting from Claude Code
 
-Migrating skills, agents, or commands from CEP or other Claude Code-format sources to Systematic? See the [Conversion Guide](https://fro.bot/systematic/guides/conversion-guide/) for field mappings and examples. Also available as [local Markdown](./docs/CONVERSION-GUIDE.md).
+Migrating skills or agents from CEP or other Claude Code-format sources to Systematic? See the [Conversion Guide](https://fro.bot/systematic/guides/conversion-guide/) for field mappings and examples.
 
 ## References
 

package/agents/research/best-practices-researcher.md

@@ -32,8 +32,8 @@ Before going online, check if curated knowledge already exists in skills:
 
 1. **Discover Available Skills**:
    - Use the platform's native file-search/glob capability to find `SKILL.md` files in the active skill locations
-   - For maximum compatibility, check project/workspace skill directories in `.claude/skills/**/SKILL.md`, `.codex/skills/**/SKILL.md`, and `.agents/skills/**/SKILL.md`
-   - Also check user/home skill directories in `~/.claude/skills/**/SKILL.md`, `~/.codex/skills/**/SKILL.md`, and `~/.agents/skills/**/SKILL.md`
+   - For maximum compatibility, check project/workspace skill directories in `.opencode/skills/**/SKILL.md`, `.codex/skills/**/SKILL.md`, and `.agents/skills/**/SKILL.md`
+   - Also check user/home skill directories in `~/.config/opencode/skills/**/SKILL.md`, `~/.codex/skills/**/SKILL.md`, and `~/.agents/skills/**/SKILL.md`
    - In Codex environments, `.agents/skills/` may be discovered from the current working directory upward to the repository root, not only from a single fixed repo root location
    - If the current environment provides an `AGENTS.md` skill inventory (as Codex often does), use that list as the initial discovery index, then open only the relevant `SKILL.md` files
    - Use the platform's native file-read capability to examine skill descriptions and understand what each covers
@@ -130,4 +130,3 @@ If you encounter conflicting advice, present the different viewpoints and explai
 **Tool Selection:** Use native file-search/glob (e.g., `Glob`), content-search (e.g., `Grep`), and file-read (e.g., `Read`) tools for repository exploration. Only use shell for commands with no native equivalent (e.g., `bundle show`), one command at a time.
 
 Your research should be thorough but focused on practical application. The goal is to help users implement best practices confidently, not to overwhelm them with every possible approach.
-

package/agents/research/issue-intelligence-analyst.md

@@ -217,8 +217,8 @@ Every theme MUST include ALL of the following fields. Do not skip fields, merge
 - **Always use `--jq` for field extraction and filtering** from `gh` JSON output (e.g., `gh issue list --json title --jq '.[].title'`, `gh issue list --json stateReason --jq '[.[] | select(.stateReason == "COMPLETED")]'`). The `gh` CLI has full jq support built in.
 - **Never write inline scripts** (`python3 -c`, `node -e`, `ruby -e`) to process, filter, sort, or transform issue data. Reason over the data directly after reading it — you are an LLM, you can filter and cluster in context without running code.
 - **Never pipe** `gh` output through any command (`| python3`, `| jq`, `| grep`, `| sort`). Use `--jq` flags instead, or read the output and reason over it.
-- Use native file-search/glob tools (e.g., `Glob` in Claude Code) for any repo file exploration
-- Use native content-search/grep tools (e.g., `Grep` in Claude Code) for searching file contents
+- Use native file-search/glob tools (e.g., `Glob` in OpenCode) for any repo file exploration
+- Use native content-search/grep tools (e.g., `Grep` in OpenCode) for searching file contents
 - Do not use shell commands for tasks that have native tool equivalents (no `find`, `cat`, `rg` through shell)
 
 ## Integration Points
@@ -229,4 +229,3 @@ This agent is designed to be invoked by:
 - Other skills or workflows — any context where understanding issue patterns is valuable
 
 The output is self-contained and not coupled to any specific caller's context.
-

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fro.bot/systematic",
-  "version": "1.23.2",
+  "version": "2.0.0",
   "description": "Structured engineering workflows for OpenCode",
   "type": "module",
   "homepage": "https://fro.bot/systematic",
@@ -17,8 +17,7 @@
   "files": [
     "dist",
     "skills",
-    "agents",
-    "commands"
+    "agents"
   ],
   "workspaces": [
     "docs"

package/skills/ce-brainstorm/SKILL.md

@@ -8,7 +8,7 @@ argument-hint: '[feature idea or problem to explore]'
 
 **Note: The current year is 2026.** Use this when dating requirements documents.
 
-Brainstorming helps answer **WHAT** to build through collaborative dialogue. It precedes `/systematic:ce-plan`, which answers **HOW** to build it.
+Brainstorming helps answer **WHAT** to build through collaborative dialogue. It precedes `/ce:plan`, which answers **HOW** to build it.
 
 The durable output of this workflow is a **requirements document**. In other workflows this might be called a lightweight PRD or feature brief. In compound engineering, keep the workflow name `brainstorm`, but make the written artifact strong enough that planning does not need to invent product behavior, scope boundaries, or success criteria.
 
@@ -28,7 +28,7 @@ This skill does not implement code. It explores, clarifies, and documents decisi
 1. **Ask one question at a time** - Do not batch several unrelated questions into one message.
 2. **Prefer single-select multiple choice** - Use single-select when choosing one direction, one priority, or one next step.
 3. **Use multi-select rarely and intentionally** - Use it only for compatible sets such as goals, constraints, non-goals, or success criteria that can all coexist. If prioritization matters, follow up by asking which selected item is primary.
-4. **Use the platform's question tool when available** - When asking the user a question, prefer the platform's blocking question tool if one exists (`AskUserQuestion` in OpenCode, `request_user_input` in Codex, `ask_user` in Gemini). Otherwise, present numbered options in chat and wait for the user's reply before proceeding.
+4. **Use the platform's question tool when available** - When asking the user a question, prefer the platform's blocking question tool if one exists (`question` in OpenCode, `request_user_input` in Codex, `ask_user` in Gemini). Otherwise, present numbered options in chat and wait for the user's reply before proceeding.
 
 ## Output Guidance
 
@@ -83,7 +83,7 @@ Scan the repo before substantive brainstorming. Match depth to scope:
 
 **Standard and Deep** — Two passes:
 
-*Constraint Check* — Check project instruction files (`AGENTS.md`, `CLAUDE.md`) for workflow, product, or scope constraints that affect the brainstorm. If these add nothing, move on.
+*Constraint Check* — Check project instruction files (`AGENTS.md`) for workflow, product, or scope constraints that affect the brainstorm. If these add nothing, move on.
 
 *Topic Scan* — Search for relevant terms. Read the most relevant existing artifact if one exists (brainstorm, plan, spec, skill, feature doc). Skim adjacent examples covering similar behavior.
 
@@ -211,8 +211,8 @@ topic: <kebab-case-topic>
 - [Affects R2][Needs research] [Question that likely requires research during planning]
 
 ## Next Steps
-[If `Resolve Before Planning` is empty: `→ /systematic:ce-plan` for structured implementation planning]
-[If `Resolve Before Planning` is not empty: `→ Resume /systematic:ce-brainstorm` to resolve blocking questions before planning]
+[If `Resolve Before Planning` is empty: `→ /ce:plan` for structured implementation planning]
+[If `Resolve Before Planning` is not empty: `→ Resume /ce:brainstorm` to resolve blocking questions before planning]
 ```
 
 For **Standard** and **Deep** brainstorms, a requirements document is usually warranted.
@@ -260,7 +260,7 @@ If `Resolve Before Planning` contains any items:
 **Question when blocking questions remain and user wants to pause:** "Brainstorm paused. Planning is blocked until the remaining questions are resolved. What would you like to do next?"
 
 Present only the options that apply:
-- **Proceed to planning (Recommended)** - Run `/systematic:ce-plan` for structured implementation planning
+- **Proceed to planning (Recommended)** - Run `/ce:plan` for structured implementation planning
 - **Proceed directly to work** - Only offer this when scope is lightweight, success criteria are clear, scope boundaries are clear, and no meaningful technical or research questions remain
 - **Review and refine** - Offer this only when a requirements document exists and can be improved through structured review
 - **Ask more questions** - Continue clarifying scope, preferences, or edge cases
@@ -273,11 +273,11 @@ If the direct-to-work gate is not satisfied, omit that option entirely.
 
 **If user selects "Proceed to planning (Recommended)":**
 
-Immediately run `/systematic:ce-plan` in the current session. Pass the requirements document path when one exists; otherwise pass a concise summary of the finalized brainstorm decisions. Do not print the closing summary first.
+Immediately run `/ce:plan` in the current session. Pass the requirements document path when one exists; otherwise pass a concise summary of the finalized brainstorm decisions. Do not print the closing summary first.
 
 **If user selects "Proceed directly to work":**
 
-Immediately run `/systematic:ce-work` in the current session using the finalized brainstorm output as context. If a compact requirements document exists, pass its path. Do not print the closing summary first.
+Immediately run `/ce:work` in the current session using the finalized brainstorm output as context. If a compact requirements document exists, pass its path. Do not print the closing summary first.
 
 **If user selects "Share to Proof":**
 
@@ -317,7 +317,7 @@ Key decisions:
 - [Decision 1]
 - [Decision 2]
 
-Recommended next step: `/systematic:ce-plan`
+Recommended next step: `/ce:plan`
 ```
 
 If the user pauses with `Resolve Before Planning` still populated, display:
@@ -331,6 +331,5 @@ Planning is blocked by:
 - [Blocking question 1]
 - [Blocking question 2]
 
-Resume with `/systematic:ce-brainstorm` when ready to resolve these before planning.
+Resume with `/ce:brainstorm` when ready to resolve these before planning.
 ```
-

package/skills/ce-compound/SKILL.md

@@ -17,13 +17,13 @@ Captures problem solutions while context is fresh, creating structured documenta
 ## Usage
 
 ```bash
-/systematic:ce-compound                    # Document the most recent fix
-/systematic:ce-compound [brief context]    # Provide additional context hint
+/ce:compound                    # Document the most recent fix
+/ce:compound [brief context]    # Provide additional context hint
 ```
 
 ## Execution Strategy
 
-**Always run full mode by default.** Proceed directly to Phase 1 unless the user explicitly requests compact-safe mode (e.g., `/systematic:ce-compound --compact` or "use compact mode").
+**Always run full mode by default.** Proceed directly to Phase 1 unless the user explicitly requests compact-safe mode (e.g., `/ce:compound --compact` or "use compact mode").
 
 Compact-safe mode exists as a lightweight alternative — see the **Compact-Safe Mode** section below. It's there if the user wants it, not something to push.
 
@@ -128,10 +128,10 @@ When invoking or recommending `ce:compound-refresh`, be explicit about the argum
 
 Examples:
 
-- `/systematic:ce-compound-refresh plugin-versioning-requirements`
-- `/systematic:ce-compound-refresh payments`
-- `/systematic:ce-compound-refresh performance-issues`
-- `/systematic:ce-compound-refresh critical-patterns`
+- `/ce:compound-refresh plugin-versioning-requirements`
+- `/ce:compound-refresh payments`
+- `/ce:compound-refresh performance-issues`
+- `/ce:compound-refresh critical-patterns`
 
 A single scope hint may still expand to multiple related docs when the change is cross-cutting within one domain, category, or pattern area.
 
@@ -299,7 +299,7 @@ Build → Test → Find Issue → Research → Improve → Document → Validate
 
 <auto_invoke> <trigger_phrases> - "that worked" - "it's fixed" - "working now" - "problem solved" </trigger_phrases>
 
-<manual_override> Use /systematic:ce-compound [context] to document immediately without waiting for auto-detection. </manual_override> </auto_invoke>
+<manual_override> Use /ce:compound [context] to document immediately without waiting for auto-detection. </manual_override> </auto_invoke>
 
 ## Routes To
 
@@ -327,11 +327,11 @@ Based on problem type, these agents can enhance documentation:
 
 ### When to Invoke
 - **Auto-triggered** (optional): Agents can run post-documentation for enhancement
-- **Manual trigger**: User can invoke agents after /systematic:ce-compound completes for deeper review
-- **Customize agents**: Edit `compound-engineering.local.md` or invoke the `setup` skill to configure which review agents are used across all workflows
+- **Manual trigger**: User can invoke agents after /ce:compound completes for deeper review
+- **Customize agents**: Edit `systematic.local.md` or invoke the `setup` skill to configure which review agents are used across all workflows
 
 ## Related Commands
 
 - `/research [topic]` - Deep investigation (searches docs/solutions/ for patterns)
-- `/systematic:ce-plan` - Planning workflow (references documented solutions)
+- `/ce:plan` - Planning workflow (references documented solutions)
 

package/skills/ce-compound-refresh/SKILL.md

@@ -33,7 +33,7 @@ Check if `$ARGUMENTS` contains `mode:autonomous`. If present, strip it from argu
 
 Follow the same interaction style as `ce:brainstorm`:
 
-- Ask questions **one at a time** — use the platform's blocking question tool when available (`AskUserQuestion` in OpenCode, `request_user_input` in Codex, `ask_user` in Gemini). Otherwise, present numbered options in plain text and wait for the user's reply before continuing
+- Ask questions **one at a time** — use the platform's blocking question tool when available (`question` in OpenCode, `request_user_input` in Codex, `ask_user` in Gemini). Otherwise, present numbered options in plain text and wait for the user's reply before continuing
 - Prefer **multiple choice** when natural options exist
 - Start with **scope and intent**, then narrow only when needed
 - Do **not** ask the user to make decisions before you have evidence
@@ -309,7 +309,7 @@ Do **not** ask questions about whether code changes were intentional, whether th
 
 #### Question Style
 
-Always present choices using the platform's blocking question tool when available (`AskUserQuestion` in OpenCode, `request_user_input` in Codex, `ask_user` in Gemini). Otherwise, present numbered options in plain text and wait for the user's reply before proceeding.
+Always present choices using the platform's blocking question tool when available (`question` in OpenCode, `request_user_input` in Codex, `ask_user` in Gemini). Otherwise, present numbered options in plain text and wait for the user's reply before proceeding.
 
 Question rules:
 

package/skills/ce-ideate/SKILL.md

@@ -18,7 +18,7 @@ This workflow produces a ranked ideation artifact in `docs/ideation/`. It does *
 
 ## Interaction Method
 
-Use the platform's blocking question tool when available (`AskUserQuestion` in OpenCode, `request_user_input` in Codex, `ask_user` in Gemini). Otherwise, present numbered options in chat and wait for the user's reply before proceeding.
+Use the platform's blocking question tool when available (`question` in OpenCode, `request_user_input` in Codex, `ask_user` in Gemini). Otherwise, present numbered options in chat and wait for the user's reply before proceeding.
 
 Ask one question at a time. Prefer concise single-select choices when natural options exist.
 
@@ -29,7 +29,7 @@ Ask one question at a time. Prefer concise single-select choices when natural op
 Interpret any provided argument as optional context. It may be:
 
 - a concept such as `DX improvements`
-- a path such as `plugins/compound-engineering/skills/`
+- a path such as `plugins/systematic/skills/`
 - a constraint such as `low-complexity quick wins`
 - a volume hint such as `top 3`, `100 ideas`, or `raise the bar`
 
@@ -103,7 +103,7 @@ Run agents in parallel in the **foreground** (do not use background dispatch —
 
 1. **Quick context scan** — dispatch a general-purpose sub-agent with this prompt:
 
-   > Read the project's AGENTS.md (or AGENTS.md / README.md if AGENTS.md is absent), then discover the top-level directory layout using the native file-search/glob tool (e.g., `Glob` with pattern `*` or `*/*` in OpenCode). Return a concise summary (under 30 lines) covering:
+> Read the project's AGENTS.md (or README.md if AGENTS.md is absent), then discover the top-level directory layout using the native file-search/glob tool (e.g., `Glob` with pattern `*` or `*/*` in OpenCode). Return a concise summary (under 30 lines) covering:
    > - project shape (language, framework, top-level directory layout)
    > - notable patterns or conventions
    > - obvious pain points or gaps
@@ -368,4 +368,3 @@ Before finishing, check:
 - survivors are materially better than a naive "give me ideas" list
 - the artifact was written before any handoff, sharing, or session end
 - acting on an idea routes to `ce:brainstorm`, not directly to implementation
-

package/skills/ce-plan/SKILL.md

@@ -49,7 +49,7 @@ ls -la docs/brainstorms/*-requirements.md 2>/dev/null | head -10
 5. Use source document content as the **primary input** to research and planning phases
 6. **Critical: The source document is the origin document.** Throughout the plan, reference specific decisions with `(see origin: <source-path>)` when carrying forward conclusions. Do not paraphrase decisions in a way that loses their original context — link back to the source.
 7. **Do not omit source content** — if the source document discussed it, the plan must address it (even if briefly). Scan each section before finalizing the plan to verify nothing was dropped.
-8. **If `Resolve Before Planning` contains any items, stop.** Do not proceed with planning. Tell the user planning is blocked by unanswered brainstorm questions and direct them to resume `/systematic:ce-brainstorm` or answer those questions first.
+8. **If `Resolve Before Planning` contains any items, stop.** Do not proceed with planning. Tell the user planning is blocked by unanswered brainstorm questions and direct them to resume `/ce:brainstorm` or answer those questions first.
 
 **If multiple source documents could match:**
 Use **question tool** to ask which source document to use, or whether to proceed without one.
@@ -582,8 +582,8 @@ After writing the plan file, use the **question tool** to present these options:
 2. **Run `/deepen-plan`** - Enhance each section with parallel research agents (best practices, performance, UI)
 3. **Review and refine** - Improve the document through structured self-review
 4. **Share to Proof** - Upload to Proof for collaborative review and sharing
-5. **Start `/systematic:ce-work`** - Begin implementing this plan locally
-6. **Start `/systematic:ce-work` on remote** - Begin implementing in OpenCode on the web (use `&` to run in background)
+5. **Start `/ce:work`** - Begin implementing this plan locally
+6. **Start `/ce:work` on remote** - Begin implementing in OpenCode on the web (use `&` to run in background)
 7. **Create Issue** - Create issue in project tracker (GitHub/Linear)
 
 Based on selection:
@@ -600,14 +600,14 @@ Based on selection:
   PROOF_URL=$(echo "$RESPONSE" | jq -r '.tokenUrl')
   ```
   Display: `View & collaborate in Proof: <PROOF_URL>` — skip silently if curl fails. Then return to options.
-- **`/systematic:ce-work`** → Call the /systematic:ce-work command with the plan file path
-- **`/systematic:ce-work` on remote** → Run `/systematic:ce-work docs/plans/<plan_filename>.md &` to start work in background for OpenCode web
+- **`/ce:work`** → Call the /ce:work command with the plan file path
+- **`/ce:work` on remote** → Run `/ce:work docs/plans/<plan_filename>.md &` to start work in background for OpenCode web
 - **Create Issue** → See "Issue Creation" section below
 - **Other** (automatically provided) → Accept free text for rework or specific changes
 
-**Note:** If running `/systematic:ce-plan` with ultrathink enabled, automatically run `/deepen-plan` after plan creation for maximum depth and grounding.
+**Note:** If running `/ce:plan` with ultrathink enabled, automatically run `/deepen-plan` after plan creation for maximum depth and grounding.
 
-Loop back to options after Simplify or Other changes until user selects `/systematic:ce-work` or another action.
+Loop back to options after Simplify or Other changes until user selects `/ce:work` or another action.
 
 ## Issue Creation
 
@@ -637,7 +637,7 @@ When user selects "Create Issue", detect their project tracker from AGENTS.md:
 
 5. **After creation:**
    - Display the issue URL
-   - Ask if they want to proceed to `/systematic:ce-work`
+   - Ask if they want to proceed to `/ce:work`
 
 NEVER CODE! Just research and write the plan.
 

package/skills/ce-plan-beta/SKILL.md

@@ -15,7 +15,7 @@ This workflow produces a durable implementation plan. It does **not** implement
 
 ## Interaction Method
 
-Use the platform's question tool when available. When asking the user a question, prefer the platform's blocking question tool if one exists (`AskUserQuestion` in OpenCode, `request_user_input` in Codex, `ask_user` in Gemini). Otherwise, present numbered options in chat and wait for the user's reply before proceeding.
+Use the platform's question tool when available. When asking the user a question, prefer the platform's blocking question tool if one exists (`question` in OpenCode, `request_user_input` in Codex, `ask_user` in Gemini). Otherwise, present numbered options in chat and wait for the user's reply before proceeding.
 
 Ask one question at a time. Prefer a concise single-select choice when natural options exist.
 
@@ -150,7 +150,7 @@ Run these agents in parallel:
 Collect:
 - Existing patterns and conventions to follow
 - Relevant files, modules, and tests
-- AGENTS.md or AGENTS.md guidance that materially affects the plan
+- AGENTS.md guidance that materially affects the plan
 - Institutional learnings from `docs/solutions/`
 
 #### 1.2 Decide on External Research
@@ -518,8 +518,8 @@ After writing the plan file, present the options using the platform's blocking q
 2. **Run `/deepen-plan-beta`** - Stress-test weak sections with targeted research when the plan needs more confidence
 3. **Run `document-review` skill** - Improve the plan through structured document review
 4. **Share to Proof** - Upload the plan for collaborative review and sharing
-5. **Start `/systematic:ce-work`** - Begin implementing this plan in the current environment
-6. **Start `/systematic:ce-work` in another session** - Begin implementing in a separate agent session when the current platform supports it
+5. **Start `/ce:work`** - Begin implementing this plan in the current environment
+6. **Start `/ce:work` in another session** - Begin implementing in a separate agent session when the current platform supports it
 7. **Create Issue** - Create an issue in the configured tracker
 
 Based on selection:
@@ -536,8 +536,8 @@ Based on selection:
   PROOF_URL=$(echo "$RESPONSE" | jq -r '.tokenUrl')
   ```
   Display `View & collaborate in Proof: <PROOF_URL>` if successful, then return to the options
-- **`/systematic:ce-work`** → Call `/systematic:ce-work` with the plan path
-- **`/systematic:ce-work` in another session** → If the current platform supports launching a separate agent session, start `/systematic:ce-work` with the plan path there. Otherwise, explain the limitation briefly and offer to run `/systematic:ce-work` in the current session instead.
+- **`/ce:work`** → Call `/ce:work` with the plan path
+- **`/ce:work` in another session** → If the current platform supports launching a separate agent session, start `/ce:work` with the plan path there. Otherwise, explain the limitation briefly and offer to run `/ce:work` in the current session instead.
 - **Create Issue** → Follow the Issue Creation section below
 - **Other** → Accept free text for revisions and loop back to options
 
@@ -545,7 +545,7 @@ If running with ultrathink enabled, or the platform's reasoning/effort level is
 
 ## Issue Creation
 
-When the user selects "Create Issue", detect their project tracker from `CLAUDE.md` or `AGENTS.md`:
+When the user selects "Create Issue", detect their project tracker from `AGENTS.md`:
 
 1. Look for `project_tracker: github` or `project_tracker: linear`
 2. If GitHub:
@@ -562,11 +562,10 @@ When the user selects "Create Issue", detect their project tracker from `CLAUDE.
 
 4. If no tracker is configured:
    - Ask which tracker they use using the platform's blocking question tool when available (see Interaction Method)
-   - Suggest adding the tracker to `CLAUDE.md` or `AGENTS.md` for future runs
+   - Suggest adding the tracker to `AGENTS.md` for future runs
 
 After issue creation:
 - Display the issue URL
-- Ask whether to proceed to `/systematic:ce-work`
+- Ask whether to proceed to `/ce:work`
 
 NEVER CODE! Research, decide, and write the plan.
-