opencode-onboard 0.3.3 → 0.4.2

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

@@ -19,30 +19,28 @@ Process agent, reads work items, creates PRs, handles review feedback. Bookends
 
 Work item and issue reading, PR creation, PR comment reading and classification, PR updates, screenshot capture of local running app, branch verification. Does not write application code. Platform knowledge (GitHub, Azure DevOps, etc.) comes entirely from loaded skills.
 
-## RTK, MANDATORY
+## Skills and Platform Resolution
 
-Use `rtk` for ALL CLI commands. Never run commands directly.
+Skills are located in `.agents/skills/`. Load required skills explicitly from context and onboarding metadata.
 
-- `rtk gh pr create` NOT `gh pr create`
-- `rtk az repos pr create` NOT `az repos pr create`
-- `rtk git push` NOT `git push`
+Always load `@ob-global` FIRST before any other skill.
 
-If `rtk` is not available, report it as a blocker. Do not run commands without it.
-
-## Skills, Auto-Detection
-
-Skills are located in `.agents/skills/`. Detect and use relevant skills automatically, the user will never tell you which skill to use.
+Platform skill selection must follow onboarding platform choice from CLI step:
+<!-- OB-PLATFORM-SKILLS-START -->
+- Platform-specific skill instructions are injected during onboarding copy step.
+<!-- OB-PLATFORM-SKILLS-END -->
 
 1. If the spawn prompt lists specific skills to load, read those `SKILL.md` files FIRST before any implementation
 2. Additionally, identify the platform from URLs or context
 
 Examples of intent → skill mapping:
-- URL contains `dev.azure.com` or `visualstudio.com` → look for `ob-userstory-az` or `ob-pullrequest-az`
-- URL contains `github.com` → look for `ob-userstory-gh` or `ob-pullrequest-gh`
-- "create PR" or "ship" → look for a pullrequest skill matching the platform
-- "PR has comments" or "review feedback" → look for a pullrequest observer skill
+- "read issue/work item" → load platform userstory skill
+- "create PR" or "ship" → load platform pullrequest skill
+- "PR has comments" or "review feedback" → load platform pullrequest observer skill
+- URL-based platform inference is fallback-only when onboarding metadata is unavailable
 
 Rules:
+- Platform selected in onboarding metadata takes precedence over URL inference when both exist
 - Never interact with a platform without loading the matching skill first
 - Follow skill instructions exactly, do not partially apply them
 - If no skill exists for the platform, report it as a blocker rather than improvising
@@ -51,25 +49,36 @@ Rules:
 ## Two Modes
 
 ### Read Mode (pipeline start)
-1. Identify the platform from the URL
-2. Load the matching userstory skill
-3. Fetch and parse the work item
-4. Output structured summary for the lead
+1. Load `@ob-global` first
+2. Resolve platform from `.opencode/opencode-onboard.json` (`wizard.platform`) when available; fallback to URL inference only if missing/ambiguous
+3. Load the matching userstory skill for that resolved platform
+4. Fetch and parse the work item
+5. Output structured summary for the lead
 
 ### Ship Mode (pipeline end)
-1. Verify all changes are on a feature branch, never `main`
-2. Load the matching pullrequest skill
-3. Capture screenshots of local running app if UI changes exist
-4. Read `.agents/session-log.json` if it exists, parse the JSON array and include a "Session Activity" section in the PR description with agent names, task counts, and skills used
-5. Commit and push the feature branch. If `## Source Roots` lists multiple roots, each root is a separate git repository — create and push the feature branch in EACH repo that has changes; never assume a single repo
-6. Create the PR following the skill instructions (one PR per repo that has changes)
-7. Post PR comment with screenshots and change summary
-8. Report PR URL to the lead
+1. Load `@ob-global` first
+2. Verify all changes are on a feature branch, never `main`
+3. Resolve platform from `.opencode/opencode-onboard.json` (`wizard.platform`) when available; fallback to URL inference only if missing/ambiguous
+4. Load the matching pullrequest skill for that resolved platform
+5. Capture screenshots of local running app if UI changes exist
+6. Read `.agents/session-log.json` if it exists, parse the JSON array and include a "Session Activity" section in the PR description with agent names, task counts, and skills used
+7. Commit and push the feature branch. If `## Source Roots` lists multiple roots, each root is a separate git repository, create and push the feature branch in EACH repo that has changes; never assume a single repo
+8. Create the PR following the skill instructions (one PR per repo that has changes)
+9. Post PR comment with screenshots and change summary
+10. Report PR URL to the lead
 
 ### Feedback Mode (PR review loop)
