@jetrabbits/agentic 0.3.1 → 0.3.3

package/AGENTS.md

@@ -1,34 +1,17 @@
 # AGENTS — root guidance
 
-## Dynamic loading of guidance
+## Dynamic guidance loading
 
-The set of loaded guidance is configurable per project and may change per task. Do not assume only statically listed
-files are available.
+The loaded guidance set is project-specific and may change per task. Do not assume the statically listed files are
+complete; first discover optional guidance under the target project's `.agent/` directory.
 
-Discover and load custom files from the target project when present:
+Discover and load guidance in this order:
 
-```text
-project_dir/
-└── .agent/
-    ├── rules/
-    ├── skills/
-    ├── workflows/
-    └── prompts/
-```
-
-## Guidance chain
-
-1. Project `.agent/` baseline
-2. `.agent/rules/*` — load all
-3. `.agent/skills/*/SKILL.md` — load only the skill matching the current task
-4. `.agent/workflows/*` — load the workflow matching the triggered command
-
-**Discovery patterns:**
-
-- `.agent/rules/*.md`
-- `.agent/skills/*/SKILL.md`
-- `.agent/workflows/*.md`
-- `.agent/prompts/*.md`
+1. `.agent/*.md` — project baseline files, when present
+2. `.agent/rules/*.md` — all project rules
+3. `.agent/skills/*/SKILL.md` — only the skill matching the current task
+4. `.agent/workflows/*.md` — only the workflow matching the triggered command
+5. `.agent/prompts/*.md` — only when explicitly requested or referenced by loaded guidance
 
 Prefer relative paths in references inside markdown files.
 
@@ -73,13 +56,17 @@ Cross-cutting practices that apply to every project regardless of area.
 ### Documentation of Behavior Changes
 
 - Any behavior change captured in Markdown artifacts must be documented under the project `docs/` directory.
-- Use documentation paths that match the change type, for example `docs/<feature>/README.md` for feature behavior and `docs/incidents/<date>-<workload>-root-cause.md` for incident root cause reports.
-- Create or update the relevant `docs/` artifact in the same change set; do not leave behavior changes documented only in workflow outputs, tickets, or PR comments.
-- Apply the `product-owner` role to confirm that docs describe the user-facing behavior, acceptance criteria, and operational constraints of the change.
+- Use documentation paths that match the change type, for example `docs/<feature>/README.md` for feature behavior and
+  `docs/incidents/<date>-<workload>-root-cause.md` for incident root cause reports.
+- Create or update the relevant `docs/` artifact in the same change set; do not leave behavior changes documented only
+  in workflow outputs, tickets, or PR comments.
+- Apply the `product-owner` role to confirm that docs describe the user-facing behavior, acceptance criteria, and
+  operational constraints of the change.
 
 ### MCP Memory Providers
 
-See [MEMORY.md](MEMORY.md) for the full protocol: provider roles, Context7 usage, MemPalace session-start queries, fact-writing triggers, tool call examples, and fallback order.
+See [MEMORY.md](MEMORY.md) for the full protocol: provider roles, Context7 usage, MemPalace session-start queries,
+fact-writing triggers, tool call examples, and fallback order.
 
 ### Code Style
 

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## v0.3.3
+
+- Updated MemPalace project initialization to pipe explicit confirmation (`echo "Y" | mempalace init ...`) for non-interactive setup robustness.
+- Removed `agent-model-mapper` from OpenCode plugin registration.
+- Deleted obsolete OpenCode plugin source `extensions/opencode/plugins/agent-model-mapper.ts`.
+
+## v0.3.2
+
+- Added optional post-task specialist agents `instruction_reviewer` and `memory_curator` outside the mandatory SDLC role matrix.
+- Added review pipeline guidance, `.reviews/<task-id>/` output conventions, and documented example instruction/memory review reports.
+- Registered the new specialists in OpenCode role configuration and extended deterministic install/model-mapper coverage.
+
 ## v0.3.1
 
 - Added project-level OpenCode plugin settings in `.agentic.json`, including Telegram `botToken` and `chatId` when `telegram-notification` is enabled.

