opencode-onboard 0.1.4 → 0.1.5

package/content/.agents/agents/back-engineer.md

@@ -72,3 +72,10 @@ Rules:
 **Files changed:** <list>
 **Blockers:** none | <description>
 ```
+
+## Session Log
+
+Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+- On start: `| {ISO timestamp} | back-engineer | started | {task summary} |`
+- On skill load: `| {ISO timestamp} | back-engineer | skill-loaded | {skill-name} |`
+- On done: `| {ISO timestamp} | back-engineer | completed | {files changed count} files |`

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

@@ -56,10 +56,11 @@ Rules:
 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. Commit and push the feature branch
-5. Create the PR following the skill instructions
-6. Post PR comment with screenshots and change summary
-7. Report PR URL to the lead
+4. Read `.agents/session-log.md` if it exists — include a "Session Activity" section in the PR description with agent names, task counts, and total duration
+5. Commit and push the feature branch
+6. Create the PR following the skill instructions
+7. Post PR comment with screenshots and change summary
+8. Report PR URL to the lead
 
 ### Feedback Mode (PR review loop)
 1. Load the matching pullrequest observer skill
@@ -106,3 +107,10 @@ Rules:
 **Questions for human:** <count>, <list>
 **Acknowledged only:** <count>
 ```
+
+## Session Log
+
+Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+- On start: `| {ISO timestamp} | devops-manager | started | {mode} mode |`
+- On skill load: `| {ISO timestamp} | devops-manager | skill-loaded | {skill-name} |`
+- On done: `| {ISO timestamp} | devops-manager | completed | {summary} |`

package/content/.agents/agents/front-engineer.md

@@ -71,3 +71,10 @@ Rules:
 **Files changed:** <list>
 **Blockers:** none | <description>
 ```
+
+## Session Log
+
+Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+- On start: `| {ISO timestamp} | front-engineer | started | {task summary} |`
+- On skill load: `| {ISO timestamp} | front-engineer | skill-loaded | {skill-name} |`
+- On done: `| {ISO timestamp} | front-engineer | completed | {files changed count} files |`

package/content/.agents/agents/infra-engineer.md

@@ -72,3 +72,10 @@ Rules:
 **Resources affected:** <list>
 **Blockers:** none | <description>
 ```
+
+## Session Log
+
+Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+- On start: `| {ISO timestamp} | infra-engineer | started | {task summary} |`
+- On skill load: `| {ISO timestamp} | infra-engineer | skill-loaded | {skill-name} |`
+- On done: `| {ISO timestamp} | infra-engineer | completed | {files changed count} files |`

package/content/.agents/agents/quality-engineer.md

@@ -72,3 +72,10 @@ Rules:
 **Acceptance criteria:** met | <unmet items>
 **Blockers:** none | <description>
 ```
+
+## Session Log
+
+Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+- On start: `| {ISO timestamp} | quality-engineer | started | {task summary} |`
+- On skill load: `| {ISO timestamp} | quality-engineer | skill-loaded | {skill-name} |`
+- On done: `| {ISO timestamp} | quality-engineer | completed | {tests added count} tests |`

package/content/.agents/agents/security-auditor.md

@@ -82,3 +82,10 @@ Rules:
 
 **Blockers:** none | <critical findings that must be resolved before PR>
 ```
+
+## Session Log
+
+Append to `.agents/session-log.md` (create with header if missing, skip if `session-logging: disabled` in AGENTS.md):
+- On start: `| {ISO timestamp} | security-auditor | started | {task summary} |`
+- On skill load: `| {ISO timestamp} | security-auditor | skill-loaded | {skill-name} |`
+- On done: `| {ISO timestamp} | security-auditor | completed | {findings count} findings |`

package/content/AGENTS.md

@@ -65,6 +65,72 @@ Replace the entire contents of this file (`AGENTS.md`) with everything below the
 
 ---
 
+### Step 4b, Patch opsx-apply for ensemble
+
+Read `.opencode/commands/opsx-apply.md`. Find the step that instructs the agent to **implement tasks directly** — it will contain phrases like "make the code changes", "implement tasks", "loop until done or blocked". This step tells the agent to write code itself.
+
+**Replace that step and everything after it** (completion output, pause output, guardrails, fluid workflow) with the following:
+
+```markdown
+6. **Implement via ensemble team**
+
+   NEVER implement tasks directly. Always delegate to specialists via ensemble.
+
+   a. Create feature branch if not already on one: `feature/{id}-{slug}`
+   b. Create team:
+      ```
+      team_create "<change-name>"
+      ```
+      Announce: "Team running. Monitor at http://localhost:4747/"
+
+   c. Spawn only what the tasks require (in parallel):
+      ```
+      team_spawn name:front   agent:front-engineer  → UI/frontend tasks
+      team_spawn name:back    agent:back-engineer   → backend/API tasks
+      team_spawn name:infra   agent:infra-engineer  → infra/pipeline tasks
+      ```
+      Pass each specialist: their relevant tasks + all context file paths from step above.
+      Log each spawn to `.agents/session-log.md` (see Session Log section).
+
+   d. Wait for all → `team_results` → `team_shutdown` + `team_merge`
+
+7. **Quality check**
+
+   ```
+   team_spawn name:quality agent:quality-engineer
+   ```
+   Wait → `team_results` → fix blockers → `team_shutdown`
+
+8. **Mark tasks complete in openspec**
+
+   After specialists finish, update the tasks file: `- [ ]` → `- [x]` for each completed task.
+   Run `openspec status --change "<name>" --json` to confirm progress.
+
+9. **On completion or pause, show status**
+
+   Display:
+   - Tasks completed this session
+   - Overall progress: "N/M tasks complete"
+   - If all done: suggest archive with `/opsx-archive`
+   - If paused: explain why and wait for guidance
+
+   Then run `team_cleanup`.
+
+**Guardrails**
+- NEVER implement tasks directly — always use `team_create` + `team_spawn`
+- Always read context files before spawning (from the apply instructions output)
+- Always pass context file paths and task list to spawned specialists
+- Mark tasks complete in openspec AFTER specialists finish, not before
+- If task is ambiguous, pause and ask before spawning
+- If implementation reveals issues, pause and suggest artifact updates
+- Pause on errors, blockers, or unclear requirements — don't guess
+- Use contextFiles from CLI output, don't assume specific file names
+```
+
+Keep all steps before the implementation step unchanged — they are openspec's domain (select change, check status, get instructions, read context, show progress).
+
+---
+
 ### Step 5, Confirm
 
 Tell the user:
@@ -108,9 +174,9 @@ This is the agent orchestration layer for your project. It provides:
 When the user provides a work item URL, says "implement the plan", or "I've added comments to the PR", **I own the full lifecycle**. I load the appropriate skill and use ensemble tools (`team_create`, `team_spawn`, etc.) to coordinate the agent team.
 
 Trigger patterns:
-- `work on this <azure-devops-url>` → spawn `devops-manager` in read mode → propose OpenSpec → implement → ship
-- `work on this <github-url>` → spawn `devops-manager` in read mode → propose OpenSpec → implement → ship
-- `implement the plan` → load skill `openspec-apply-change` → implement → ship
+- `work on this <azure-devops-url>` → spawn `devops-manager` in read mode → propose OpenSpec → **confirm with user** → implement → ship
+- `work on this <github-url>` → spawn `devops-manager` in read mode → propose OpenSpec → **confirm with user** → implement → ship
+- `implement the plan` → run `/opsx-apply` (ensemble orchestration is built into the command) → ship
 - `I've added comments to the PR` → spawn `devops-manager` in feedback mode → fix → update PR
 
 **Never delegate without a plan. Never write implementation code directly, always spawn specialists.**
@@ -166,21 +232,17 @@ devops-manager (ship mode)
 1. team_spawn devops-manager (read mode) → fetch work item via skill, output summary
 2. Load skill: openspec-propose → generate proposal.md, specs/, tasks.md
    - team_create → spawn design + specs in parallel → merge → write tasks.md
-3. Show summary, confirm with user before implementing
+3. Show the plan: change name, schema, total tasks, task list summary
+4. STOP. Ask user: "Ready to implement? (yes/no)" — DO NOT proceed until confirmed.
 ```
 
 ### Phase 2, Implement
 
 ```
-1. Load skill: openspec-apply-change → get apply instructions
-2. Create feature branch: feature/{id}-{slug}
-3. team_create "<change-name>"
-4. Announce: "Team running. Monitor at http://localhost:4747/"
-5. Spawn only what the task needs (in parallel):
-   team_spawn name:front   agent:front-engineer  → UI tasks
-   team_spawn name:back    agent:back-engineer   → backend tasks
-   team_spawn name:infra   agent:infra-engineer  → infra tasks
-6. Wait for all → team_results → team_shutdown + team_merge
+1. Run /opsx-apply (or load skill openspec-apply-change)
+   The command handles context reading, ensemble orchestration, and task marking automatically.
+   DO NOT implement tasks directly — the command spawns specialists via ensemble.
+2. After /opsx-apply completes, proceed to quality check.
 ```
 
 ### Phase 3, Quality
@@ -277,6 +339,52 @@ Example: `feature/42-add-user-auth`
 
 ---
 
+## Session Log
+
+<!-- session-logging: enabled -->
+
+All agents MUST log their activity to `.agents/session-log.md`. This file is gitignored and temporary.
+
+**Check before logging:** Read the `session-logging` comment above. If it says `disabled`, skip all logging.
+
+**On first write per session**, create the file with the header:
+```markdown
+# Session Log
+
+| Timestamp | Agent | Action | Detail |
+|-----------|-------|--------|--------|
+```
+
+**Log these events** by appending a row:
+- Lead spawns an agent → `| {ISO timestamp} | lead | spawned | {agent-name} for {purpose} |`
+- Agent starts → `| {ISO timestamp} | {agent-name} | started | {task summary} |`
+- Agent loads a skill → `| {ISO timestamp} | {agent-name} | skill-loaded | {skill-name} |`
+- Agent completes → `| {ISO timestamp} | {agent-name} | completed | {files changed count} files |`
+- Agent blocked → `| {ISO timestamp} | {agent-name} | blocked | {reason} |`
+
+**Rules:**
+- Append only, never overwrite previous entries
+- One row per event, keep detail column short
+- Use ISO 8601 timestamps
+- The file is gitignored — never commit it
+
+---
+
+## RTK
+
+Use `rtk` wrapper for ALL CLI commands. Never run git, az, gh, or openspec commands directly.
+
+- `rtk git add` NOT `git add`
+- `rtk git commit` NOT `git commit`
+- `rtk git push` NOT `git push`
+- `rtk az boards work-item show` NOT `az boards work-item show`
+- `rtk az repos pr create` NOT `az repos pr create`
+- `rtk gh issue view` NOT `gh issue view`
+- `rtk gh pr create` NOT `gh pr create`
+- `rtk openspec new change` NOT `openspec new change`
+
+---
+
 ## Guardrails
 
 ### Git Operations

package/package.json

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