@fro.bot/systematic 1.23.2 → 2.0.0

package/skills/deepen-plan/SKILL.md

@@ -10,7 +10,7 @@ argument-hint: '[path to plan file]'
 
 **Note: The current year is 2026.** Use this when searching for recent documentation and best practices.
 
-This command takes an existing plan (from `/systematic:ce-plan`) and enhances each section with parallel research agents. Each major element gets its own dedicated research sub-agent to find:
+This command takes an existing plan (from `/ce:plan`) and enhances each section with parallel research agents. Each major element gets its own dedicated research sub-agent to find:
 - Best practices and industry patterns
 - Performance optimizations
 - UI/UX improvements (if applicable)
@@ -68,9 +68,9 @@ Dynamically discover all available skills and match them to plan sections. Don't
 ls .opencode/skills/
 
 # 2. User's global skills (~/.config/opencode/)
-ls ~/.opencode/skills/
+ls ~/.config/opencode/skills/
 
-# 3. compound-engineering plugin skills
+# 3. systematic plugin skills
 ls ~/.config/opencode/plugins/cache/*/compound-engineering/*/skills/
 
 # 4. ALL other installed plugins - check every plugin for skills
@@ -137,7 +137,7 @@ Task general-purpose: "Use the frontend-design skill at ~/.config/opencode/plugi
 
 Task general-purpose: "Use the agent-native-architecture skill at ~/.config/opencode/plugins/.../agent-native-architecture. Read SKILL.md and apply it to: [agent/tool sections of plan]"
 
-Task general-purpose: "Use the security-patterns skill at ~/.opencode/skills/security-patterns. Read SKILL.md and apply it to: [full plan]"
+Task general-purpose: "Use the security-patterns skill at ~/.config/opencode/skills/security-patterns. Read SKILL.md and apply it to: [full plan]"
 ```
 
 **No limit on skill sub-agents. Spawn one for every skill that could possibly be relevant.**
@@ -145,13 +145,13 @@ Task general-purpose: "Use the security-patterns skill at ~/.opencode/skills/sec
 ### 3. Discover and Apply Learnings/Solutions
 
 <thinking>
-Check for documented learnings from /systematic:ce-compound. These are solved problems stored as markdown files. Spawn a sub-agent for each learning to check if it's relevant.
+Check for documented learnings from /ce:compound. These are solved problems stored as markdown files. Spawn a sub-agent for each learning to check if it's relevant.
 </thinking>
 
 **LEARNINGS LOCATION - Check these exact folders:**
 
 ```
-docs/solutions/           <-- PRIMARY: Project-level learnings (created by /systematic:ce-compound)
+docs/solutions/           <-- PRIMARY: Project-level learnings (created by /ce:compound)
 ├── performance-issues/
 │   └── *.md
 ├── debugging-patterns/
@@ -175,7 +175,7 @@ Run these commands to get every learning file:
 find docs/solutions -name "*.md" -type f 2>/dev/null
 
 # If docs/solutions doesn't exist, check alternate locations:
-find .claude/docs -name "*.md" -type f 2>/dev/null
+find .opencode/docs -name "*.md" -type f 2>/dev/null
 find ~/.config/opencode/docs -name "*.md" -type f 2>/dev/null
 ```
 
@@ -305,12 +305,12 @@ Dynamically discover every available agent and run them ALL against the plan. Do
 
 ```bash
 # 1. Project-local agents (highest priority - project-specific)
-find .claude/agents -name "*.md" 2>/dev/null
+find .opencode/agents -name "*.md" 2>/dev/null
 
 # 2. User's global agents (~/.config/opencode/)
 find ~/.config/opencode/agents -name "*.md" 2>/dev/null
 
-# 3. compound-engineering plugin agents (all subdirectories)
+# 3. systematic plugin agents (all subdirectories)
 find ~/.config/opencode/plugins/cache/*/compound-engineering/*/agents -name "*.md" 2>/dev/null
 
 # 4. ALL other installed plugins - check every plugin for agents
