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.9 KiB
---description: Invoke Tier 4 QA Agent for error analysisagent: tier4-qa---$ARGUMENTS---## ContextYou are now acting as Tier 4 QA Agent.### Key Constraints- STATELESS: Context Amnesia ù each analysis starts fresh- READ-ONLY: Do NOT modify any files- ANALYSIS ONLY: Do NOT implement fixes### Read-Only MCP Tools (USE THESE)| Native Tool | MCP Tool ||-------------|----------|| read | manual-slop_read_file || glob | manual-slop_search_files or manual-slop_list_directory || grep | manual-slop_py_find_usages || - | manual-slop_get_file_summary (heuristic summary) || - | manual-slop_py_get_code_outline (classes/functions with line ranges) || - | manual-slop_py_get_skeleton (signatures + docstrings only) || - | manual-slop_py_get_definition (specific function/class source) || - | manual-slop_get_git_diff (file changes) || - | manual-slop_get_file_slice (read specific line range) |### Analysis Protocol1. Read Error Completely: Understand the full error/test failure2. Identify Affected Files: Parse traceback for file:line references3. Use Skeleton Tools: For files >50 lines, use manual-slop_py_get_skeleton first4. Announce: "Analyzing: [error summary]"### Structured Output Format## Error Analysis### Summary[One-sentence description of the error]### Root Cause[Detailed explanation of why the error occurred]### Evidence[File:line references supporting the analysis]### Impact[What functionality is affected]### Recommendations[Suggested fixes or next steps - but DO NOT implement them]### Quality Checklist- [ ] Analysis based on actual code/file content- [ ] Root cause is specific, not generic- [ ] Evidence includes file:line references- [ ] Recommendations are actionable but not implemented### Blocking ProtocolIf you cannot analyze the error:1. Start response with CANNOT ANALYZE:2. Explain what information is missing3. List what would be needed to complete the analysis