opencode-onboard 0.4.14 → 0.4.15

package/README.md

@@ -6,7 +6,7 @@
 
 **One command to prepare any codebase for AI agent workflows in OpenCode.**
 
-Works with [OpenCode](https://opencode.ai), [OpenCode Ensemble](https://github.com/hueyexe/opencode-ensemble), [OpenSpec](https://github.com/fission-ai/openspec), GitHub, Azure DevOps, or no tracker/PR platform at all.
+Works with [OpenCode](https://opencode.ai), [OpenCode Ensemble](https://github.com/hueyexe/opencode-ensemble), [OpenSpec](https://github.com/fission-ai/openspec), GitHub, Azure DevOps, or no tracker/PR platform at all.
 
 [![npm version](https://img.shields.io/npm/v/opencode-onboard?style=flat-square&color=black)](https://www.npmjs.com/package/opencode-onboard)
 [![npm downloads](https://img.shields.io/npm/dm/opencode-onboard?style=flat-square&color=black)](https://www.npmjs.com/package/opencode-onboard)
@@ -74,8 +74,8 @@ The CLI runs a 10-step onboarding wizard. It keeps the current step visible, plu
 | --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **1. Source scope**               | Choose current repo or sibling source roots for code analysis                                                                                                        |
 | **2. Clean AI files**             | Detects existing `AGENTS.md`, `.cursorrules`, `CLAUDE.md`, `.agents/` etc. and removes them, preserves your `.agents/skills/`                                        |
-| **3. Choose platform**            | GitHub, Azure DevOps, or None                                                                                                                                       |
-| **4. Check platform CLI**         | Verifies `gh` (GitHub) or `az` + `azure-devops` (Azure DevOps), or skips checks when platform is None                                                              |
+| **3. Choose platform**            | GitHub, Azure DevOps, or None                                                                                                                                       |
+| **4. Check platform CLI**         | Verifies `gh` (GitHub) or `az` + `azure-devops` (Azure DevOps), or skips checks when platform is None                                                              |
 | **5. Copy scaffolding**           | Copies agents + built-in skills + bootstrap docs, writes source-roots metadata, applies AGENTS bootstrap patching, copies `skills-lock.json`, then runs `npx skills` |
 | **6. Init OpenSpec**              | Runs `npx @fission-ai/openspec init` silently for structured change management                                                                                       |
 | **7. Choose models**              | Fetches live model list from [models.dev](https://models.dev), lets you pick plan / build / fast models with cost indicators and canonical pricing                   |
@@ -100,7 +100,7 @@ Custom slash commands are installed into `.opencode/commands/` and are available
 | Command        | Description                                                                                           |
 | -------------- | ----------------------------------------------------------------------------------------------------- |
 | `/ob-init`        | Initialize the project. Asks greenfield vs brownfield, then activates the agent team. Supports skipping doc generation for new projects. |
-| `/ob-plan <url>`  | Parse a user story URL and produce a plan, proposal, specs, and tasks. Stops before implementation. Use platform mode, not `None`.   |
+| `/ob-plan <url>`  | Parse a user story URL and produce a plan, proposal, specs, and tasks. Stops before implementation. Use platform mode, not `None`.   |
 | `/ob-main <task>` | Quick direct implementation, no OpenSpec, no ensemble, no PRs. Just do it.                            |
 | `/ob-create-engineer <name> "<description>"` | Create a custom engineer agent from a description, with skills auto-installed from [skills.sh](https://www.skills.sh/) |
 | `/ob-create-architecture` | Generate or regenerate `ARCHITECTURE.md` from the codebase. Safe to rerun any time the architecture changes. |
@@ -123,14 +123,14 @@ devops-manager     lead/orchestrator, planning, PR lifecycle
 basic-engineer     implementation worker, ability-driven
 ```
 
-`basic-engineer` behavior is composed by abilities, not hardcoded role silos.
-Project-specific specialization comes from user-created custom engineers via `/ob-create-engineer`. During `/opsx-apply`, the lead should inspect the engineers that actually exist in `.opencode/agents/`, prefer matching custom engineers, and fall back to `basic-engineer` only when no specialist is a clear fit.
+`basic-engineer` behavior is composed by abilities, not hardcoded role silos.
+Project-specific specialization comes from user-created custom engineers via `/ob-create-engineer`. During `/opsx-apply`, the lead should inspect the engineers that actually exist in `.opencode/agents/`, prefer matching custom engineers, and fall back to `basic-engineer` only when no specialist is a clear fit.
 
-### Skills, platform knowledge
-
-Skills define _what to know_. They provide project rules, platform behavior, and task-specific execution guidance. Agents auto-detect/load relevant skills; **you do not manually choose skills per prompt**.
-
-If you choose platform `None` during onboarding, no userstory or pull-request platform skills are injected into the workflow. The project works from direct conversation, local repo context, and optional OpenSpec artifacts only.
+### Skills, platform knowledge
+
+Skills define _what to know_. They provide project rules, platform behavior, and task-specific execution guidance. Agents auto-detect/load relevant skills; **you do not manually choose skills per prompt**.
+
+If you choose platform `None` during onboarding, no userstory or pull-request platform skills are injected into the workflow. The project works from direct conversation, local repo context, and optional OpenSpec artifacts only.
 
 Current loading model:
 
@@ -179,7 +179,7 @@ Models are fetched live from [models.dev](https://models.dev) (3000+ models, cac
 
 ## The pipeline
 
-When you give the lead agent a work item URL, execution follows this pipeline. If onboarding platform is `None`, skip the work item / PR stages and work directly from conversation plus optional OpenSpec artifacts:
+When you give the lead agent a work item URL, execution follows this pipeline. If onboarding platform is `None`, skip the work item / PR stages and work directly from conversation plus optional OpenSpec artifacts:
 
 ```
 devops-manager (load ob-global first)
@@ -218,7 +218,7 @@ Each agent runs in its own isolated git worktree via [OpenCode Ensemble](https:/
 
 ```
 your-project/
-├── AGENTS.md                        ← bootstrap mode, replaced after first "init"
+├── AGENTS.md                        ← bootstrap mode, replaced after first "/ob-init"
 ├── ARCHITECTURE.md                  ← prompt for agents to fill in from your codebase
 ├── DESIGN.md                        ← prompt for agents to fill in from your codebase
 ├── .opencode/

package/content/.opencode/agents/basic-engineer.md

@@ -1,7 +1,7 @@
 ---
 description: Basic Engineer Agent.
 mode: primary
-color: #68A063
+color: success
 permission:
   edit: allow
   bash: allow

package/content/.opencode/agents/devops-manager.md

@@ -1,7 +1,7 @@
 ---
 description: Process agent. Reads work items and user stories at pipeline start. Creates PRs, posts screenshots, responds to review comments at pipeline end. Bridges the work tracker and the repository. Platform knowledge comes from skills.
-mode: primary
-color: #690a69
+mode: subagent
+color: primary
 permission:
   edit: allow
   bash: allow

package/content/.opencode/commands/ob-create-engineer.md

@@ -46,7 +46,7 @@ Example: `/ob-create-engineer frontend-engineer "A frontend engineer specialized
    ---
    description: <description>
    mode: primary
-   color: <pick a unique hex color>
+   color: <pick a theme color: primary|secondary|accent|success|warning|error|info>
    permission:
      edit: allow
      bash: allow

package/content/AGENTS.md

@@ -6,7 +6,7 @@
 
 ## Trigger
 
-When the user says anything resembling initialization, "init", "initialize", "setup", "start", "bootstrap", "get started", "prepare", execute the steps below. Follow the greenfield/brownfield branching exactly.
+When the user says anything resembling initialization, "/ob-init", "initialize", "setup", "start", "bootstrap", "get started", "prepare", execute the steps below. Follow the greenfield/brownfield branching exactly.
 
 ---
 
@@ -174,10 +174,10 @@ Source scope is defined by mandatory `ob-global` skill.
 - Follow the generated `## Source Roots` section from that skill.
 - Do not duplicate source-scope rules here.
 
-## I Am the Lead, Full Workflow Ownership
-
-<!-- OB-PLATFORM-WORKFLOW-START -->
-When the user provides a work item URL or says "implement the plan" or "I've added comments to the PR", **I own the full lifecycle**. I load `ob-global` skill first, then the appropriate userstory skill, and use ensemble tools to coordinate the agent team.
+## I Am the Lead, Full Workflow Ownership
+
+<!-- OB-PLATFORM-WORKFLOW-START -->
+When the user provides a work item URL or says "implement the plan" or "I've added comments to the PR", **I own the full lifecycle**. I load `ob-global` skill first, then the appropriate userstory skill, and use ensemble tools to coordinate the agent team.
 
 Trigger patterns, I recognize ALL of these, exact wording does not matter:
 - User pastes or mentions a GitHub Issue URL → load `ob-userstory-gh` skill → parse issue → run `/opsx-propose` → confirm with user → run `/opsx-apply` → ship
@@ -186,20 +186,20 @@ Trigger patterns, I recognize ALL of these, exact wording does not matter:
 - `I've added comments to the PR` → read PR comments → fix → update PR
 - Any GitHub/Azure DevOps PR URL in a feedback/fix request (e.g. "check comments", "fix PR feedback") → run PR Feedback Loop
 
-**A GitHub or Azure DevOps URL anywhere in the user's message is always a trigger, regardless of surrounding words.**
-<!-- OB-PLATFORM-WORKFLOW-END -->
-
-**Never delegate without a plan. Default to specialists for implementation. If ensemble is clearly non-functional in the current session (idle teammate, no claim, or repeated spawn failure after one retry), stop forcing it: report the failure, then continue in the main session or ask the user whether to retry later.**
-
-## Engineer Selection
-
-Before spawning implementation workers:
-- Inspect `.opencode/agents/*.md` and build the list of engineers that actually exist in this project.
-- Exclude `devops-manager` from implementation selection.
-- Prefer the most specialized custom engineer whose description and abilities clearly match the task domain.
-- Use `basic-engineer` only when no custom engineer is a clear fit or as a recovery fallback.
-- Never spawn engineer names that are not present in `.opencode/agents/`.
-- When multiple engineers could fit, choose the narrower specialist before the generalist.
+**A GitHub or Azure DevOps URL anywhere in the user's message is always a trigger, regardless of surrounding words.**
+<!-- OB-PLATFORM-WORKFLOW-END -->
+
+**Never delegate without a plan. Default to specialists for implementation. If ensemble is clearly non-functional in the current session (idle teammate, no claim, or repeated spawn failure after one retry), stop forcing it: report the failure, then continue in the main session or ask the user whether to retry later.**
+
+## Engineer Selection
+
+Before spawning implementation workers:
+- Inspect `.opencode/agents/*.md` and build the list of engineers that actually exist in this project.
+- Exclude `devops-manager` from implementation selection.
+- Prefer the most specialized custom engineer whose description and abilities clearly match the task domain.
+- Use `basic-engineer` only when no custom engineer is a clear fit or as a recovery fallback.
+- Never spawn engineer names that are not present in `.opencode/agents/`.
+- When multiple engineers could fit, choose the narrower specialist before the generalist.
 
 ## Multi-Agent Execution, opencode-ensemble
 
@@ -218,10 +218,10 @@ Core tools used in this workflow:
 - **Max {{MAX_CONCURRENT_AGENTS}} truly concurrent agents.** All {{MAX_CONCURRENT_AGENTS}} must be spawned and running simultaneously, not sequentially. Spawn in waves if more than {{MAX_CONCURRENT_AGENTS}} are needed. Wait for wave N to finish before spawning wave N+1.
 - **Non-overlapping file domains.** Each agent owns exclusive directories. Two agents must NEVER touch the same file.
 - **Immediate shutdown on completion.** The moment an agent's domain has no more pending tasks → `team_shutdown` → `team_merge`. Keep agents alive if more tasks in their domain are pending (rolling batch).
-- **Rolling batch assignment.** Agents receive up to 3 tasks initially. When they complete a batch, lead assigns the next batch of up to 3 from the board. Never leave pending tasks orphaned.
-- **Stall detection at 5 minutes.** No commits after 5 min → nudge message → 2 min grace → force shutdown + respawn.
-- **Idle-without-claim is an earlier stall.** If a spawned teammate sits idle with no claimed task after a short wait, resend one short claim-only message with the exact task IDs. If still idle, force shutdown + respawn once with a shorter prompt. If the retry repeats the same failure, treat ensemble as unavailable for that session and stop recycling equivalent workers.
-- **Retry limit.** Max 3 retries per failing task → stop-and-report to user. Never retry indefinitely.
+- **Rolling batch assignment.** Agents receive up to 3 tasks initially. When they complete a batch, lead assigns the next batch of up to 3 from the board. Never leave pending tasks orphaned.
+- **Stall detection at 5 minutes.** No commits after 5 min → nudge message → 2 min grace → force shutdown + respawn.
+- **Idle-without-claim is an earlier stall.** If a spawned teammate sits idle with no claimed task after a short wait, resend one short claim-only message with the exact task IDs. If still idle, force shutdown + respawn once with a shorter prompt. If the retry repeats the same failure, treat ensemble as unavailable for that session and stop recycling equivalent workers.
+- **Retry limit.** Max 3 retries per failing task → stop-and-report to user. Never retry indefinitely.
 
 **Progress inspection commands (tell user explicitly after spawning):**
 - `team_status` for live team snapshot
@@ -236,12 +236,12 @@ If a teammate stalls due to model quota/rate-limit exhaustion:
 
 ---
 
-## Pipeline
-
-<!-- OB-PLATFORM-PIPELINE-START -->
-```
-devops-manager (lead mode)
-  → load ob-global + parse work item via skill
+## Pipeline
+
+<!-- OB-PLATFORM-PIPELINE-START -->
+```
+devops-manager (lead mode)
+  → load ob-global + parse work item via skill
         ↓
   openspec-propose
   → proposal.md + specs + tasks
@@ -269,11 +269,11 @@ devops-manager (ship mode)
 
 ```
 0. Run /quota to check remaining budget before spawning.
-1. Run /opsx-apply.
-   - Step 5b: classify cost tier, announce scope, ask user to confirm if ≥4 tasks.
-   - Lead adds all tasks to board.
-   - When dependencies exist, lead uses multiple `team_tasks_add` waves so later tasks can reference real task IDs returned by earlier waves.
-   - Lead discovers available engineers from `.opencode/agents/*.md`, prefers matching custom engineers, then spawns engineers with initial batch of up to 3 tasks each (rolling batch model).
+1. Run /opsx-apply.
+   - Step 5b: classify cost tier, announce scope, ask user to confirm if ≥4 tasks.
+   - Lead adds all tasks to board.
+   - When dependencies exist, lead uses multiple `team_tasks_add` waves so later tasks can reference real task IDs returned by earlier waves.
+   - Lead discovers available engineers from `.opencode/agents/*.md`, prefers matching custom engineers, then spawns engineers with initial batch of up to 3 tasks each (rolling batch model).
    - Each engineer claims tasks, implements, completes, messages lead.
    - Lead assigns next batch (up to 3) to agents that report done. Repeat until board empty.
    - Lead merges each engineer branch after shutdown, then marks tasks done in tasks.md.
@@ -306,10 +306,10 @@ When user says "I've added comments to the PR" or asks to fix PR comments from P
 6. Wait for engineer results → team_shutdown + team_merge per engineer
 7. Run verification tasks (tests/build/lint) and fix blockers if any
 8. team_spawn devops-manager (ship mode) with "push + update PR threads" task ID + team_message "Start now"
-9. Wait → team_results → report what was updated
-10. team_cleanup
-```
-<!-- OB-PLATFORM-PIPELINE-END -->
+9. Wait → team_results → report what was updated
+10. team_cleanup
+```
+<!-- OB-PLATFORM-PIPELINE-END -->
 
 ---
 
@@ -322,7 +322,7 @@ All agents are universal, no project-specific knowledge. Platform and tech knowl
 | `devops-manager` | .opencode/agents/devops-manager.md | Reads work items, creates PRs, handles review feedback |
 | `basic-engineer` | .opencode/agents/basic-engineer.md | Generic implementation worker using ability-loaded skills |
 
-User can add more custom engineer agents and run them in parallel. Keep behavior ability-driven via skill mappings. Custom engineers are the primary specialization mechanism; `basic-engineer` is the general fallback when no custom engineer is a clear fit.
+User can add more custom engineer agents and run them in parallel. Keep behavior ability-driven via skill mappings. Custom engineers are the primary specialization mechanism; `basic-engineer` is the general fallback when no custom engineer is a clear fit.
 
 Default `basic-engineer` abilities:
 
@@ -336,7 +336,7 @@ Default `basic-engineer` abilities:
 
 ## Skills
 
-Skills provide platform and tech-specific knowledge. Agents usually detect and load them automatically. Prefer auto-detection, but explicitly naming a skill in a spawn prompt is allowed when a workflow requires it or repeated misses show the agent is not loading the right context.
+Skills provide platform and tech-specific knowledge. Agents usually detect and load them automatically. Prefer auto-detection, but explicitly naming a skill in a spawn prompt is allowed when a workflow requires it or repeated misses show the agent is not loading the right context.
 
 `ob-global` is always loaded first, it provides baseline rules for all agents.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-onboard",
-  "version": "0.4.14",
+  "version": "0.4.15",
   "description": "Prepare any brownfield codebase for AI agent workflows using OpenCode, OpenSpec, and ensemble orchestration.",
   "keywords": [
     "opencode",

package/src/commands/wizard.js

@@ -111,7 +111,7 @@ export async function runWizard(version) {
   console.log(chalk.bold.green('━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━'))
   console.log()
   console.log('  Open this project in OpenCode and type:')
-  console.log(chalk.bold('  "init"'))
+  console.log(chalk.bold('  "/ob-init"'))
   console.log()
   if (toGenerate.length > 0) {
     console.log(`  OpenCode will generate ${toGenerate.join(' and ')}`)

package/src/steps/openspec/index.js

@@ -1,6 +1,6 @@
 import { execa } from "execa"
 import path from "node:path"
-import { commandExists, error, header, info, loading, success, warn} from "../../utils/exec.js"
+import { commandExists, error, header, info, loading, success, warn } from "../../utils/exec.js"
 import { APPLY_TARGETS, patchApplyFile } from "./ensemble.js"
 
 export const openspecSteps = {
@@ -58,7 +58,7 @@ async function install() {
     success("OpenSpec installed")
   } catch (err) {
     error(`Failed to run openspec install: ${err.message}`)
-  }  
+  }
 }
 
 async function check() {
@@ -77,7 +77,7 @@ async function init() {
   try {
     const result = await execa(
       "npx",
-      ["@fission-ai/openspec", "init", "--tools", "opencode", "--force"],
+      ["@fission-ai/openspec", "/ob-init", "--tools", "opencode", "--force"],
       {
         cwd: process.cwd(),
         stdio: "pipe",