3.6 KiB
3.6 KiB
TODO
Persistent task list. Check off + note outcome; move done items to the bottom log with date.
State: .opencode/state/status.md. Design: docs/architecture.md.
Phase 0 — analysis
- Inspect repo, fastcrw reference, pocock-agents, upstream skills, OpenCode v2 plugin + agent docs
- Architecture (docs/architecture.md §1)
- Plugin API requirements (§3)
- Agent architecture (§4)
- Sync strategy (§5)
- Gitea Actions design (§6)
- Testing strategy (§7)
- Phased plan (§9)
- Skill inventory + classification matrix → docs/skill-mapping.md + .opencode/state/classification.json (38 skills analyzed from SKILL.md sources)
- Commit phase-0 docs
Phase 1 — plugin package
- 1.1 scaffold package (package.json name @haylan/opencode-pocock — CONFIRM scope with repo owner, tsconfig, prettier, .gitignore, MIT LICENSE + upstream attribution, README stub)
- 1.2 scripts/sync-upstream.ts + vendor upstream/ @49dd158 + state update
- 1.3 scripts/generate.ts: manifest.json + skills/ output + unit tests (parser, manifest)
- 1.4 src/index.ts plugin: skill injection, options validation, agent-staleness warning + fake-ctx integration tests (verify Skill.Info fields against installed @opencode/plugin typings!)
- 1.5 bin init (copy agents, -g global, no silent overwrite) + tests
- 1.6 agent-templates/: port pocock + pocock-worker from pocock-agents to V2-native frontmatter (permissions array, shell action, no legacy keys); generate agents/*.md; drift tests
- 1.7 scripts/release.ts + version.ts adapted from fastcrw + unit tests
- 1.8 .gitea/workflows/: check.yml, nightly.yml, smoke (dispatch); smoke.ts against opencode serve
- 1.9 local runtime verification (serve + HTTP API: plugin ok, skills visible, autoinvoke flags, agents after init, worker denies hold) → docs/runtime-checks.md
- 1.10 manual release 0.1.0 to Gitea registry; verify install-from-registry by package name
- ask repo admin to add Gitea secret PACKAGE_TOKEN (write:package + write:repository)
Phase 2 — conversion
- 2.1 deep per-skill analysis → .opencode/state/classification.json + docs/skill-mapping.md (done in phase 0; generator must regenerate mapping doc from classification.json — keep in 1.3 scope)
- 2.2 guardrails plugin hook (opt-in, tool.hook execute.before on shell) + tests
- 2.3 pocock-reviewer: CONFIRMED by analysis (D8) — implement template + skill-permission scoping
- 2.4 orchestrator V2 flow wiring (background-subagent status in V2? batch fallback; worktree permission guidance; slash UX for user-invoked skills)
- 2.5 per-skill regression checks + manual orchestration smoke (token-spending, documented)
- 2.6 README usage guide + finalize skill-mapping
- 2.7 one week of green nightlies → declare stable
Open questions
ExactRESOLVED 2026-10-14 (Skill.Info/editor.add field set@opencode/plugin@2.0.29):{id, name, description?, autoinvoke?, path, content}; noslashin Info.- V2 background subagents: still env-gated? Affects orchestrator dispatch loop wording (1.6).
- Do plugin-injected skills get
/nameslash exposure (noslashfield in Skill.Info)? Runtime check at 1.9; fallback = documentskills: ["<pkg-dir>/skills"]config entry for file-based load. - Package name/scope confirmation (1.1).
- Does nightly runner have network access to github.com for upstream fetch? (1.8 — fallback: mirror upstream to Gitea and sync from the mirror.)
Done log
- 2026-10-14: phase-0 analysis docs written (AGENTS.md, state/, docs/architecture.md, TODO.md).