@@ -324,13 +324,13 @@ cat ~/.config/opencode/plugins/installed_plugins.json
 ```
 
 **Important:** Check EVERY source. Include agents from:
-- Project `.claude/agents/`
+- Project `.opencode/agents/`
 - User's `~/.config/opencode/agents/`
-- compound-engineering plugin (but SKIP workflow/ agents - only use review/, research/, design/, docs/)
+- systematic plugin (but SKIP workflow/ agents - only use review/, research/, design/, docs/)
 - ALL other installed plugins (agent-sdk-dev, frontend-design, etc.)
 - Any local plugins
 
-**For compound-engineering plugin specifically:**
+**For systematic plugin specifically:**
 - USE: `agents/review/*` (all reviewers)
 - USE: `agents/research/*` (all researchers)
 - USE: `agents/design/*` (design agents)
@@ -370,7 +370,7 @@ Wait for ALL parallel agents to complete - skills, research agents, review agent
 **Collect outputs from ALL sources:**
 
 1. **Skill-based sub-agents** - Each skill's full output (code examples, patterns, recommendations)
-2. **Learnings/Solutions sub-agents** - Relevant documented learnings from /systematic:ce-compound
+2. **Learnings/Solutions sub-agents** - Relevant documented learnings from /ce:compound
 3. **Research agents** - Best practices, documentation, real-world examples
 4. **Review agents** - All feedback from every reviewer (architecture, security, performance, simplicity, etc.)
 5. **Context7 queries** - Framework documentation and patterns
@@ -480,13 +480,13 @@ After writing the enhanced plan, use the **question tool** to present these opti
 
 **Options:**
 1. **View diff** - Show what was added/changed
-2. **Start `/systematic:ce-work`** - Begin implementing this enhanced plan
+2. **Start `/ce:work`** - Begin implementing this enhanced plan
 3. **Deepen further** - Run another round of research on specific sections
 4. **Revert** - Restore original plan (if backup exists)
 
 Based on selection:
 - **View diff** → Run `git diff [plan_path]` or show before/after
-- **`/systematic:ce-work`** → Call the /systematic:ce-work command with the plan file path
+- **`/ce:work`** → Call the /ce:work command with the plan file path
 - **Deepen further** → Ask which sections need more research, then re-run those agents
 - **Revert** → Restore from git or backup
 

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

@@ -23,7 +23,7 @@ This skill does **not** turn plans into implementation scripts. It identifies we
 
 ## 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.
 
@@ -83,7 +83,7 @@ Use this default:
 
 If the plan already appears sufficiently grounded:
 - Say so briefly
-- Recommend moving to `/systematic:ce-work` or the `document-review` skill
+- Recommend moving to `/ce:work` or the `document-review` skill
 - If the user explicitly asked to deepen anyway, continue with a light pass and deepen at most 1-2 sections
 
 ### Phase 1: Parse the Current `ce:plan-beta` Structure
@@ -317,7 +317,7 @@ Based on selection:
 
 If no substantive changes were warranted:
 - Say that the plan already appears sufficiently grounded
-- Offer the `document-review` skill or `/systematic:ce-work` as the next step instead
+- Offer the `document-review` skill or `/ce:work` as the next step instead
 
 NEVER CODE! Research, challenge, and strengthen the plan.
 

package/skills/deploy-docs/SKILL.md

@@ -14,16 +14,16 @@ Run these checks:
 
 ```bash
 # Count components
-echo "Agents: $(ls plugins/compound-engineering/agents/*.md | wc -l)"
-echo "Skills: $(ls -d plugins/compound-engineering/skills/*/ 2>/dev/null | wc -l)"
+echo "Agents: $(ls plugins/systematic/agents/*.md | wc -l)"
+echo "Skills: $(ls -d plugins/systematic/skills/*/ 2>/dev/null | wc -l)"
 
 # Validate JSON
 cat .claude-plugin/marketplace.json | jq . > /dev/null && echo "✓ marketplace.json valid"
-cat plugins/compound-engineering/.claude-plugin/plugin.json | jq . > /dev/null && echo "✓ plugin.json valid"
+cat plugins/systematic/.claude-plugin/plugin.json | jq . > /dev/null && echo "✓ plugin.json valid"
 
 # Check all HTML files exist
 for page in index agents commands skills mcp-servers changelog getting-started; do
-  if [ -f "plugins/compound-engineering/docs/pages/${page}.html" ] || [ -f "plugins/compound-engineering/docs/${page}.html" ]; then
+  if [ -f "plugins/systematic/docs/pages/${page}.html" ] || [ -f "plugins/systematic/docs/${page}.html" ]; then
     echo "✓ ${page}.html exists"
   else
     echo "✗ ${page}.html MISSING"
@@ -34,7 +34,7 @@ done
 ## Step 2: Check for Uncommitted Changes
 
 ```bash
-git status --porcelain plugins/compound-engineering/docs/
+git status --porcelain plugins/systematic/docs/
 ```
 
 If there are uncommitted changes, warn the user to commit first.
@@ -66,7 +66,7 @@ on:
   push:
     branches: [main]
     paths:
-      - 'plugins/compound-engineering/docs/**'
+      - 'plugins/systematic/docs/**'
   workflow_dispatch:
 
 permissions:
