ed
38430fd312
Restores the 20 tracked files deleted in commitf63769ac. The user clarified that the .opencode/ directory contains the OpenCode agent role definitions and slash command starters — these are NOT outdated; they are starter files that OpenCode loads as primary/subagent roles and user-invokable slash commands. The .opencode/agents/ files are AGENT ROLE DEFINITIONS (tier1-orchestrator, tier2-tech-lead, tier3-worker, tier4-qa, explore, general). OpenCode loads these as primary/subagent roles. The .opencode/commands/ files are SLASH COMMAND DEFINITIONS (conductor-implement, conductor-new-track, conductor-setup, conductor-status, conductor-verify, and the 4 mma-tierN-* slash commands). OpenCode surfaces these as user-invokable commands. These are NOT equivalent to .agents/skills/mma-*/SKILL.md (skill definitions loaded on-demand via the Skill tool). I previously conflated agents with skills in my 'duplicates of canonical' claim — that was incorrect. Restoration method (per AGENTS.md HARD BAN on 'git restore'/'git reset'): - Extracted each file from commit f63769ac^ via 'git show <sha>:<path>' - Wrote each file's bytes back to disk via the Write tool equivalent - This is a forward commit (fix-forward per conductor/tier2/agents/tier2-autonomous.md 'timeline-is-immutable' principle); git history preserved.f63769acremains in history for forensics; this commit supersedes it. For future reference: 'legacy' labels in superpowers_review_20260619/report.md §16.2 refer to the project's NOT USING these files in its current MMA workflow — NOT that the files themselves are outdated. They remain starter templates for OpenCode.
1.5 KiB
---description: Initialize conductor context ΓÇö read product docs, verify structure, report readinessagent: tier1-orchestratorsubtask: true---# /conductor-setupBootstrap the session with full conductor context. Run this at session start.## Steps1. Read Core Documents: - conductor/index.md ΓÇö navigation hub - conductor/product.md ΓÇö product vision - conductor/product-guidelines.md ΓÇö UX/code standards - conductor/tech-stack.md ΓÇö technology constraints - conductor/workflow.md ΓÇö task lifecycle (skim; reference during implementation)2. Check Active Tracks: - List all directories in conductor/tracks/ - Read each metadata.json for status - Read each plan.md for current task state - Identify the track with [~] in-progress tasks3. Check Session Context: - Read conductor/tracks.md if it exists ΓÇö check for IN_PROGRESS or BLOCKED tasks - Read last 3 entries in JOURNAL.md for recent activity - Run git log --oneline -10 for recent commits4. Report Readiness: Present a session startup summary: ## Session Ready **Active Track:** {track name} ΓÇö Phase {N}, Task: {current task description} **Recent Activity:** {last journal entry title} **Last Commit:** {git log -1 oneline} Ready to: - `/conductor-implement` ΓÇö resume active track - `/conductor-status` ΓÇö full status overview - `/conductor-new-track` ΓÇö start new work ## Important- This is READ-ONLY ΓÇö do not modify files