feat(opencode): Enforce Manual Slop MCP tools across all agents
This commit is contained in:
@@ -11,25 +11,34 @@ Resume or start implementation of the active track following TDD protocol.
|
||||
- Run `/conductor-setup` first to load context
|
||||
- Ensure a track is active (has `[~]` tasks)
|
||||
|
||||
## CRITICAL: Use MCP Tools Only
|
||||
|
||||
All 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 Protocol
|
||||
|
||||
1. **Identify Current Task:**
|
||||
- Read active track's `plan.md`
|
||||
- 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 phase
|
||||
|
||||
2. **Research Phase (MANDATORY):**
|
||||
Before implementing, use tools to understand context:
|
||||
- `py_get_code_outline` on target files
|
||||
- `py_get_skeleton` on dependencies
|
||||
- `grep` for related patterns
|
||||
- `get_git_diff` for recent changes
|
||||
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 state
|
||||
|
||||
3. **TDD Cycle:**
|
||||
|
||||
### Red Phase (Write Failing Tests)
|
||||
- Stage current progress: `git add .`
|
||||
- Stage current progress: `manual-slop_run_powershell` with `git add .`
|
||||
- Delegate test creation to @tier3-worker:
|
||||
```
|
||||
@tier3-worker
|
||||
@@ -41,13 +50,13 @@ Resume or start implementation of the active track following TDD protocol.
|
||||
HOW: Use pytest, assert [expected behavior]
|
||||
SAFETY: [thread-safety constraints]
|
||||
|
||||
Use 1-space indentation.
|
||||
Use 1-space indentation. Use MCP tools only.
|
||||
```
|
||||
- Run tests: `uv run pytest tests/test_file.py -v`
|
||||
- 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: `git add .`
|
||||
- Stage current progress: `manual-slop_run_powershell` with `git add .`
|
||||
- Delegate implementation to @tier3-worker:
|
||||
```
|
||||
@tier3-worker
|
||||
@@ -59,9 +68,9 @@ Resume or start implementation of the active track following TDD protocol.
|
||||
HOW: [API calls, patterns to use]
|
||||
SAFETY: [thread-safety constraints]
|
||||
|
||||
Use 1-space indentation.
|
||||
Use 1-space indentation. Use MCP tools only.
|
||||
```
|
||||
- Run tests: `uv run pytest tests/test_file.py -v`
|
||||
- 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)
|
||||
@@ -69,6 +78,7 @@ Resume or start implementation of the active track following TDD protocol.
|
||||
- Re-run tests to verify
|
||||
|
||||
4. **Commit Protocol (ATOMIC PER-TASK):**
|
||||
Use `manual-slop_run_powershell`:
|
||||
```powershell
|
||||
git add .
|
||||
git commit -m "feat(scope): description"
|
||||
@@ -90,7 +100,7 @@ If tests fail after Green phase:
|
||||
|
||||
[test output]
|
||||
|
||||
DO NOT fix - provide analysis only.
|
||||
DO NOT fix - provide analysis only. Use MCP tools only.
|
||||
```
|
||||
- Maximum 2 fix attempts before escalating to user
|
||||
|
||||
|
||||
Reference in New Issue
Block a user