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
3.2 KiB
Markdown
1 line
3.2 KiB
Markdown
---description: Resume or start track implementation following TDD protocolagent: tier2-tech-lead---# /conductor-implementResume or start implementation of the active track following TDD protocol.## Prerequisites- Run `/conductor-setup` first to load context- Ensure a track is active (has `[~]` tasks)## CRITICAL: Use MCP Tools OnlyAll research and file operations must use Manual Slop's MCP tools:- `manual-slop_py_get_code_outline` - structure analysis- `manual-slop_py_get_skeleton` - signatures + docstrings- `manual-slop_py_find_usages` - find references- `manual-slop_get_git_diff` - recent changes- `manual-slop_run_powershell` - shell commands## Implementation Protocol1. **Identify Current Task:** - Read active track's `plan.md` via `manual-slop_read_file` - Find the first `[~]` (in-progress) or `[ ]` (pending) task - If phase has no pending tasks, move to next phase2. **Research Phase (MANDATORY):** Before implementing, use MCP tools to understand context: - `manual-slop_py_get_code_outline` on target files - `manual-slop_py_get_skeleton` on dependencies - `manual-slop_py_find_usages` for related patterns - `manual-slop_get_git_diff` for recent changes - Audit `__init__` methods for existing state3. **TDD Cycle:** ### Red Phase (Write Failing Tests) - Stage current progress: `manual-slop_run_powershell` with `git add .` - Delegate test creation to @tier3-worker: ``` @tier3-worker Write tests for: [task description] WHERE: tests/test_file.py:line-range WHAT: Test [specific functionality] HOW: Use pytest, assert [expected behavior] SAFETY: [thread-safety constraints] Use 1-space indentation. Use MCP tools only. ``` - Run tests: `manual-slop_run_powershell` with `uv run pytest tests/test_file.py -v` - **CONFIRM TESTS FAIL** - this is the Red phase ### Green Phase (Implement to Pass) - Stage current progress: `manual-slop_run_powershell` with `git add .` - Delegate implementation to @tier3-worker: ``` @tier3-worker Implement: [task description] WHERE: src/file.py:line-range WHAT: [specific change] HOW: [API calls, patterns to use] SAFETY: [thread-safety constraints] Use 1-space indentation. Use MCP tools only. ``` - Run tests: `manual-slop_run_powershell` with `uv run pytest tests/test_file.py -v` - **CONFIRM TESTS PASS** - this is the Green phase ### Refactor Phase (Optional) - With passing tests, refactor for clarity - Re-run tests to verify4. **Commit Protocol (ATOMIC PER-TASK):** Use `manual-slop_run_powershell`: ```powershell git add . git commit -m "feat(scope): description" $hash = git log -1 --format="%H" git notes add -m "Task: [summary]" $hash ``` - Update `plan.md`: Change `[~]` to `[x]` with commit SHA - Commit plan update: `git add plan.md && git commit -m "conductor(plan): Mark task complete"`5. **Repeat for Next Task**## Error HandlingIf tests fail after Green phase:- Delegate analysis to @tier4-qa: ``` @tier4-qa Analyze this test failure: [test output] DO NOT fix - provide analysis only. Use MCP tools only. ```- Maximum 2 fix attempts before escalating to user## Phase CompletionWhen all tasks in a phase are `[x]`:- Run `/conductor-verify` for checkpoint |