@@ -89,7 +89,7 @@ jobs:
       - uses: actions/configure-pages@v4
       - uses: actions/upload-pages-artifact@v3
         with:
-          path: 'plugins/compound-engineering/docs'
+          path: 'plugins/systematic/docs'
       - uses: actions/deploy-pages@v4
 ```
 
@@ -108,6 +108,6 @@ Provide a summary:
 - [ ] Commit any pending changes
 - [ ] Push to main branch
 - [ ] Verify GitHub Pages workflow exists
-- [ ] Check deployment at https://everyinc.github.io/compound-engineering-plugin/
+- [ ] Check deployment at https://everyinc.github.io/systematic/
 ```
 

package/skills/file-todos/SKILL.md

@@ -185,7 +185,7 @@ Work logs serve as:
 
 | Trigger | Flow | Tool |
 |---------|------|------|
-| Code review | `/workflows:review` → Findings → `/triage` → Todos | Review agent + skill |
+| Code review | `/ce:review` → Findings → `/triage` → Todos | Review agent + skill |
 | PR comments | `/resolve_pr_parallel` → Individual fixes → Todos | gh CLI + skill |
 | Code TODOs | `/resolve_todo_parallel` → Fixes + Complex todos | Agent + skill |
 | Planning | Brainstorm → Create todo → Work → Complete | Skill |
@@ -250,3 +250,4 @@ grep -r "payment" todos/
 - Temporary tracking for single conversation
 - Not persisted to disk
 - Different from both systems above
+

package/skills/generate_command/SKILL.md

@@ -114,7 +114,7 @@ Implement #$ARGUMENTS following these steps:
 3. Implement
    - Follow existing code patterns (reference specific files)
    - Write tests first if doing TDD
-   - Ensure code follows CLAUDE.md conventions
+   - Ensure code follows AGENTS.md conventions
 
 4. Verify
    - Run tests: `bin/rails test`

package/skills/{report-bug → report-bug-ce}/SKILL.md

@@ -1,17 +1,17 @@
 ---
-name: report-bug
-description: Report a bug in the compound-engineering plugin
+name: report-bug-ce
+description: Use this skill when a user needs to report a bug in the Systematic plugin with complete reproduction details and environment data, then open a GitHub issue directly from the CLI.
 argument-hint: '[optional: brief description of the bug]'
 disable-model-invocation: true
 ---
 
-# Report a Compounding Engineering Plugin Bug
+# Report a Systematic Plugin Bug
 
-Report bugs encountered while using the compound-engineering plugin. This command gathers structured information and creates a GitHub issue for the maintainer.
+Report bugs encountered while using the Systematic plugin. This skill gathers structured information and creates a GitHub issue for maintainers.
 
 ## Step 1: Gather Bug Information
 
