@fro.bot/systematic 1.11.1 → 1.13.0

package/LICENSE

@@ -1,6 +1,6 @@
 # The MIT License (MIT)
 
-Copyright (c) 2022 Marcus R. Brown <git@mrbro.dev>
+Copyright (c) 2026 Marcus R. Brown <git@mrbro.dev>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of
 this software and associated documentation files (the "Software"), to deal in

package/README.md

@@ -15,7 +15,7 @@
 
 <br>
 
-**[Overview](#overview)** · **[Quick Start](#quick-start)** · **[Skills](#skills)** · **[Agents](#agents)** · **[Commands](#commands)** · **[Development](#development)**
+**[Overview](#overview)** · **[Quick Start](#quick-start)** · **[Skills](#skills)** · **[Agents](#agents)** · **[Commands](#commands)** · **[CLI](#cli)** · **[Configuration](#configuration)** · **[Development](#development)**
 
 </div>
 
@@ -38,11 +38,12 @@ 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
-- **⚡ Zero Configuration** — Works immediately after installation via config hooks
-- **🔧 Extensible** — Add project-specific skills and commands alongside bundled ones
-- **📦 Batteries Included** — Skills, agents, and commands ship with the npm package
+- **Structured Skills** — Pre-built workflows for brainstorming, planning, and code review
+- **Specialized Agents** — Purpose-built subagents for architecture, security, and performance
+- **Zero Configuration** — Works immediately after installation via config hooks
+- **Extensible** — Add project-specific skills and commands alongside bundled ones
+- **Batteries Included** — 8 skills, 11 agents, and 9 commands ship with the npm package
+- **CLI Tooling** — Inspect, list, and convert assets from the command line
 
 ## Quick Start
 
@@ -145,7 +146,7 @@ Agents are specialized subagents with pre-configured prompts and expertise. They
 
 ### Using Agents
 
-Agents are invoked via OpenCode's `@mention` syntax or `delegate_task`:
+Agents are invoked via OpenCode's `@mention` syntax or `task`:
 
 ```
 @architecture-strategist Review the authentication refactoring in this PR
@@ -154,7 +155,7 @@ Agents are invoked via OpenCode's `@mention` syntax or `delegate_task`:
 Or programmatically in skills/commands:
 
 ```
-delegate_task(subagent_type="architecture-strategist", prompt="Review...")
+task(subagent_type="architecture-strategist", prompt="Review...")
 ```
 
 ## Commands
@@ -169,16 +170,52 @@ Commands are slash-invokable shortcuts that trigger workflows or actions.
 | `/workflows:plan` | Create detailed implementation plans |
 | `/workflows:review` | Run code review with specialized agents |
 | `/workflows:work` | Execute planned work systematically |
-| `/workflows:compound` | Build compound documentation |
+| `/workflows:compound` | Document recently solved problems to build team knowledge |
 
 ### Utility Commands
 
 | Command | Description |
 |---------|-------------|
-| `/systematic:lfg` | "Let's go" — start working immediately |
-| `/systematic:create-agent-skill` | Create a new skill with guidance |
-| `/systematic:deepen-plan` | Add detail to existing plans |
-| `/systematic:agent-native-audit` | Audit code for agent-native patterns |
+| `/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.
+
+```
+systematic <command> [options]
+```
+
+### Commands
+
+| Command | Description |
+|---------|-------------|
+| `list [type]` | List available skills, agents, or commands |
+| `convert <type> <file>` | Convert a CEP file and output the result to stdout |
+| `config show` | Show current configuration and file contents |
+| `config path` | Print config file locations |
+
+### Examples
+
+```bash
+# List all bundled skills
+systematic list skills
+
+# List all bundled agents
+systematic list agents
+
+# Convert a Claude Code agent to OpenCode format
+systematic convert agent ./agents/my-agent.md
+
+# Convert with a specific agent mode
+systematic convert agent ./agents/my-agent.md --mode=primary
+
+# Show configuration
+systematic config show
+```
 
 ## Configuration
 
@@ -186,16 +223,31 @@ Systematic works out of the box, but you can customize it via configuration file
 
 ### Plugin Configuration
 
-Create `~/.config/opencode/systematic.json` or `.opencode/systematic.json` to disable specific bundled content:
+Configuration is loaded from multiple locations and merged (later sources override earlier ones):
+
+1. **User config:** `~/.config/opencode/systematic.json`
+2. **Project config:** `.opencode/systematic.json`
+3. **Custom config:** `$OPENCODE_CONFIG_DIR/systematic.json` (if `OPENCODE_CONFIG_DIR` is set)
 
 ```json
 {
   "disabled_skills": ["git-worktree"],
   "disabled_agents": [],
-  "disabled_commands": []
+  "disabled_commands": [],
+  "bootstrap": {
+    "enabled": true
+  }
 }
 ```
 
+| Option | Type | Default | Description |
+|--------|------|---------|-------------|
+| `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:
@@ -219,7 +271,7 @@ The plugin exposes one tool to OpenCode:
 
 | Tool | Description |
 |------|-------------|
-| `systematic_skill` | Load Systematic bundled skills by name |
+| `systematic_skill` | Load Systematic bundled skills by name. Lists available skills in its description and returns formatted skill content when invoked. |
 
 For non-Systematic skills (project or user-level), use OpenCode's native `skill` tool.
 
@@ -247,9 +299,9 @@ flowchart TB
     style G fill:#0f0f23,stroke:#F5A623,color:#B2F5EA
 ```
 
-1. **`config` hook** — Merges bundled assets into your OpenCode configuration
-2. **`tool` hook** — Registers the `systematic_skill` tool for loading skills
-3. **`system.transform` hook** — Injects the "Using Systematic" guide into system prompts
+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.
+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.
 
@@ -286,20 +338,27 @@ bun test
 ### Project Structure
 
 ```
+systematic/
 ├── src/
-│   ├── index.ts              # Plugin entry point
+│   ├── index.ts              # Plugin entry point (SystematicPlugin)
 │   ├── cli.ts                # CLI entry point
 │   └── lib/
 │       ├── bootstrap.ts      # System prompt injection
-│       ├── config.ts         # JSONC config loading
-│       ├── config-handler.ts # OpenCode config hook
-│       ├── skill-tool.ts     # systematic_skill tool
+│       ├── config.ts         # JSONC config loading + merging
+│       ├── config-handler.ts # OpenCode config hook implementation
+│       ├── converter.ts      # CEP-to-OpenCode content conversion
+│       ├── skill-tool.ts     # systematic_skill tool factory
+│       ├── skill-loader.ts   # Skill content loading + formatting
 │       ├── skills.ts         # Skill discovery
 │       ├── agents.ts         # Agent discovery
-│       └── commands.ts       # Command discovery
-├── skills/                   # Bundled skills (SKILL.md files)
-├── agents/                   # Bundled agents (Markdown)
-├── commands/                 # Bundled commands (Markdown)
+│       ├── commands.ts       # Command discovery
+│       ├── frontmatter.ts    # YAML frontmatter parsing
+│       ├── validation.ts     # Agent config validation + type guards
+│       └── walk-dir.ts       # Recursive directory walker
+├── skills/                   # 8 bundled skills (SKILL.md files)
+├── agents/                   # 11 bundled agents (4 categories)
+├── commands/                 # 9 bundled commands (with workflows/ subdir)
+├── docs/                     # Starlight documentation site
 ├── tests/
 │   ├── unit/                 # Unit tests
 │   └── integration/          # Integration tests
@@ -317,6 +376,9 @@ bun test tests/unit/skills.test.ts
 
 # Run integration tests
 bun test tests/integration
+
+# Run all tests
+bun test
 ```
 
 ### Contributing
@@ -325,13 +387,15 @@ See [`AGENTS.md`](./AGENTS.md) for detailed development guidelines, code style c
 
 ## Converting from Claude Code
 
-Migrating skills, agents, or commands from Claude Code (CEP) 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, 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).
 
 ## References
 
+- [Systematic Documentation](https://fro.bot/systematic) — Full documentation site
 - [OpenCode Documentation](https://opencode.ai/docs/) — Official OpenCode platform docs
+- [OpenCode Plugin API](https://opencode.ai/docs/plugins) — Plugin development reference
 - [Compound Engineering Plugin](https://github.com/EveryInc/compound-engineering-plugin) — Original Claude Code workflows
-- [Plugin Source Code](https://github.com/marcusrbrown/systematic) — View the implementation
+- [Source Code](https://github.com/marcusrbrown/systematic) — View the implementation
 
 ## License
 

package/commands/workflows/brainstorm.md

@@ -33,7 +33,7 @@ Evaluate whether brainstorming is needed based on the feature description.
 - Constrained, well-defined scope
 
 **If requirements are already clear:**
-Use **AskUserQuestion tool** to suggest: "Your requirements seem detailed enough to proceed directly to planning. Should I run `/workflows:plan` instead, or would you like to explore the idea further?"
+Use the **question tool** to suggest: "Your requirements seem detailed enough to proceed directly to planning. Should I run `/workflows:plan` instead, or would you like to explore the idea further?"
 
 ### Phase 1: Understand the Idea
 
@@ -41,13 +41,13 @@ Use **AskUserQuestion tool** to suggest: "Your requirements seem detailed enough
 
 Run a quick repo scan to understand existing patterns:
 
-- Task repo-research-analyst("Understand existing patterns related to: <feature_description>")
+- task repo-research-analyst("Understand existing patterns related to: <feature_description>")
 
-Focus on: similar features, established patterns, CLAUDE.md guidance.
+Focus on: similar features, established patterns, AGENTS.md guidance.
 
 #### 1.2 Collaborative Dialogue
 
-Use the **AskUserQuestion tool** to ask questions **one at a time**.
+Use the **question tool** to ask questions **one at a time**.
 
 **Guidelines (see `brainstorming` skill for detailed techniques):**
 - Prefer multiple choice when natural options exist
@@ -68,7 +68,7 @@ For each approach, provide:
 
 Lead with your recommendation and explain why. Apply YAGNI—prefer simpler solutions.
 
-Use **AskUserQuestion tool** to ask which approach the user prefers.
+Use the **question tool** to ask which approach the user prefers.
 
 ### Phase 3: Capture the Design
 
@@ -80,15 +80,24 @@ Ensure `docs/brainstorms/` directory exists before writing.
 
 ### Phase 4: Handoff
 
-Use **AskUserQuestion tool** to present next steps:
+Use the **question tool** to present next steps:
 
 **Question:** "Brainstorm captured. What would you like to do next?"
 
 **Options:**
-1. **Proceed to planning** - Run `/workflows:plan` (will auto-detect this brainstorm)
-2. **Refine design further** - Continue exploring
+1. **Review and refine** - Improve the document through structured self-review
+2. **Proceed to planning** - Run `/workflows:plan` (will auto-detect this brainstorm)
 3. **Done for now** - Return later
 
+**If user selects "Review and refine":**
+
+Load the `document-review` skill and apply it to the brainstorm document.
+
+When document-review returns "Review complete", present next steps:
+
+1. **Move to planning** - Continue to `/workflows:plan` with this document
+2. **Done for now** - Brainstorming complete. To start planning later: `/workflows:plan [document-path]`
+
 ## Output Summary
 
 When complete, display:

package/commands/workflows/compound.md

@@ -21,53 +21,83 @@ Captures problem solutions while context is fresh, creating structured documenta
 /workflows:compound [brief context]    # Provide additional context hint
 ```
 
-## Execution Strategy: Parallel Subagents
-
-This command launches multiple specialized subagents IN PARALLEL to maximize efficiency:
-
-### 1. **Context Analyzer** (Parallel)
-   - Extracts conversation history
-   - Identifies problem type, component, symptoms
-   - Validates against CORA schema
-   - Returns: YAML frontmatter skeleton
-
-### 2. **Solution Extractor** (Parallel)
-   - Analyzes all investigation steps
-   - Identifies root cause
-   - Extracts working solution with code examples
-   - Returns: Solution content block
-
-### 3. **Related Docs Finder** (Parallel)
-   - Searches `docs/solutions/` for related documentation
-   - Identifies cross-references and links
-   - Finds related GitHub issues
-   - Returns: Links and relationships
-
-### 4. **Prevention Strategist** (Parallel)
-   - Develops prevention strategies
-   - Creates best practices guidance
-   - Generates test cases if applicable
-   - Returns: Prevention/testing content
-
-### 5. **Category Classifier** (Parallel)
-   - Determines optimal `docs/solutions/` category
-   - Validates category against schema
-   - Suggests filename based on slug
-   - Returns: Final path and filename
-
-### 6. **Documentation Writer** (Parallel)
-   - Assembles complete markdown file
-   - Validates YAML frontmatter
-   - Formats content for readability
-   - Creates the file in correct location
-
-### 7. **Optional: Specialized Agent Invocation** (Post-Documentation)
-   Based on problem type detected, automatically invoke applicable agents:
-   - **performance_issue** → `performance-oracle`
-   - **security_issue** → `security-sentinel`
-   - **database_issue** → `data-integrity-guardian`
-   - **test_failure** → `cora-test-reviewer`
-   - Any code-heavy issue → `kieran-rails-reviewer` + `code-simplicity-reviewer`
+## Execution Strategy: Two-Phase Orchestration
+
+<critical_requirement>
+**Only ONE file gets written - the final documentation.**
+
+Phase 1 subagents return TEXT DATA to the orchestrator. They must NOT use Write, Edit, or create any files. Only the orchestrator (Phase 2) writes the final documentation file.
+</critical_requirement>
+
+### Phase 1: Parallel Research
+
+<parallel_tasks>
+
+Launch these subagents IN PARALLEL. Each returns text data to the orchestrator.
+
+#### 1. **Context Analyzer**
+- Extracts conversation history
+- Identifies problem type, component, symptoms
+- Validates against schema
+- Returns: YAML frontmatter skeleton
+
+#### 2. **Solution Extractor**
+- Analyzes all investigation steps
+- Identifies root cause
+- Extracts working solution with code examples
+- Returns: Solution content block
+
+#### 3. **Related Docs Finder**
+- Searches `docs/solutions/` for related documentation
+- Identifies cross-references and links
+- Finds related GitHub issues
+- Returns: Links and relationships
+
+#### 4. **Prevention Strategist**
+- Develops prevention strategies
+- Creates best practices guidance
+- Generates test cases if applicable
+- Returns: Prevention/testing content
+
+#### 5. **Category Classifier**
+- Determines optimal `docs/solutions/` category
+- Validates category against schema
+- Suggests filename based on slug
+- Returns: Final path and filename
+
+</parallel_tasks>
+
+### Phase 2: Assembly & Write
+
+<sequential_tasks>
+
+**WAIT for all Phase 1 subagents to complete before proceeding.**
+
+The orchestrating agent (main conversation) performs these steps:
+
+1. Collect all text results from Phase 1 subagents
+2. Assemble complete markdown file from the collected pieces
+3. Validate YAML frontmatter against schema
+4. Create directory if needed: `mkdir -p docs/solutions/[category]/`
+5. Write the SINGLE final file: `docs/solutions/[category]/[filename].md`
+
+</sequential_tasks>
+
+### Phase 3: Optional Enhancement
+
+**WAIT for Phase 2 to complete before proceeding.**
+
+<parallel_tasks>
+
+Based on problem type, optionally invoke specialized agents to review the documentation:
+
+- **performance_issue** → `performance-oracle`
+- **security_issue** → `security-sentinel`
+- **database_issue** → `data-integrity-guardian`
+- **test_failure** → `cora-test-reviewer`
+- Any code-heavy issue → `kieran-rails-reviewer` + `code-simplicity-reviewer`
+
+</parallel_tasks>
 
 ## What It Captures
 
@@ -110,24 +140,29 @@ This command launches multiple specialized subagents IN PARALLEL to maximize eff
 - integration-issues/
 - logic-errors/
 
+## Common Mistakes to Avoid
+
+| Wrong | Correct |
+|----------|-----------:|
+| Subagents write files like `context-analysis.md`, `solution-draft.md` | Subagents return text data; orchestrator writes one final file |
+| Research and assembly run in parallel | Research completes, then assembly runs |
+| Multiple files created during workflow | Single file: `docs/solutions/[category]/[filename].md` |
+
 ## Success Output
 
 ```
-✓ Parallel documentation generation complete
-
-Primary Subagent Results:
-  ✓ Context Analyzer: Identified performance_issue in brief_system
-  ✓ Solution Extractor: Extracted 3 code fixes
-  ✓ Related Docs Finder: Found 2 related issues
-  ✓ Prevention Strategist: Generated test cases
-  ✓ Category Classifier: docs/solutions/performance-issues/
-  ✓ Documentation Writer: Created complete markdown
+Subagent Results:
+  Context Analyzer: Identified performance_issue in brief_system
+  Solution Extractor: 3 code fixes
+  Related Docs Finder: 2 related issues
+  Prevention Strategist: Prevention strategies, test suggestions
+  Category Classifier: `performance-issues`
 
 Specialized Agent Reviews (Auto-Triggered):
-  ✓ performance-oracle: Validated query optimization approach
-  ✓ kieran-rails-reviewer: Code examples meet Rails standards
-  ✓ code-simplicity-reviewer: Solution is appropriately minimal
-  ✓ every-style-editor: Documentation style verified
+  performance-oracle: Validated query optimization approach
+  kieran-rails-reviewer: Code examples meet Rails standards
+  code-simplicity-reviewer: Solution is appropriately minimal
+  every-style-editor: Documentation style verified
 
 File created:
 - docs/solutions/performance-issues/n-plus-one-brief-generation.md

package/commands/workflows/plan.md

@@ -1,7 +1,7 @@
 ---
 name: workflows:plan
 description: Transform feature descriptions into well-structured project plans following conventions
-argument-hint: "[feature description, bug report, or improvement idea]"
+argument-hint: '[feature description, bug report, or improvement idea]'
 ---
 
 # Create a plan for a new feature or bug fix
@@ -43,11 +43,11 @@ ls -la docs/brainstorms/*.md 2>/dev/null | head -10
 5. Use brainstorm decisions as input to the research phase
 
 **If multiple brainstorms could match:**
-Use **AskUserQuestion tool** to ask which brainstorm to use, or whether to proceed without one.
+Use **question tool** to ask which brainstorm to use, or whether to proceed without one.
 
 **If no brainstorm found (or not relevant), run idea refinement:**
 
-Refine the idea through collaborative dialogue using the **AskUserQuestion tool**:
+Refine the idea through collaborative dialogue using the **question tool**:
 
 - Ask questions one at a time to understand the idea fully
 - Prefer multiple choice questions when natural options exist
@@ -74,11 +74,11 @@ First, I need to understand the project's conventions, existing patterns, and an
 
 Run these agents **in parallel** to gather local context:
 
-- Task repo-research-analyst(feature_description)
-- Task learnings-researcher(feature_description)
+- task repo-research-analyst(feature_description)
+- task learnings-researcher(feature_description)
 
 **What to look for:**
-- **Repo research:** existing patterns, CLAUDE.md guidance, technology familiarity, pattern consistency
+- **Repo research:** existing patterns, AGENTS.md guidance, technology familiarity, pattern consistency
 - **Learnings:** documented solutions in `docs/solutions/` that might apply (gotchas, patterns, lessons learned)
 
 These findings inform the next step.
@@ -89,7 +89,7 @@ Based on signals from Step 0 and findings from Step 1, decide on external resear
 
 **High-risk topics → always research.** Security, payments, external APIs, data privacy. The cost of missing something is too high. This takes precedence over speed signals.
 
-**Strong local context → skip external research.** Codebase has good patterns, CLAUDE.md has guidance, user knows what they want. External research adds little value.
+**Strong local context → skip external research.** Codebase has good patterns, AGENTS.md has guidance, user knows what they want. External research adds little value.
 
 **Uncertainty or unfamiliar territory → research.** User is exploring, codebase has no examples, new technology. External perspective is valuable.
 
@@ -105,8 +105,8 @@ Examples:
 
 Run these agents in parallel:
 
-- Task best-practices-researcher(feature_description)
-- Task framework-docs-researcher(feature_description)
+- task best-practices-researcher(feature_description)
+- task framework-docs-researcher(feature_description)
 
 ### 1.6. Consolidate Research
 
@@ -116,7 +116,7 @@ After all research steps complete, consolidate findings:
 - **Include relevant institutional learnings** from `docs/solutions/` (key insights, gotchas to avoid)
 - Note external documentation URLs and best practices (if external research was done)
 - List related issues or PRs discovered
-- Capture CLAUDE.md conventions
+- Capture AGENTS.md conventions
 
 **Optional validation:** Briefly summarize findings and ask if anything looks off or missing before proceeding to planning.
 
@@ -150,7 +150,7 @@ Think like a product manager - what would make this issue clear and actionable?
 
 After planning the issue structure, run SpecFlow Analyzer to validate and refine the feature specification:
 
-- Task spec-flow-analyzer(feature_description, research_findings)
+- task spec-flow-analyzer(feature_description, research_findings)
 
 **SpecFlow Analyzer Output:**
 
@@ -491,38 +491,36 @@ Examples:
 
 ## Post-Generation Options
 
-After writing the plan file, use the **AskUserQuestion tool** to present these options:
+After writing the plan file, use the **question tool** to present these options:
 
 **Question:** "Plan ready at `docs/plans/YYYY-MM-DD-<type>-<name>-plan.md`. What would you like to do next?"
 
 **Options:**
 1. **Open plan in editor** - Open the plan file for review
 2. **Run `/deepen-plan`** - Enhance each section with parallel research agents (best practices, performance, UI)
-3. **Run `/plan_review`** - Get feedback from reviewers (DHH, Kieran, Simplicity)
-4. **Start `/workflows:work`** - Begin implementing this plan locally
-5. **Start `/workflows:work` on remote** - Begin implementing in Claude Code on the web (use `&` to run in background)
+3. **Run `/technical_review`** - Technical feedback from code-focused reviewers (DHH, Kieran, Simplicity)
+4. **Review and refine** - Improve the document through structured self-review
+5. **Start `/workflows:work`** - Begin implementing this plan locally
 6. **Create Issue** - Create issue in project tracker (GitHub/Linear)
-7. **Simplify** - Reduce detail level
 
 Based on selection:
 - **Open plan in editor** → Run `open docs/plans/<plan_filename>.md` to open the file in the user's default editor
 - **`/deepen-plan`** → Call the /deepen-plan command with the plan file path to enhance with research
-- **`/plan_review`** → Call the /plan_review command with the plan file path
+- **`/technical_review`** → Call the /technical_review command with the plan file path
+- **Review and refine** → Load `document-review` skill.
 - **`/workflows:work`** → Call the /workflows:work command with the plan file path
-- **`/workflows:work` on remote** → Run `/workflows:work docs/plans/<plan_filename>.md &` to start work in background for Claude Code web
 - **Create Issue** → See "Issue Creation" section below
-- **Simplify** → Ask "What should I simplify?" then regenerate simpler version
 - **Other** (automatically provided) → Accept free text for rework or specific changes
 
 **Note:** If running `/workflows: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 `/workflows:work` or `/plan_review`.
+Loop back to options after Simplify or Other changes until user selects `/workflows:work` or `/technical_review`.
 
 ## Issue Creation
 
-When user selects "Create Issue", detect their project tracker from CLAUDE.md:
+When user selects "Create Issue", detect their project tracker from AGENTS.md:
 
-1. **Check for tracker preference** in user's CLAUDE.md (global or project):
+1. **Check for tracker preference** in user's AGENTS.md (global or project):
    - Look for `project_tracker: github` or `project_tracker: linear`
    - Or look for mentions of "GitHub Issues" or "Linear" in their workflow section
 
@@ -542,10 +540,10 @@ When user selects "Create Issue", detect their project tracker from CLAUDE.md:
 
 4. **If no tracker configured:**
    Ask user: "Which project tracker do you use? (GitHub/Linear/Other)"
-   - Suggest adding `project_tracker: github` or `project_tracker: linear` to their CLAUDE.md
+   - Suggest adding `project_tracker: github` or `project_tracker: linear` to their AGENTS.md
 
 5. **After creation:**
    - Display the issue URL
-   - Ask if they want to proceed to `/workflows:work` or `/plan_review`
+   - Ask if they want to proceed to `/workflows:work` or `/technical_review`
 
 NEVER CODE! Just research and write the plan.