Private
Public Access
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 line
2.6 KiB
Markdown
1 line
2.6 KiB
Markdown
---description: Verify phase completion and create checkpoint commitagent: tier2-tech-lead---# /conductor-verifyExecute phase completion verification and create checkpoint.## Prerequisites- All tasks in the current phase must be marked `[x]`- All changes must be committed## CRITICAL: Use MCP Tools OnlyAll operations must use Manual Slop's MCP tools:- `manual-slop_read_file` - read files- `manual-slop_get_git_diff` - check changes- `manual-slop_run_powershell` - shell commands## Verification Protocol1. **Announce Protocol Start:** Inform user that phase verification has begun.2. **Determine Phase Scope:** - Find previous phase checkpoint SHA in `plan.md` via `manual-slop_read_file` - If no previous checkpoint, scope is all changes since first commit3. **List Changed Files:** Use `manual-slop_run_powershell`: ```powershell git diff --name-only <previous_checkpoint_sha> HEAD ```4. **Verify Test Coverage:** For each code file changed (exclude `.json`, `.md`, `.yaml`): - Check if corresponding test file exists via `manual-slop_search_files` - If missing, create test file via @tier3-worker5. **Execute Tests in Batches:** **CRITICAL**: Do NOT run full suite. Run max 4 test files at a time. Announce command before execution: ``` I will now run: uv run pytest tests/test_file1.py tests/test_file2.py -v ``` Use `manual-slop_run_powershell` to execute. If tests fail with large output: - Pipe to log file - Delegate analysis to @tier4-qa - Maximum 2 fix attempts before escalating6. **Present Results:** ``` ## Phase Verification Results **Phase:** {phase name} **Files Changed:** {count} **Tests Run:** {count} **Tests Passed:** {count} **Tests Failed:** {count} [Detailed results or failure analysis] ```7. **Await User Confirmation:** **PAUSE** and wait for explicit user approval before proceeding.8. **Create Checkpoint:** Use `manual-slop_run_powershell`: ```powershell git add . git commit --allow-empty -m "conductor(checkpoint): Phase {N} complete" $hash = git log -1 --format="%H" git notes add -m "Verification: [report summary]" $hash ```9. **Update Plan:** - Add `[checkpoint: {sha}]` to phase heading in `plan.md` - Use `manual-slop_set_file_slice` or `manual-slop_read_file` + write - Commit: `git add plan.md && git commit -m "conductor(plan): Mark phase complete"`10. **Announce Completion:** Inform user that phase is complete with checkpoint created.## Error Handling- If any verification fails: HALT and present logs- Do NOT proceed without user confirmation- Maximum 2 fix attempts per failure |