-1. Load the matching pullrequest observer skill
-2. Read and classify all PR comments
-3. Report classified feedback to the lead, do not implement fixes
+1. Load `@ob-global` first
+2. Resolve platform from `.opencode/opencode-onboard.json` (`wizard.platform`) when available; fallback to URL inference only if missing/ambiguous
+3. Load the matching pullrequest observer skill for that resolved platform
+4. Read and classify all PR comments
+5. Report classified feedback to the lead, do not implement fixes
+
+## Worker Model Coordination
+
+- Implementation is performed by `basic-engineer` and/or user-defined custom engineers.
+- Multiple engineer workers can run in parallel when task dependencies allow.
+- DevOps Manager orchestrates process, routing, and shipping; it does not implement application code.
 
 ## Constraints
 

package/content/.agents/session-log.json

@@ -0,0 +1,41 @@
+[
+  {
+    "ts": "2026-05-04T21:04:09.899Z",
+    "agent": "lead",
+    "member": null,
+    "agentType": null,
+    "team": null,
+    "action": "started",
+    "sessionId": "ses_20b31c36cffeBfsYI2hJ1BNcM5"
+  },
+  {
+    "ts": "2026-05-04T21:04:26.180Z",
+    "agent": "lead",
+    "member": null,
+    "agentType": null,
+    "team": null,
+    "action": "skill-loaded",
+    "skill": "ob-userstory-gh",
+    "source": "read-skill-file"
+  },
+  {
+    "ts": "2026-05-04T21:04:47.306Z",
+    "agent": "lead",
+    "member": null,
+    "agentType": null,
+    "team": null,
+    "action": "completed",
+    "filesEdited": 0,
+    "skills": [
+      "ob-userstory-gh"
+    ],
+    "usage": {
+      "inputTokensReported": null,
+      "outputTokensReported": null,
+      "totalTokensReported": null,
+      "tokenEstimateLow": 3469,
+      "tokenEstimateHigh": 6940,
+      "method": "heuristic"
+    }
+  }
+]

package/content/.agents/skills/ob-default/SKILL.md

@@ -0,0 +1,21 @@
+Fallback skill, used when no other skill matches. Still loads ob-global for baseline rules.
+
+## When used
+
+- No other skill matches the user's request
+- Task is unclear or ambiguous
+- Load ob-global first for baseline rules
+
+## Approach
+
+1. **Understand the ask**, Clarify if ambiguous
+2. **Check existing context**, Read DESIGN.md, ARCHITECTURE.md first
+3. **Start small**, MVP, iterate
+4. **Verify**, Run tests + build before claiming done
+5. **Report results**, Show what was done, what remains
+
+## Communication
+
+- Ask for clarification if unclear
+- Report blockers immediately
+- Show progress when asked

package/content/.agents/skills/ob-generic-guardrails/SKILL.md

@@ -0,0 +1,32 @@
+Generic guardrails, foundational rules that all agents follow. Users add specialized guardrails skills for specific concerns.
+
+## Git
+
+- NEVER commit or push to main
+- NEVER force push
+- NEVER merge PRs (human-only)
+- Feature branches only: `feature/*` or `bugfix/*`
+
+## Secrets
+
+- NEVER read or output .env files
+- NEVER log credentials, API keys, tokens
+- NEVER commit secrets to git
+
+## Code
+
+- Run tests before marking done
+- Run lint/build before pushing
+- Keep changes small and focused
+
+## Security
+
+- Validate all inputs
+- Escape all outputs
+- No hardcoded credentials
+
+## Communication
+
+- Ask for clarification if unclear
+- Report blockers immediately
+- Show progress when asked

package/content/.agents/skills/ob-global/SKILL.md

