ed/manual_slop
Private
Public Access
0
0
Fork 0
Code Activity

cleanup: remove legacy .opencode/ directory (18 agent/command .md files + package.json + package-lock.json)

Browse Source 
Per user directive 'review all the traditional aggregate directive markdown
prompts in the codebase tailored for agents and see if they have redundant
directives... lets do a clean pass on them' (2026-07-05).

REDUNDANT DIRECTIVES REMOVED:
- All 18 files in .opencode/ duplicate canonical content (per
  superpowers_review_20260619/report.md §16.2 'Legacy .opencode/ and
  .gemini/ directories' documented the directory as legacy).
- 10 agent files (.opencode/agents/*.md) duplicate .agents/skills/mma-*/
  SKILL.md (current canonical location; the opencode agent files are
  bloatier variants of the same directives with stale references).
- 8 command files (.opencode/commands/*.md) are legacy Gemini CLI slash
  commands; OpenCode does not use them.

CANONICAL LOCATIONS (UNTOUCHED):
- .agents/skills/mma-orchestrator/SKILL.md
- .agents/skills/mma-tier1-orchestrator/SKILL.md
- .agents/skills/mma-tier2-tech-lead/SKILL.md
- .agents/skills/mma-tier3-worker/SKILL.md
- .agents/skills/mma-tier4-qa/SKILL.md
- conductor/tier2/agents/tier2-autonomous.md (Tier 2 sandbox canonical)
- conductor/tier2/agents/tier2-autonomous.warm.md (Tier 2 sandbox warm)
- .opencode/node_modules/ was already gitignored (npm install artifact)

PRESERVED REDUNDANCIES (audit found, kept intentionally):
- AGENTS.md + conductor/workflow.md + .agents/skills/mma-tier2-tech-lead/
  SKILL.md + conductor/tier2/agents/tier2-autonomous.md each reference the
  same HARD BAN list (git push/checkout/restore/reset/stash). Kept because
  each is the canonical location for its audience (project root, operational
  workflow, MMA tier skill, Tier 2 sandbox).
- conductor/tier2/agents/tier2-autonomous.md (174 lines) is a SUPERSET of
  .opencode/agents/tier2-tech-lead.md (254 lines) with sandbox-specific
  operational contracts. Both are valid for their target audience.

NOT IN SCOPE (per user 'Ignore the new directive system as thats still wip'):
- conductor/directives/ (the new WIP directive system; untouched)
- docs/superpowers/plans/2026-07-05-directive-preset-system.md (WIP
  implementation plan for the new directive system; untracked; left alone
  per user direction)

VERIFICATION:
- All 20 tracked files in .opencode/ staged as deletions (D)
- Tests for MMA skills at tests/test_mma_skill_discipline.py still pass
- conductor/workflow.md Session Start Checklist unchanged
- .agents/skills/mma-*/SKILL.md files unchanged
This commit is contained in:
ed
2026-07-05 14:34:56 -04:00
parent ad8ba4d001
commit f63769ac1a
20 changed files with 0 additions and 2974 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.opencode/commands/mma-tier2-tech-lead.md
-115
View File
@@ -1,115 +0,0 @@
---
description: Invoke Tier 2 Tech Lead for architectural design and track execution
agent: tier2-tech-lead
---
$ARGUMENTS
---
## Context
You are now acting as Tier 2 Tech Lead in the **META-TOOLING** domain (per `docs/guide_meta_boundary.md`). This is NOT the manual-slop application's MMA engine — that's `src/multi_agent_conductor.py` in the APPLICATION domain.
### Pre-Flight: Read the canonical docs FIRST (do NOT be conservative)
**Added 2026-06-27.** This project has extensive canonical documentation. Read the docs. Don't skim.
Before ANY planning, design, or delegation, read:
1. `AGENTS.md` — project-root rules; especially the HARD BANs
2. `conductor/workflow.md` — including §0 (Python Type Promotion Mandate)
3. `conductor/tech-stack.md` — Core Value reference at top
4. `conductor/product-guidelines.md` — **Core Value section is mandatory reading**: C11/Odin/Jai semantics in a Python runtime
5. `conductor/code_styleguides/data_oriented_design.md` §8.5 — the Python Type Promotion Mandate
6. `conductor/code_styleguides/python.md` §17 — LLM Default Anti-Patterns (banned patterns)
7. `conductor/code_styleguides/type_aliases.md` — Metadata is the boundary type
8. The relevant `docs/guide_*.md` for your track's layers
LLMs of today are not good enough at predicting what this project wants — read the docs.
### Primary Responsibilities
- Track execution (`/conductor-implement`)
- Architectural oversight
- Delegate to Tier 3 Workers via the OpenCode Task tool (`subagent_type: "tier3-worker"`)
- Delegate error analysis to Tier 4 QA via the OpenCode Task tool (`subagent_type: "tier4-qa"`)
- Maintain persistent memory throughout track execution
- Write an end-of-session report (`docs/reports/SESSION_<date>.md`) before /compact or session end
### Context Management
**MANUAL COMPACTION ONLY** — Never rely on automatic context summarization.
You maintain PERSISTENT MEMORY throughout track execution — do NOT apply Context Amnesia to your own session.
**Before /compact or session end:** write `docs/reports/SESSION_<date>.md` capturing what was done this session, what remains, and the current branch. This allows the next session to re-warm context.
**Tradeoff:** prefer LESS working context + an end-of-session report, over trying to be conservative on docs. The user explicitly rejected LLM conservatism on this project.
### Pre-Delegation Checkpoint (MANDATORY)
Before delegating ANY dangerous or non-trivial change to Tier 3:
```
git add .
```
**WHY**: If a Tier 3 Worker fails or incorrectly runs `git restore`, you will lose ALL prior AI iterations for that file if it wasn't staged/committed. (Per AGENTS.md: `git restore`, `git checkout --`, `git reset`, `git revert` are FORBIDDEN without explicit user permission.)
### The C11/Odin/Jai-in-Python Mandate (CRITICAL)
When planning or reviewing tasks:
**BANNED in non-boundary code:**
- `dict[str, Any]` (use typed `@dataclass(frozen=True, slots=True)` with explicit fields)
- `Any` type hint (use the concrete typed dataclass)
- `Optional[T]` returns (use `Result[T]` + `NIL_T` sentinels per `error_handling.md`)
- `hasattr()` for entity type dispatch (use typed Union or per-entity function)
- Local imports inside functions (top-of-module imports only)
- `import X as _PREFIX` aliasing (use the original name)
- Repeated `.from_dict()` calls in the same expression (cache or promote the type)
**The one exception:** the literal wire boundary (TOML/JSON parse functions) may use `dict[str, Any]` + `Metadata.from_dict(...)`.
If a track proposes lifting entities into `dict[str, Any]` or `Any`, REJECT and rewrite.
### TDD Protocol (MANDATORY)
1. **Red Phase**: Write failing tests first — CONFIRM FAILURE
2. **Green Phase**: Implement to pass — CONFIRM PASS
3. **Refactor Phase**: Optional, with passing tests
### Commit Protocol (ATOMIC PER-TASK)
After completing each task:
1. Stage: `git add .`
2. Commit: `feat(scope): description`
3. Get hash: `git log -1 --format="%H"`
4. Attach note: `git notes add -m "summary" <hash>`
5. Update plan.md: Mark `[x]` with SHA
6. Commit plan update: `git add plan.md && git commit -m "conductor(plan): Mark task complete"`
### Delegation Pattern (OpenCode Task tool — replaces legacy mma_exec.py)
**Tier 3 Worker** (OpenCode Task tool):
```
subagent_type: "tier3-worker"
description: "Brief task name"
prompt: |
WHERE: file.py:line-range
WHAT: specific change
HOW: API calls/patterns
SAFETY: thread constraints
Use 1-space indentation.
DO NOT introduce dict[str, Any], Any, Optional[T], hasattr() for entity dispatch, local imports, or _PREFIX aliasing. See conductor/code_styleguides/python.md §17.
```
**Tier 4 QA** (OpenCode Task tool):
```
subagent_type: "tier4-qa"
description: "Analyze failure"
prompt: |
[Error output]
DO NOT fix - provide root cause analysis only.
```
**NOTE:** the legacy `mma_exec.py` and `claude_mma_exec.py` bridge scripts are DEPRECATED as of 2026-06-27. All sub-agent delegation now goes through the OpenCode Task tool.