fix: slim down token usage

.agent/controllers/teamwise-prompt-lens/goal.md

@@ -0,0 +1,12 @@
+# Goal
+
+Turn rough user prompts entered into the controller goal planner into clear, production-quality improvement briefs shaped by a cross-functional software team.
+
+The controller should:
+- reinterpret ambiguous or sloppy requests through the perspectives of an architect, product owner, senior engineer, QA engineer, and other relevant software roles;
+- surface missing context, risks, constraints, edge cases, and acceptance criteria before execution begins;
+- rewrite the original request into a coherent codebase-improvement prompt that is specific, technically credible, and ready for autonomous planning or implementation;
+- prefer maintainable, incremental improvements over novelty or one-off solutions;
+- produce outputs that help downstream agents make sound architectural, implementation, testing, and rollout decisions with minimal back-and-forth.
+
+Success means a weak initial prompt becomes a well-scoped, team-reviewed execution brief with explicit goals, assumptions, constraints, risks, and verification expectations.

.agent/controllers/teamwise-prompt-lens/plan.toon

@@ -0,0 +1,89 @@
+version: 1
+goal_summary: "Define a team-oriented planning controller that transforms rough prompts into implementation-ready improvement briefs using cross-functional software perspectives."
+steps[6]:
+  - id: "step-01"
+    title: Audit Current Controller Artifacts
+    purpose: "Inspect the existing goal, standards, plan, and state files to replace placeholders and preserve any useful structure."
+    notes: "The current controller files are placeholder-heavy and need concrete intent before automation can rely on them. One or more commands failed"
+    inputs[4]: ".agent/controllers/teamwise-prompt-lens/goal.md",".agent/controllers/teamwise-prompt-lens/standards.md",".agent/controllers/teamwise-prompt-lens/plan.toon",".agent/controllers/teamwise-prompt-lens/state.toon"
+    outputs[3]: Confirmed file inventory,List of placeholder content to replace,Any existing TOON structure worth preserving
+    dependencies[0]:
+    verification[1]:
+      - label: Read current controller files
+        commands[4]: "sed -n '1,200p' .agent/controllers/teamwise-prompt-lens/goal.md","sed -n '1,240p' .agent/controllers/teamwise-prompt-lens/standards.md","sed -n '1,240p' .agent/controllers/teamwise-prompt-lens/plan.toon","sed -n '1,240p' .agent/controllers/teamwise-prompt-lens/state.toon"
+    cleanup_requirements[1]{label,description}:
+      No stale placeholders,Remove generic placeholder text once the real controller intent is documented.
+    status: active
+    attempts: 4
+  - id: "step-02"
+    title: "Define Cross-Functional Prompt Lens"
+    purpose: "Specify the software-team roles and the exact review dimensions each role contributes to prompt improvement."
+    notes: The controller needs explicit personas so it consistently upgrades prompts instead of producing generic rewrites.
+    inputs[2]: "User request for architect, QA, senior engineer, product owner, and broader team input","Findings from step-01"
+    outputs[3]: Role list for the prompt lens,"Per-role review criteria",Rules for when to include or omit additional roles
+    dependencies[1]: "step-01"
+    verification[1]:
+      - label: Check role coverage in artifacts
+        commands[1]: "rg -n \"architect|product|senior engineer|qa|operations|security|performance\" .agent/controllers/teamwise-prompt-lens"
+    cleanup_requirements[1]{label,description}:
+      Avoid role sprawl,Keep the persona set opinionated and reusable rather than listing every possible specialty.
+    status: todo
+    attempts: 0
+  - id: "step-03"
+    title: Rewrite Goal And Standards
+    purpose: "Replace the placeholder Markdown with controller-specific guidance that matches the desired teamwise prompt transformation behavior."
+    notes: The goal and standards must be explicit because downstream planning quality depends on them.
+    inputs[2]: "Outputs from step-01","Outputs from step-02"
+    outputs[2]: "Updated .agent/controllers/teamwise-prompt-lens/goal.md","Updated .agent/controllers/teamwise-prompt-lens/standards.md"
+    dependencies[1]: "step-02"
+    verification[1]:
+      - label: Validate rewritten Markdown content
+        commands[3]: "sed -n '1,240p' .agent/controllers/teamwise-prompt-lens/goal.md","sed -n '1,260p' .agent/controllers/teamwise-prompt-lens/standards.md","rg -n \"Describe the goal for this controller|placeholder|TODO\" .agent/controllers/teamwise-prompt-lens/goal.md .agent/controllers/teamwise-prompt-lens/standards.md"
+    cleanup_requirements[1]{label,description}:
+      Keep standards actionable,Remove vague quality slogans unless they imply a concrete execution rule.
+    status: todo
+    attempts: 0
+  - id: "step-04"
+    title: Author Planner Workflow In TOON
+    purpose: "Encode the planning workflow so the controller consistently turns sloppy prompts into structured, execution-ready briefs."
+    notes: The main behavioral logic belongs in the plan file because the controller is operating in planning mode.
+    inputs[2]: Rewritten goal and standards,"Cross-functional prompt lens definition"
+    outputs[2]: "Updated .agent/controllers/teamwise-prompt-lens/plan.toon with ordered planning behavior","Explicit output sections for rewritten prompt, assumptions, risks, acceptance criteria, and verification"
+    dependencies[1]: "step-03"
+    verification[1]:
+      - label: Review plan structure
+        commands[2]: "sed -n '1,260p' .agent/controllers/teamwise-prompt-lens/plan.toon","rg -n \"assumptions|risks|acceptance criteria|verification|rewrite|team\" .agent/controllers/teamwise-prompt-lens/plan.toon"
+    cleanup_requirements[1]{label,description}:
+      No dead branches,Remove unused workflow branches or duplicate instructions that would confuse autonomous execution.
+    status: todo
+    attempts: 0
+  - id: "step-05"
+    title: Initialize Stateful Planning Data
+    purpose: "Define the minimal controller state needed to track prompt quality, assumptions, open questions, and plan readiness across runs."
+    notes: State should stay minimal so the controller remains predictable and maintainable.
+    inputs[2]: "Planner workflow from step-04","Existing .agent/controllers/teamwise-prompt-lens/state.toon"
+    outputs[2]: "Updated .agent/controllers/teamwise-prompt-lens/state.toon","Stable state fields for prompt intake, role synthesis, assumptions, risks, and completion status"
+    dependencies[1]: "step-04"
+    verification[1]:
+      - label: Inspect state schema
+        commands[2]: "sed -n '1,240p' .agent/controllers/teamwise-prompt-lens/state.toon","rg -n \"prompt|assumption|risk|question|ready|status\" .agent/controllers/teamwise-prompt-lens/state.toon"
+    cleanup_requirements[1]{label,description}:
+      Avoid overspecified state,Remove transient or redundant fields that do not support repeated planning runs.
+    status: todo
+    attempts: 0
+  - id: "step-06"
+    title: Validate With Representative Prompt Cases
+    purpose: Check that the controller can upgrade rough prompts into clearer briefs without losing user intent.
+    notes: A few realistic examples are the fastest way to catch missing sections or overcomplicated output rules.
+    inputs[2]: Updated controller artifacts,Representative sloppy prompts about codebase improvements
+    outputs[2]: Validation notes,"Any final wording adjustments to goal, standards, plan, or state"
+    dependencies[1]: "step-05"
+    verification[2]:
+      - label: Run artifact review against sample prompts
+        commands[4]: "sed -n '1,260p' .agent/controllers/teamwise-prompt-lens/goal.md","sed -n '1,260p' .agent/controllers/teamwise-prompt-lens/standards.md","sed -n '1,320p' .agent/controllers/teamwise-prompt-lens/plan.toon","sed -n '1,260p' .agent/controllers/teamwise-prompt-lens/state.toon"
+      - label: Final placeholder sweep
+        commands[1]: "rg -n \"TODO|placeholder|Describe the goal for this controller|TBD\" .agent/controllers/teamwise-prompt-lens"
+    cleanup_requirements[1]{label,description}:
+      Remove ad hoc examples,"Do not leave validation-only sample prompts in production controller files unless intentionally documented."
+    status: todo
+    attempts: 0

.agent/controllers/teamwise-prompt-lens/standards.md

@@ -0,0 +1,13 @@
+# Standards
+
+- Treat every incoming prompt as incomplete until assumptions, constraints, and success criteria are made explicit.
+- Synthesize perspectives from architecture, product, engineering, QA, and operations when they materially affect the outcome.
+- Optimize for maintainable codebase improvements, not clever one-off patches.
+- Preserve the user's core intent while upgrading precision, scope control, and technical quality.
+- Make missing information visible as assumptions or open questions instead of silently inventing product or system behavior.
+- Require clear deliverables, acceptance criteria, and verification expectations in the rewritten prompt.
+- Call out risks, dependencies, migration concerns, and likely regression areas when relevant.
+- Keep outputs concise enough for autonomous execution, but complete enough to avoid avoidable follow-up.
+- Prefer incremental, reviewable changes that can keep tests green throughout execution.
+- Eliminate placeholder language, vague directives, and non-actionable advice from controller artifacts.
+- Leave tests green.