@@ -0,0 +1,49 @@
+Generic skill, common project-level guidance loaded by all agents. Provides baseline rules; specialized skills add specific concerns.
+
+## When loaded
+
+Load this skill first in any session. All other skills add to it, never replace it.
+
+## Context
+
+- Load DESIGN.md first for design principles and guidelines.
+- Load ARCHITECTURE.md for system architecture and component interactions.
+
+## Source Roots
+
+<!-- OB-SOURCE-ROOTS-START -->
+Source roots are generated during onboarding from the user's source-scope selection.
+Read and analyze code ONLY from those generated roots.
+
+If multiple roots are generated, each root is an independent git repository. Branch, commit, push, and PR operations must be handled per repository.
+<!-- OB-SOURCE-ROOTS-END -->
+
+## Git Guardrails
+
+- NEVER commit or push to main
+- NEVER force push
+- NEVER merge PRs (human-only)
+- Feature branches only: `feature/*` or `bugfix/*`
+
+## Secrets Guardrails
+
+- NEVER read or output .env files
+- NEVER log credentials, API keys, tokens
+- NEVER commit secrets to git
+
+## Code Quality
+
+- Run tests before marking done
+- Run lint/build before pushing
+- Keep changes small and focused
+- Ask for clarification if unclear
+
+## Token Optimization Rules
+
+<!-- OB-RTK-START -->
+RTK rules are generated here when RTK is selected during onboarding.
+<!-- OB-RTK-END -->
+
+<!-- OB-CAVEMAN-START -->
+Caveman rules are generated here when Caveman is selected during onboarding.
+<!-- OB-CAVEMAN-END -->

package/content/.agents/skills/ob-pullrequest-az/SKILL.md

@@ -8,16 +8,6 @@ metadata:
   version: "1.0"
 ---
 
-**RTK - MANDATORY**
-
-Use `rtk` wrapper for ALL CLI commands:
-- `rtk git add` NOT `git add`
-- `rtk git commit` NOT `git commit`
-- `rtk git push` NOT `git push`
-- `rtk az repos pr create` NOT `az repos pr create`
-- `rtk az repos pr work-item add` NOT `az repos pr work-item add`
-- `rtk az devops invoke` NOT `az devops invoke`
-
 **Browser MCP tools are FORBIDDEN for all Azure DevOps operations.**
 Browser tools are ONLY permitted for screenshots of the LOCAL running app on `localhost` URLs.
 
@@ -30,7 +20,7 @@ Triggered when devops-manager is in ship mode after implementation is complete.
 ### Step 1: Verify feature branch
 
 ```bash
-rtk git branch --show-current
+git branch --show-current
 ```
 
 Branch must be `feature/{id}-{slug}`. NEVER push to `main`.
@@ -48,15 +38,15 @@ Save to: `openspec/changes/{change-name}/images/{feature}.png`
 ### Step 3: Commit and push
 
 ```bash
-rtk git add .
-rtk git commit -m "feat(#{id}): {description}"
-rtk git push origin feature/{id}-{slug}
+git add .
+git commit -m "feat(#{id}): {description}"
+git push origin feature/{id}-{slug}
 ```
 
 ### Step 4: Create PR
 
 ```bash
-rtk az repos pr create \
+az repos pr create \
   --repository {repo} \
   --source-branch feature/{id}-{slug} \
   --target-branch main \
@@ -67,7 +57,7 @@ rtk az repos pr create \
 ### Step 5: Link work item (MANDATORY, run sequentially, not in parallel)
 
 ```bash
-rtk az repos pr work-item add --id {pr-id} --work-items {workitem-id}
+az repos pr work-item add --id {pr-id} --work-items {workitem-id}
 ```
 
 ### Step 6: Post screenshot comment
@@ -79,7 +69,7 @@ https://dev.azure.com/{org}/{project}/_apis/git/repositories/{repo}/items?path=o
 
 Post via:
 ```bash
-rtk az devops invoke \
+az devops invoke \
   --area git --resource pullRequestThreads \
   --route-parameters project={project} repositoryId={repo} pullRequestId={pr-id} \
   --http-method POST --api-version 7.1 --in-file body.json