package/README.md

@@ -1,6 +1,6 @@
 # Agent Intelligence Configuration (agentic)
 
-> **18 areas · 10 Software specs · 8 DevOps specs · 7 SDLC agents · 105+ skills · 73+ workflows**
+> **18 areas · 10 Software specs · 8 DevOps specs · 7 SDLC agents + 2 specialists · 105+ skills · 73+ workflows**
 
 A unified catalog of agentic specializations and the `agentic` CLI. Install orchestrator-ready rules, skills, workflows,
 and prompts into any project — and run a full SDLC agent team out of the box.
@@ -77,14 +77,14 @@ agent-guides/
 │       └── database-ops/      # PostgreSQL, Redis, migrations, backup/restore
 ├── extensions/
 │   ├── opencode/              # OpenCode agent definitions, commands, skills
-│   │   └── agents/            # 7 SDLC agents for .opencode/agents/
+│   │   └── agents/            # SDLC agents + optional specialists for .opencode/agents/
 │   ├── claude/                # Claude Code configs
-│   │   └── agents/            # 7 SDLC agents for .claude/agents/
+│   │   └── agents/            # SDLC agents + optional specialists for .claude/agents/
 │   ├── antigravity/           # Antigravity platform configs
 │   ├── codex/                 # Codex custom agents and override configs
-│   │   └── agents/            # 7 SDLC agents for .codex/agents/
+│   │   └── agents/            # SDLC agents + optional specialists for .codex/agents/
 │   └── gemini/                # Gemini-specific configs
-│   │   └── agents/            # 7 SDLC agents for .gemini/agents/
+│   │   └── agents/            # SDLC agents + optional specialists for .gemini/agents/
 ├── areas/template/            # Authoring templates — start here for new content
 ├── docs/                      # Setup and usage guides
 ├── AGENTS.md                  # Root agent guidance (loaded into every project)
@@ -140,8 +140,8 @@ guidance bundle.
 
 ## SDLC Agent team
 
-The same 7-agent team works across **Claude Code**, **OpenCode**, **Codex**, and any tool that supports agent or
-subagent files.
+The same 7-agent SDLC team works across **Claude Code**, **OpenCode**, **Codex**, and any tool that supports agent or
+subagent files. Agentic also ships optional post-task review specialists for instruction quality and memory hygiene.
 
 | Agent             | Role                                           | Invoke when                                   |
 |:------------------|:-----------------------------------------------|:----------------------------------------------|
@@ -156,6 +156,16 @@ subagent files.
 Each agent has a `vibe` (one-line personality), `Identity`, `Communication Style`, `Success Metrics`, and explicit
 `Boundaries` — so roles never overlap and handoffs are always documented.
 