-Use the question tool to collect the following information:
+Ask the user the following questions (using the platform's blocking question tool — e.g., `question` in OpenCode, `request_user_input` in Codex, `ask_user` in Gemini — or present numbered options and wait for a reply):
 
 **Question 1: Bug Category**
 - What type of issue are you experiencing?
@@ -39,18 +39,25 @@ Use the question tool to collect the following information:
 
 ## Step 2: Collect Environment Information
 
-Automatically gather:
-```bash
-# Get plugin version
-cat ~/.config/opencode/plugins/installed_plugins.json 2>/dev/null | grep -A5 "compound-engineering" | head -10 || echo "Plugin info not found"
-
-# Get OpenCode version
-claude --version 2>/dev/null || echo "Claude CLI version unknown"
+Automatically gather environment details. Detect the coding agent platform and collect what is available:
 
-# Get OS info
+**OS info (all platforms):**
+```bash
 uname -a
 ```
 
+**Plugin version:** Read the plugin manifest or installed plugin metadata. Common locations:
+- OpenCode: `~/.config/opencode/plugins/installed_plugins.json`
+- Codex: `.codex/plugins/` or project config
+- Other platforms: check the platform's plugin registry
+
+**Agent CLI version:** Run the platform's version command:
+- OpenCode: `opencode --version`
+- Codex: `codex --version`
+- Other platforms: use the appropriate CLI version flag
+
+If any of these fail, note "unknown" and continue — do not block the report.
+
 ## Step 3: Format the Bug Report
 
 Create a well-structured bug report with:
@@ -63,8 +70,9 @@ Create a well-structured bug report with:
 
 ## Environment
 
-- **Plugin Version:** [from installed_plugins.json]
-- **OpenCode Version:** [from claude --version]
+- **Plugin Version:** [from plugin manifest/registry]
+- **Agent Platform:** [e.g., OpenCode, Codex, Copilot, Pi, Kilo]
+- **Agent Version:** [from CLI version command]
 - **OS:** [from uname]
 
 ## What Happened
@@ -83,16 +91,14 @@ Create a well-structured bug report with:
 
 ## Error Messages
 
-```
 [Any error output]
-```
 
 ## Additional Context
 
 [Any other relevant information]
 
 ---
-*Reported via `/report-bug` command*
+*Reported via `/report-bug-ce` skill*
 ```
 
 ## Step 4: Create GitHub Issue
@@ -101,17 +107,17 @@ Use the GitHub CLI to create the issue:
 
 ```bash
 gh issue create \
-  --repo EveryInc/compound-engineering-plugin \
-  --title "[compound-engineering] Bug: [Brief description]" \
+  --repo marcusrbrown/systematic \
+  --title "[systematic] Bug: [Brief description]" \
   --body "[Formatted bug report from Step 3]" \
-  --label "bug,compound-engineering"
+  --label "bug"
 ```
 
 **Note:** If labels don't exist, create without labels:
 ```bash
 gh issue create \
-  --repo EveryInc/compound-engineering-plugin \
-  --title "[compound-engineering] Bug: [Brief description]" \
+  --repo marcusrbrown/systematic \
+  --title "[systematic] Bug: [Brief description]" \
   --body "[Formatted bug report]"
 ```
 
@@ -125,28 +131,27 @@ After the issue is created:
 ## Output Format
 
 ```
-✅ Bug report submitted successfully!
+Bug report submitted successfully!
 
-Issue: https://github.com/EveryInc/compound-engineering-plugin/issues/[NUMBER]
-Title: [compound-engineering] Bug: [description]
+Issue: https://github.com/marcusrbrown/systematic/issues/[NUMBER]
+Title: [systematic] Bug: [description]
 
-Thank you for helping improve the compound-engineering plugin!
+Thank you for helping improve Systematic!
 The maintainer will review your report and respond as soon as possible.
 ```
 
 ## Error Handling
 
-- If `gh` CLI is not authenticated: Prompt user to run `gh auth login` first
-- If issue creation fails: Display the formatted report so user can manually create the issue
-- If required information is missing: Re-prompt for that specific field
+- If `gh` CLI is not installed or not authenticated: prompt the user to install/authenticate first
+- If issue creation fails: display the formatted report so the user can manually create the issue
+- If required information is missing: re-prompt for that specific field
 
 ## Privacy Notice
 
-This command does NOT collect:
+This skill does NOT collect:
 - Personal information
 - API keys or credentials
-- Private code from your projects
+- Private code from projects
 - File paths beyond basic OS info
 
 Only technical information about the bug is included in the report.
-

package/skills/resolve-todo-parallel/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: resolve-todo-parallel
+description: Use this skill when there are multiple unresolved CLI todo files and you want to resolve them in parallel, document learnings, and clean up completed entries in one disciplined pass.
+argument-hint: '[optional: specific todo ID or pattern]'
+---
+
+Resolve all TODO comments using parallel processing, document lessons learned, then clean up completed todos.
+
+## Workflow
+
+### 1. Analyze
+
+Get all unresolved TODOs from the /todos/*.md directory
+
+If any todo recommends deleting, removing, or gitignoring files in `docs/brainstorms/`, `docs/plans/`, or `docs/solutions/`, skip it and mark it as `wont_fix`. These are Systematic workflow artifacts that are intentional and permanent.
+
+### 2. Plan
+
+Create a task list of all unresolved items grouped by type (e.g., `todowrite` in OpenCode, `update_plan` in Codex). Analyze dependencies and prioritize items that others depend on. For example, if a rename is needed, it must complete before dependent items. Output a mermaid flow diagram showing execution order — what can run in parallel, and what must run first.
+
+### 3. Implement (PARALLEL)
+
+Spawn a `pr-comment-resolver` agent for each unresolved item.
+
+If there are 3 items, spawn 3 agents — one per item. Prefer running all agents in parallel; if the platform does not support parallel dispatch, run them sequentially respecting the dependency order from step 2.
+
+Keep parent-context pressure bounded:
+- If there are 1-4 unresolved items, direct parallel returns are fine
+- If there are 5+ unresolved items, launch in batches of at most 4 agents at a time
+- Require each resolver agent to return only a short status summary to the parent: todo handled, files changed, tests run or skipped, and any blocker that still needs follow-up
+
+If the todo set is large enough that even batched short returns are likely to get noisy, use a per-run scratch directory such as `.context/systematic/resolve-todo-parallel/<run-id>/`:
+- Have each resolver write a compact artifact for its todo there
+- Return only a completion summary to the parent
+- Re-read only the artifacts that are needed to summarize outcomes, document learnings, or decide whether a todo is truly resolved
+
+### 4. Commit & Resolve
+
+- Commit changes
+- Remove the TODO from the file, and mark it as resolved.
+- Push to remote
+
+GATE: STOP. Verify that todos have been resolved and changes committed. Do NOT proceed to step 5 if no todos were resolved.
+
+### 5. Compound on Lessons Learned
+
+Load the `ce:compound` skill to document what was learned from resolving the todos.
+
+The todo resolutions often surface patterns, recurring issues, or architectural insights worth capturing. This step ensures that knowledge compounds rather than being lost.
+
+GATE: STOP. Verify that the compound skill produced a solution document in `docs/solutions/`. If no document was created (user declined or no non-trivial learnings), continue to step 6.
+
+### 6. Clean Up Completed Todos
+
+List all todos and identify those with `done` or `resolved` status, then delete them to keep the todo list clean and actionable.
+
+If a scratch directory was used and the user did not ask to inspect it, clean it up after todo cleanup succeeds.
+
+After cleanup, output a summary:
+
+```
+Todos resolved: [count]
+Lessons documented: [path to solution doc, or "skipped"]
+Todos cleaned up: [count deleted]
+```

package/skills/setup/SKILL.md

@@ -8,7 +8,7 @@ disable-model-invocation: true
 
 ## Interaction Method
 
-If `AskUserQuestion` is available, use it for all prompts below.
+If `question` is available, use it for all prompts below.
 
 If not, present each question as a numbered list and wait for a reply before proceeding to the next step. For multiSelect questions, accept comma-separated numbers (e.g. `1, 3`). Never skip or auto-configure.
 
@@ -16,7 +16,7 @@ Interactive setup for `systematic.local.md` — configures which agents run duri
 
 ## Step 1: Check Existing Config
 
-Read `systematic.local.md` in the project root. If it exists, display current settings summary and use AskUserQuestion:
+Read `systematic.local.md` in the project root. If it exists, display current settings summary and use question:
 
 ```
 question: "Settings file already exists. What would you like to do?"
@@ -47,7 +47,7 @@ test -f requirements.txt && echo "python" || \
 echo "general"
 ```
 
-Use AskUserQuestion:
+Use question:
 
 ```
 question: "Detected {type} project. How would you like to configure?"

package/skills/test-browser/SKILL.md

@@ -133,8 +133,8 @@ If the user passed a port number (e.g., `/test-browser 5000` or `/test-browser -
 
 **Priority 2: AGENTS.md / project instructions**
 ```bash
-# Check CLAUDE.md for port references
-grep -Eio '(port\s*[:=]\s*|localhost:)([0-9]{4,5})' CLAUDE.md 2>/dev/null | grep -Eo '[0-9]{4,5}' | head -1
+# Check AGENTS.md for port references
+grep -Eio '(port\s*[:=]\s*|localhost:)([0-9]{4,5})' AGENTS.md 2>/dev/null | grep -Eo '[0-9]{4,5}' | head -1
 ```
 
 **Priority 3: package.json scripts**
@@ -158,7 +158,7 @@ Store the result in a `PORT` variable for use in all subsequent steps.
 # Combined detection (run this)
 PORT="${EXPLICIT_PORT:-}"
 if [ -z "$PORT" ]; then
-  PORT=$(grep -Eio '(port\s*[:=]\s*|localhost:)([0-9]{4,5})' CLAUDE.md 2>/dev/null | grep -Eo '[0-9]{4,5}' | head -1)
+  PORT=$(grep -Eio '(port\s*[:=]\s*|localhost:)([0-9]{4,5})' AGENTS.md 2>/dev/null | grep -Eo '[0-9]{4,5}' | head -1)
 fi
 if [ -z "$PORT" ]; then
   PORT=$(grep -Eo '\-\-port[= ]+[0-9]{4,5}' package.json 2>/dev/null | grep -Eo '[0-9]{4,5}' | head -1)
@@ -391,4 +391,3 @@ agent-browser --headed click @e1       # Click in visible browser
 agent-browser wait @e1             # Wait for element
 agent-browser wait 2000            # Wait milliseconds
 ```
-

package/skills/create-agent-skill/SKILL.md

@@ -1,10 +0,0 @@
----
-name: create-agent-skill
-description: Create or edit OpenCode skills with expert guidance on structure and best practices
-allowed-tools: Skill(create-agent-skills)
-argument-hint: '[skill description or requirements]'
-disable-model-invocation: true
----
-
-Invoke the create-agent-skills skill for: $ARGUMENTS
-