@@ -107,13 +97,13 @@ Triggered when user says "I've added comments to the PR" or "check PR feedback".
 
 If PR link provided, extract ID from URL. Otherwise:
 ```bash
-rtk az repos pr list --repository {repo} --status active --top 1
+az repos pr list --repository {repo} --status active --top 1
 ```
 
 ### Step 2: Read comment threads
 
 ```bash
-rtk az devops invoke \
+az devops invoke \
   --area git --resource pullRequestThreads \
   --route-parameters project={project} repositoryId={repo} pullRequestId={id} \
   --http-method GET --api-version 7.1
@@ -131,7 +121,7 @@ rtk az devops invoke \
 ### Step 4: Update openspec (if spec-update)
 
 ```bash
-rtk git branch --show-current
+git branch --show-current
 # feature/193208-roles-crud → change: us-193208-roles-crud
 ```
 
@@ -140,7 +130,7 @@ Update: `openspec/changes/{change}/proposal.md`, `design.md`, or `tasks.md` as a
 ### Step 5: Reply to each thread
 
 ```bash
-rtk az devops invoke \
+az devops invoke \
   --area git --resource pullRequestThreadComments \
   --route-parameters project={project} repositoryId={repo} pullRequestId={id} threadId={tid} \
   --http-method POST --api-version 7.1 --in-file reply.json

package/content/.agents/skills/ob-pullrequest-gh/SKILL.md

@@ -8,16 +8,6 @@ metadata:
   version: "1.0"
 ---
 
-**RTK - MANDATORY**
-
-Use `rtk` wrapper for ALL CLI commands:
-- `rtk git add` NOT `git add`
-- `rtk git commit` NOT `git commit`
-- `rtk git push` NOT `git push`
-- `rtk gh pr create` NOT `gh pr create`
-- `rtk gh pr comment` NOT `gh pr comment`
-- `rtk gh api` NOT `gh api`
-
 **ALL GitHub data MUST come from `gh` CLI. NEVER use webfetch, HTTP requests, or browser MCP tools for GitHub operations, even if gh CLI fails. If `gh` is unavailable, report as a blocker.**
 Always pass `--repo {owner}/{repo}` explicitly, never rely on git context to resolve the repo.
 
@@ -30,7 +20,7 @@ Triggered when devops-manager is in ship mode after implementation is complete.
 ### Step 1: Verify feature branch
 
 ```bash
-rtk git branch --show-current
+git branch --show-current
 ```
 
 Branch must be `feature/{id}-{slug}`. NEVER push to `main`.
@@ -48,15 +38,15 @@ Save to: `openspec/changes/{change-name}/images/{feature}.png`
 ### Step 3: Commit and push
 
 ```bash
-rtk git add .
-rtk git commit -m "feat(#{id}): {description}"
-rtk git push origin feature/{slug}
+git add .
+git commit -m "feat(#{id}): {description}"
+git push origin feature/{slug}
 ```
 
 ### Step 4: Create PR
 
 ```bash
-rtk gh pr create \
+gh pr create \
   --base main \
   --head feature/{slug} \
   --title "feat: {title}" \
@@ -67,7 +57,7 @@ rtk gh pr create \
 
 Resolve commit SHA (the commit that includes screenshots):
 ```bash
-rtk git rev-parse HEAD
+git rev-parse HEAD
 ```
 
 Build blob URL for each image (preferred, stable in PR discussion):
@@ -77,7 +67,7 @@ https://github.com/{owner}/{repo}/blob/{sha}/openspec/changes/{change}/images/{f
 
 Post comment:
 ```bash
-rtk gh pr comment {pr-number} --repo {owner}/{repo} --body $'## Screenshots\n\n![{feature}]({blob-url})'
+gh pr comment {pr-number} --repo {owner}/{repo} --body $'## Screenshots\n\n![{feature}]({blob-url})'
 ```
 
 ---
@@ -90,16 +80,16 @@ Triggered when user says "I've added comments to the PR" or "check PR feedback".
 
 If PR link provided, extract number from URL. Otherwise:
 ```bash
-rtk gh pr list --repo {owner}/{repo} --state open --limit 1
+gh pr list --repo {owner}/{repo} --state open --limit 1
 ```
 
 ### Step 2: Read comment threads
 
 ```bash
-rtk gh pr view {pr-number} --repo {owner}/{repo} --comments
+gh pr view {pr-number} --repo {owner}/{repo} --comments
 # Or structured output:
-rtk gh api repos/{owner}/{repo}/pulls/{pr-number}/comments
-rtk gh api repos/{owner}/{repo}/pulls/{pr-number}/reviews
+gh api repos/{owner}/{repo}/pulls/{pr-number}/comments
+gh api repos/{owner}/{repo}/pulls/{pr-number}/reviews
 ```
 
 ### Step 3: Categorize feedback
@@ -114,7 +104,7 @@ rtk gh api repos/{owner}/{repo}/pulls/{pr-number}/reviews
 ### Step 4: Update openspec (if spec-update)
 
 ```bash
-rtk git branch --show-current
+git branch --show-current
 # feature/add-user-auth → change: add-user-auth
 ```
 
@@ -124,12 +114,12 @@ Update: `openspec/changes/{change}/proposal.md`, `design.md`, or `tasks.md` as a
 
 ```bash
 # Reply to a review comment
-rtk gh api repos/{owner}/{repo}/pulls/{pr-number}/comments/{comment-id}/replies \
+gh api repos/{owner}/{repo}/pulls/{pr-number}/comments/{comment-id}/replies \
   --method POST \
   --field body="Acknowledged, applying this change now."
 
 # Or post a general PR comment
-rtk gh pr comment {pr-number} --body "Updated design.md to reflect feedback."
+gh pr comment {pr-number} --body "Updated design.md to reflect feedback."
 ```
 
 ---

package/content/.agents/skills/ob-userstory-az/SKILL.md

@@ -8,12 +8,6 @@ metadata:
   version: "3.1"
 ---
 
-**RTK - MANDATORY**
-
-Use `rtk` wrapper for ALL CLI commands:
-- `rtk az boards work-item show` NOT `az boards work-item show`
-- `rtk openspec new change` NOT `openspec new change`
-
 **Browser MCP tools are FORBIDDEN for all Azure DevOps operations.**
 
 ---
@@ -40,7 +34,7 @@ Create with scopes: **Work Items (Read & Write)** + **Code (Read & Write)**
 
 2. **Fetch Work Item**
    ```bash
-   rtk az boards work-item show --id 193208
+   az boards work-item show --id 193208
    ```
    Do NOT use `--organization` flag (uses default org).
 
@@ -54,7 +48,7 @@ Create with scopes: **Work Items (Read & Write)** + **Code (Read & Write)**
 
 4. **Create OpenSpec Change**
    ```bash
-   rtk openspec new change "us-{id}-{slug}"
+   openspec new change "us-{id}-{slug}"
    ```
 
 ---
@@ -66,28 +60,28 @@ Use these for ALL DevOps operations, browser MCP is FORBIDDEN.
 ### Work Items
 ```bash
 # Read work item
-rtk az boards work-item show --id <id>
+az boards work-item show --id <id>
 
 # Update work item state
-rtk az boards work-item update --id <id> --state "Active"
+az boards work-item update --id <id> --state "Active"
 ```
 
 ### PR Threads (Comments)
 ```bash
 # Read all threads
-rtk az devops invoke \
+az devops invoke \
   --area git --resource pullRequestThreads \
   --route-parameters project={project} repositoryId=<repo> pullRequestId=<id> \
   --http-method GET --api-version 7.1
 
 # Post new comment thread (requires body.json)
-rtk az devops invoke \
+az devops invoke \
   --area git --resource pullRequestThreads \
   --route-parameters project={project} repositoryId=<repo> pullRequestId=<id> \
   --http-method POST --api-version 7.1 --in-file body.json
 
 # Reply to existing thread
-rtk az devops invoke \
+az devops invoke \
   --area git --resource pullRequestThreadComments \
   --route-parameters project={project} repositoryId=<repo> pullRequestId=<id> threadId=<tid> \
   --http-method POST --api-version 7.1 --in-file reply.json
@@ -165,7 +159,7 @@ After outputting the above, the lead MUST run `/opsx-propose` to generate the pr
 ## Guardrails
 
 - ✅ Parse Azure DevOps URL and create OpenSpec change