+Optional specialist agents run outside the mandatory SDLC role matrix:
+
+| Agent                  | Role                                             | Invoke when                                      |
+|:-----------------------|:-------------------------------------------------|:-------------------------------------------------|
+| `instruction_reviewer` | Post-task instruction effectiveness review       | Instructions, tool use, or role guidance changed |
+| `memory_curator`       | Post-task memory hygiene recommendations         | Durable facts or memory quality need review      |
+
+See [Review Pipeline](docs/review-pipeline.md) for the guidance-mode pipeline and `.reviews/<task-id>/` output
+convention.
+
 | Platform    | Agent path                      | Format                         | Guide                                                                                           |
 |:------------|:--------------------------------|:-------------------------------|:------------------------------------------------------------------------------------------------|
 | Claude Code | `project/.claude/agents/*.md`   | Markdown with YAML frontmatter | [Claude Code subagents](https://docs.claude.com/en/api/agent-sdk/subagents)                     |

package/agentic

@@ -1946,7 +1946,7 @@ print_mempalace_project_setup_instructions() {
   out "2) Install MemPalace:"
   out "   pip install mempalace"
   out "3) Initialize the project memory taxonomy without LLM calls:"
-  out "   mempalace init \"$PROJECT_DIR\" --yes --no-llm"
+  out "   echo \"N\" | mempalace init \"$PROJECT_DIR\" --yes --no-llm"
   out "4) Mine project knowledge into its isolated wing:"
   out "   mempalace mine \"$PROJECT_DIR\" --wing \"$project_wing\""
   if [[ -d "$PROJECT_DIR/docs" ]]; then
@@ -2242,7 +2242,7 @@ initialize_mempalace_project() {
     return 1
   fi
 
-  if ! run_mempalace_command "MemPalace init" mempalace init "$PROJECT_DIR" --yes --no-llm; then
+  if ! run_mempalace_command "MemPalace init" bash -lc "echo \"N\" | mempalace init \"$PROJECT_DIR\" --yes --no-llm"; then
     print_mempalace_project_setup_instructions
     return 1
   fi

package/docs/agentic-stabilization/README.md

@@ -5,10 +5,10 @@
 - Post-install doctor checks run independently for `codex`, `opencode`, `claude`, and `gemini`.
 - `AGENTIC_DOCTOR_TIMEOUT_SECONDS` defaults to `10`; a timeout is reported as a doctor failure and install continues.
 - Codex doctor runs non-interactively with `--ephemeral`, `--sandbox workspace-write`, and the same lightweight smoke prompt as other supported doctor targets.
-- OpenCode uses `agent-model-mapper` instead of the removed `model-checker` artifacts.
+- OpenCode uses an install-time `agent-model-mapper` flow instead of the removed `model-checker` artifacts.
 - `agent-model-mapper` writes `.opencode/opencode.json` during interactive install only after confirmation.
-- `agent-model-mapper` uses `fzf` for install-time model dropdowns when available and OpenCode startup skips once all roles are mapped.
-- The runtime OpenCode plugin never opens `fzf`, asks questions, or writes project files.
+- `agent-model-mapper` uses `fzf` for install-time model dropdowns when available.
+- No runtime OpenCode plugin is shipped for `agent-model-mapper`, so OpenCode startup never opens `fzf`, asks questions, or writes project files.
 - Context7 offers an interactive key mode: configure without a key or enter `CONTEXT7_API_KEY` for the selected target configs.
 - OpenCode MemPalace setup writes `mempalace-mcp` config and initializes/mines project memory into a project-specific wing without LLM calls.
 - Telegram notification credentials are read from project `.agentic.json` when the plugin is enabled.
@@ -24,8 +24,9 @@
 - Hung agent doctor commands time out and do not stop remaining selected agents from running.
 - Doctor output includes timeout duration, exit status, and per-agent elapsed time.
 - `extensions/opencode/plugins/model-checker.ts` and `model-checker.json` are absent.
-- `extensions/opencode/opencode.json` lists `agent-model-mapper`.
-- Runtime model mapper execution does not prompt or modify project files.
+- `extensions/opencode/plugins/agent-model-mapper.ts` is absent.
+- `extensions/opencode/opencode.json` does not list `agent-model-mapper`.
+- Install-time model mapper execution still writes confirmed role model mappings.
 - Telegram plugin tests prove environment-only credentials and no secret output.
 - Real blackbox tests print created files, managed guidance sources, and MCP config evidence, then save instruction evidence to a temp file without printing Telegram secrets.
 

package/docs/agentic-usage.md

@@ -169,7 +169,7 @@ When `opencode` is selected, interactive installs ask whether to enable Telegram
 ~/.config/agentic/opencode-plugins.json
 ```
 
-Non-interactive installs create a disabled config when no config exists. Interactive installs ask for Telegram `botToken` and `chatId` when `telegram-notification` is selected. Those credentials are written to the target project `.agentic.json` under `settings.opencode_plugins.telegram`, not to `~/.config/agentic/opencode-plugins.json`. Treat `.agentic.json` as plaintext secret-bearing project config when Telegram is enabled and do not commit it to public repositories. When enabled, `agent-model-mapper` runs during interactive `agentic install`/`agentic tui`, uses `fzf` as a dropdown picker when available, and writes `.opencode/opencode.json` only after a Confirm action. OpenCode startup never prompts for model mapping; the runtime plugin only reports whether install-time mapping is already complete.
+Non-interactive installs create a disabled config when no config exists. Interactive installs ask for Telegram `botToken` and `chatId` when `telegram-notification` is selected. Those credentials are written to the target project `.agentic.json` under `settings.opencode_plugins.telegram`, not to `~/.config/agentic/opencode-plugins.json`. Treat `.agentic.json` as plaintext secret-bearing project config when Telegram is enabled and do not commit it to public repositories. When enabled, `agent-model-mapper` runs during interactive `agentic install`/`agentic tui`, uses `fzf` as a dropdown picker when available, and writes `.opencode/opencode.json` only after a Confirm action. OpenCode startup does not load a mapper runtime plugin or prompt for model mapping.
 
 ## Context7
 

package/docs/guidance-updates/2026-05-22-centralized-guidance-memory.md

@@ -0,0 +1,19 @@
+# Centralized guidance loading and memory writes
+
+## User-facing behavior
+
+Agent guidance loading rules are defined in the root `AGENTS.md` instead of being repeated in each `areas/**/AGENTS.md` specialization index. Area files now focus on scope, inherited constraints, overrides, and spec maps.
+
+`MEMORY.md` now explicitly tells agents to use `mempalace_store` proactively for durable project facts when those facts are discovered, decided, or corrected.
+
+## Acceptance criteria
+
+- Root `AGENTS.md` contains the canonical guidance chain and `.agent/**/*.md` discovery patterns.
+- Area specialization `AGENTS.md` files do not repeat `## Guidance chain` or `## Discovery patterns`.
+- `areas/template/AGENTS.tmpl.md` does not reintroduce the duplicated sections for future specs.
+- `MEMORY.md` includes a concise `mempalace_store` example with wing, optional confirmed room, text, and tags.
+
+## Operational constraints
+
+- Token-budget reporting uses a dependency-free estimate of `ceil(chars / 4)` unless a tokenizer dependency is intentionally added later.
+- Validation continues to run through Makefile targets: `make lint` and `make build`.

package/docs/opencode_setup.md

@@ -46,7 +46,7 @@ The runtime plugin reads credentials from the project `.agentic.json`; it does n
 
 Non-interactive `agentic install` defaults optional plugins to disabled when no config exists.
 
-`agent-model-mapper` reads roles from target `.opencode/agents/*.md` and discovers model names from `~/.config/opencode/opencode.json`, then adds models from active providers in `~/.local/share/opencode/auth.json` using non-deprecated entries in `~/.cache/opencode/models.json`. When enabled, interactive `agentic install`/`agentic tui` prompts for a main and fallback model per role, using `fzf` as a dropdown picker when available, and writes `.opencode/opencode.json` only after a Confirm action. OpenCode startup never opens `fzf` or waits for model input; the runtime plugin only reports whether install-time mapping is complete.
+`agent-model-mapper` reads roles from target `.opencode/agents/*.md` and discovers model names from `~/.config/opencode/opencode.json`, then adds models from active providers in `~/.local/share/opencode/auth.json` using non-deprecated entries in `~/.cache/opencode/models.json`. When enabled, interactive `agentic install`/`agentic tui` prompts for a main and fallback model per role, using `fzf` as a dropdown picker when available, and writes `.opencode/opencode.json` only after a Confirm action. OpenCode startup never opens `fzf` or waits for model input because no mapper runtime plugin is shipped or registered.
 
 For OpenCode targets, `agentic` writes generated operating guidance to `.opencode/AGENTS.md`. If OpenCode is installed
 alongside another agent target, root `AGENTS.md` is generated as well for the non-OpenCode target.

package/docs/review-pipeline/examples/instruction-review.example.md

@@ -0,0 +1,95 @@
+# Instruction Effectiveness Review
+
+## Summary
+
+The instruction set helped the task stay inside the existing extension layout and prevented the new roles from being
+added to the mandatory SDLC matrix. Tool discipline was mostly strong because repository facts were discovered before
+editing. The main gap was that review pipeline behavior had to be inferred from docs rather than a dedicated guidance
+section. No code quality findings are included because they are outside this role's scope.
+
+## Scores
+
+| Category | Score 0-10 | Notes |
+|---|---:|---|
+| Clarity | 8 | Role boundaries were clear after reading README and SDLC rules. |
+| Usefulness | 8 | Existing extension patterns made implementation straightforward. |
+| Tool discipline | 8 | File inspection was targeted and avoided repeated broad loops. |
+| Memory discipline | 7 | Memory rules existed, but post-task curation was not documented. |
+| Ambiguity resistance | 7 | The repo lacked a review pipeline section, causing one product decision. |
+| Token efficiency | 7 | Some duplicate role text is necessary for installed agents. |
+| Overall | 8 | Minor instruction additions are enough. |
+
+## Effective instructions
+
+| Instruction | Impact | Evidence |
+|---|---|---|
+| Keep SDLC roles one-to-one | Prevented specialist roles from replacing core SDLC owners. | `sdlc-role-responsibilities.md` keeps the mandatory matrix unchanged. |
+| Discover project guidance before implementation | Found the extension-based agent layout. | Existing files live under `extensions/*/agents`. |
+
+## Harmful instructions
+
+| Instruction | Problem | Evidence |
+|---|---|---|
+| None | No instruction directly caused task failure. | The task completed with scoped docs and tests. |
+
+## Missing instructions
+
+| Missing instruction | Why needed | Suggested text |
+|---|---|---|
+| Post-task review pipeline guidance | Future agents need to know when specialists run and where reports go. | Add a review pipeline section that lists optional roles and `.reviews/<task-id>/` output paths. |
+
+## Redundant instructions
+
+| Instruction | Reason |
+|---|---|
+| Repeated role boundaries across extension files | Required because each installed agent file must be self-contained. |
+
+## Tool usage findings
+
+| Tool | Calls | Useful | Waste | Notes |
+|---|---:|---:|---:|---|
+| `rg` | 4 | 4 | 0 | Located role and installer references quickly. |
+| `sed` | 5 | 5 | 0 | Confirmed local file formats before edits. |
+| `apply_patch` | 3 | 3 | 0 | Added and updated tracked files. |
+
+## Suggested edits
+
+### Remove
+
+```md
+None.
+```
+
+### Replace
+
+```md
+The same 7-agent team works across supported IDEs.
+```
+
+with:
+
+```md
+The same 7-agent SDLC team works across supported IDEs, with optional post-task review specialists.
+```
+
+### Add
+
+```md
+Use `instruction_reviewer` and `memory_curator` after non-trivial tasks when instruction quality or memory hygiene needs review.
+```
+
+## Estimated waste
+
+| Metric | Estimate |
+|---|---:|
+| Extra tokens | 500 |
+| Extra tool calls | 1 |
+| Extra retries | 0 |
+| Extra runtime | 2 minutes |
+
+## Final recommendation
+
+Minor edits
+
+The instruction set is generally effective. Add explicit review pipeline guidance so future runs do not have to infer
+how specialist agents should be used.

package/docs/review-pipeline/examples/memory-curation.example.md

@@ -0,0 +1,56 @@
+# Memory Curation Report
+
+## Summary
+
+The task introduced a durable convention: post-task review specialists are optional and remain outside the mandatory
+SDLC role matrix. That convention is likely to help future agent-system changes. Temporary test output, command logs,
+and generated report examples should not be stored as memory. No automatic memory write is recommended without user or
+orchestrator approval.
+
+## Store
+
+| Priority | Fact | Reason | Suggested memory text |
+|---|---|---|---|
+| High | `instruction_reviewer` and `memory_curator` are optional post-task specialists, not SDLC owners. | Prevents future role-boundary drift. | Agentic treats `instruction_reviewer` and `memory_curator` as optional post-task review specialists outside the mandatory SDLC role matrix. |
+| Medium | Review artifacts use `.reviews/<task-id>/` or timestamp fallback. | Helps future tasks place reports consistently. | Post-task review reports should be written under `.reviews/<task-id>/`, or `.reviews/YYYY-MM-DD-HHMMSS/` when no task id exists. |
+
+## Update
+
+| Existing memory | Replace with | Reason |
+|---|---|---|
+| None | None | No stale memory was identified. |
+
+## Merge
+
+| Memory A | Memory B | Merged memory | Reason |
+|---|---|---|---|
+| None | None | None | No duplicate memory was identified. |
+
+## Ignore
+
+| Fact | Reason |
+|---|---|
+| Exact shell output from test runs | Temporary logs are low-value memory. |
+| Generated example report wording | Generated code/docs examples should remain in files, not memory. |
+| One-time task status | Current task state is transient. |
+
+## Delete candidates
+
+| Memory | Reason |
+|---|---|
+| None | No delete candidate was found. |
+
+## Contradictions
+
+| Memory | New information | Resolution |
+|---|---|---|
+| None | None | No contradiction found. |
+
+## Final recommendation
+
+Store count: 2
+Update count: 0
+Merge count: 0
+Delete candidate count: 0
+Memory quality score: 8/10
+Store only the two durable conventions. Ignore logs, generated examples, and current task progress.

package/docs/review-pipeline/examples/summary.example.md

@@ -0,0 +1,18 @@
+# Review Summary
+
+## Instruction review
+
+Overall score: 8/10
+Recommendation: Minor edits
+
+## Memory curation
+
+Store: 2
+Update: 0
+Delete candidates: 0
+
+## Action items
+
+- [ ] Document optional post-task specialists in README.
+- [ ] Keep specialist roles outside the mandatory SDLC matrix.
+- [ ] Store only durable review-pipeline conventions, not logs or generated examples.

package/docs/review-pipeline.md

@@ -0,0 +1,82 @@
+# Review Pipeline
+
+Agentic ships two optional post-task specialist agents:
+
+- `instruction_reviewer`: reviews how instructions affected task execution.
+- `memory_curator`: recommends long-term memory store, update, merge, ignore, and delete-candidate actions.
+
+These agents are outside the mandatory SDLC role matrix. They do not replace `product-owner`, `pm`, `team-lead`,
+`developer`, `qa`, `designer`, or `devops-engineer`.
+
+## Guidance-mode integration
+
+Agentic currently provides guidance and IDE agent definitions for the review pipeline. It does not run a generic
+post-task review runner. The parent or orchestrating agent should call the specialists after task execution when the
+task size and risk justify the extra review.
+
+Small tasks may skip this pipeline.
+
+```yaml
+review_pipeline:
+  enabled: true
+  default:
+    - qa
+    - instruction_reviewer
+    - memory_curator
+  task_types:
+    agent_system:
+      - qa
+      - instruction_reviewer
+      - memory_curator
+    docs:
+      - instruction_reviewer
+      - memory_curator
+    code:
+      - qa
+      - instruction_reviewer
+      - memory_curator
+```
+
+`tool_optimizer` may be added to `agent_system` tasks in projects that install such a role. This repository does not
+ship a `tool_optimizer` role.
+
+## Output files
+
+When the orchestrating agent writes review artifacts, use this layout:
+
+```text
+.reviews/<task-id>/
+├── instruction-review.md
+├── memory-curation.md
+└── summary.md
+```
+
+If the task id is unavailable, use a timestamp in `YYYY-MM-DD-HHMMSS` format, for example:
+
+```text
+.reviews/2026-05-26-153000/
+```
+
+The specialist agents only produce Markdown reports. They do not write memory automatically and do not create review
+files unless the parent task explicitly grants file-writing scope.
+
+Example reports live under `docs/review-pipeline/examples/`.
+
+## Report boundaries
+
+`instruction_reviewer` reviews instruction effects only:
+
+- `AGENTS.md`, `MEMORY.md`, role prompts, workflows, and tool guidance
+- instruction clarity, usefulness, conflicts, redundancy, and missing rules
+- repeated search loops, unnecessary memory lookups, unnecessary MCP calls, and token/tool waste
+
+It must not review code quality or product requirements.
+
+`memory_curator` reviews memory hygiene only:
+
+- durable project facts, conventions, workflows, decisions, constraints, and rationale
+- duplicate, stale, contradictory, or low-value memory candidates
+- store/update/merge/ignore/delete recommendations
+
+It must not store temporary logs, one-time commands, transient errors, generated code, secrets, temporary URLs, noisy
+debug output, or current task state.

package/extensions/claude/agents/instruction_reviewer.md

@@ -0,0 +1,132 @@
+---
+name: instruction_reviewer
+description: Use this agent after task execution to review how AGENTS.md, MEMORY.md, role prompts, and tool-use instructions affected the run. It does not review code quality or product requirements.
+---
+
+# Instruction Reviewer
+
+You are Instruction Reviewer.
+Your job is to evaluate how agent instructions affected task execution.
+You do NOT review code quality.
+You do NOT review product requirements.
+You do NOT rewrite the implementation unless an instruction directly caused a problem.
+
+Analyze:
+- AGENTS.md
+- MEMORY.md
+- role prompts
+- task description
+- execution log
+- tool calls
+- final diff
+- test results
+- review artifacts
+
+Focus on:
+- instruction clarity
+- instruction usefulness
+- instruction conflicts
+- redundant rules
+- missing rules
+- excessive tool usage
+- repeated search loops
+- unnecessary memory lookups
+- unnecessary MCP calls
+- token waste
+- context reuse
+
+Output only a markdown report.
+Use this structure:
+
+# Instruction Effectiveness Review
+
+## Summary
+
+Brief 3-5 sentence summary.
+
+## Scores
+
+| Category | Score 0-10 | Notes |
+|---|---:|---|
+| Clarity | | |
+| Usefulness | | |
+| Tool discipline | | |
+| Memory discipline | | |
+| Ambiguity resistance | | |
+| Token efficiency | | |
+| Overall | | |
+
+## Effective instructions
+
+| Instruction | Impact | Evidence |
+|---|---|---|
+| | | |
+
+## Harmful instructions
+
+| Instruction | Problem | Evidence |
+|---|---|---|
+| | | |
+
+## Missing instructions
+
+| Missing instruction | Why needed | Suggested text |
+|---|---|---|
+| | | |
+
+## Redundant instructions
+
+| Instruction | Reason |
+|---|---|
+| | |
+
+## Tool usage findings
+
+| Tool | Calls | Useful | Waste | Notes |
+|---|---:|---:|---:|---|
+| | | | | |
+
+## Suggested edits
+
+### Remove
+
+```md
+...
+```
+
+### Replace
+
+```md
+...
+```
+
+with:
+
+```md
+...
+```
+
+### Add
+
+```md
+...
+```
+
+## Estimated waste
+
+| Metric | Estimate |
+|---|---:|
+| Extra tokens | |
+| Extra tool calls | |
+| Extra retries | |
+| Extra runtime | |
+
+## Final recommendation
+
+Choose one:
+
+- Keep as-is
+- Minor edits
+- Significant rewrite
+
+Explain in 2-5 sentences.