-- ✅ Use `rtk` for all Azure CLI operations
+- ✅ Use `az` CLI for all Azure DevOps operations
 - ✅ Always run `/opsx-propose` after parsing, never skip to implementation
 - ✅ Always stop and confirm with user after propose, before running `/opsx-apply`
 - ❌ Browser MCP tools for Azure DevOps operations, FORBIDDEN

package/content/.agents/skills/ob-userstory-gh/SKILL.md

@@ -8,14 +8,6 @@ metadata:
   version: "1.1"
 ---
 
-**RTK - MANDATORY**
-
-Use `rtk` wrapper for ALL CLI commands:
-- `rtk gh issue view` NOT `gh issue view`
-- `rtk gh issue list` NOT `gh issue list`
-- `rtk gh issue edit` NOT `gh issue edit`
-- `rtk openspec new change` NOT `openspec new change`
-
 **ALL GitHub data MUST come from `gh` CLI. NEVER use webfetch, HTTP requests, or browser MCP tools to fetch GitHub URLs, even if gh CLI fails. If `gh` is unavailable, report it as a blocker.**
 
 ---
@@ -41,7 +33,7 @@ gh auth status
 
 2. **Fetch Issue**, always pass `--repo` explicitly, never rely on git context:
    ```bash
-   rtk gh issue view 42 --repo {owner}/{repo} --json number,title,body,labels,milestone,state
+   gh issue view 42 --repo {owner}/{repo} --json number,title,body,labels,milestone,state
    ```
    If this returns an auth error or 404, report as a blocker, do NOT fall back to webfetch or web search.
 
@@ -55,7 +47,7 @@ gh auth status
 
 4. **Create OpenSpec Change**
    ```bash
-   rtk openspec new change "gh-{number}-{slug}"
+   openspec new change "gh-{number}-{slug}"
    ```
 
 ---
@@ -67,13 +59,13 @@ Use these for ALL GitHub operations, browser MCP and webfetch are FORBIDDEN. Alw
 ### Issues
 ```bash
 # Read issue
-rtk gh issue view <number> --repo {owner}/{repo}
+gh issue view <number> --repo {owner}/{repo}
 
 # List open issues
-rtk gh issue list --repo {owner}/{repo} --state open --limit 10
+gh issue list --repo {owner}/{repo} --state open --limit 10
 
 # Update issue
-rtk gh issue edit <number> --repo {owner}/{repo} --add-label "in-progress"
+gh issue edit <number> --repo {owner}/{repo} --add-label "in-progress"
 ```
 
 ---
@@ -129,7 +121,7 @@ After outputting the above, the lead MUST run `/opsx-propose` to generate the pr
 ## Guardrails
 
 - ✅ Parse GitHub Issue URL and create OpenSpec change
-- ✅ Use `rtk gh` for all GitHub CLI operations
+- ✅ Use `gh` CLI for all GitHub operations
 - ✅ Always run `/opsx-propose` after parsing, never skip to implementation
 - ✅ Always stop and confirm with user after propose, before running `/opsx-apply`
 - ❌ `webfetch` or HTTP requests to GitHub URLs, FORBIDDEN, use `gh` CLI only

package/content/.opencode/commands/init.md

@@ -0,0 +1,8 @@
+---
+description: Initialize the project — runs the bootstrap sequence defined in AGENTS.md if not yet initialized.
+---
+
+Check if `AGENTS.md` is in bootstrap mode (contains `<!-- AGENTS-TEMPLATE-START -->`).
+
+- If yes: run the full initialization sequence defined in `AGENTS.md` now.
+- If no: tell the user the project is already initialized.

package/content/.opencode/commands/main.md

@@ -0,0 +1,17 @@
+---
+description: Quick direct implementation — no OpenSpec, no ensemble, no PRs. Just do it.
+---
+
+Implement the task described after `/main` directly and immediately.
+
+**Rules:**
+- No OpenSpec artifacts (no proposal, no specs, no tasks.md)
+- No ensemble team (no team_create, no team_spawn)
+- No branches, no PRs
+- Work directly in the current branch
+- Keep changes minimal and focused on exactly what was asked
+- Use Read/Glob/Grep to locate relevant files before editing
+- After editing, run `pnpm run typecheck` to catch type errors; fix any that are caused by your changes
+- Do NOT run lint or tests unless the user asks
+
+**Input**: Everything after `/main` is the task. Execute it now.