agentera 3.0.0-dev.6 → 3.0.0-dev.7

package/bundle/skills/agentera/capabilities/{dokumentera → document}/schemas/artifacts.yaml

@@ -5,24 +5,24 @@ ARTIFACTS:
     local_role: produces_and_consumes
     description: >-
       Documentation contract with conventions, artifact mapping, and
-      documentation index. Dokumentera writes and reads doc root, style
+      documentation index. Document writes and reads doc root, style
       conventions, auto-generated doc tracking, project-local artifact mappings,
       and a status index (current/stale/missing) for tracked docs. During
-      closeout, Dokumentera consumes docs state through CLI `closeout_context`
+      closeout, Document consumes docs state through CLI `closeout_context`
       before raw artifact fallback.
   2:
     id: A2
     artifact_id: vision
     local_role: consumes
     description: >-
-      Dokumentera reads this to understand who the documentation is for
+      Document reads this to understand who the documentation is for
       and what tone to use.
   3:
     id: A3
     artifact_id: progress
     local_role: consumes
     description: >-
-      Dokumentera reads this during explore-and-generate mode to understand
+      Document reads this during explore-and-generate mode to understand
       recent project context. During closeout, latest progress evidence and
       verification pointers are consumed through CLI `closeout_context` before
       raw artifact fallback.
@@ -31,21 +31,21 @@ ARTIFACTS:
     artifact_id: decisions
     local_role: consumes
     description: >-
-      Dokumentera reads this during explore-and-generate mode for project
+      Document reads this during explore-and-generate mode for project
       context and decision awareness.
   5:
     id: A5
     artifact_id: health
     local_role: consumes
     description: >-
-      Dokumentera reads this to discover documentation gaps surfaced
+      Document reads this to discover documentation gaps surfaced
       during health audits.
   6:
     id: A6
     artifact_id: todo
     local_role: produces_and_consumes
     description: >-
-      Dokumentera writes to this when code diverges from docs (per DTC,
+      Document writes to this when code diverges from docs (per DTC,
       the code is wrong). Also reads for context during documentation work;
       closeout blocker state is consumed through CLI `closeout_context` before
       raw artifact fallback.
@@ -54,20 +54,20 @@ ARTIFACTS:
     artifact_id: design
     local_role: consumes
     description: >-
-      Dokumentera reads this to respect the declared aesthetic and voice
+      Document reads this to respect the declared aesthetic and voice
       when generating user-facing documentation.
   8:
     id: A8
     artifact_id: profile
     local_role: consumes
     description: >-
-      Dokumentera reads this to calibrate documentation style preferences:
+      Document reads this to calibrate documentation style preferences:
       detail level, tone, format.
   9:
     id: A9
     artifact_id: changelog
     local_role: consumes
     description: >-
-      Dokumentera reads this during closeout synchronization through CLI
+      Document reads this during closeout synchronization through CLI
       `closeout_context` to preserve the changelog boundary and avoid inventing
       release, tag, publication, or remote state.

package/bundle/skills/agentera/capabilities/{dokumentera → document}/schemas/triggers.yaml

@@ -3,11 +3,15 @@ TRIGGERS:
     id: T1
     description: >-
       Direct invocation by name or slash command. Matches when the user
-      explicitly requests dokumentera.
+      explicitly requests document.
     priority: high
     patterns:
-      - "dokumentera"
-      - "/dokumentera"
+      - "document"
+      - "/document"
+    confidence_threshold: 60
+    borderline_band: 10
+    patterns_regex:
+      - "\\b/document\\b"
   2:
     id: T2
     description: >-
@@ -22,6 +26,7 @@ TRIGGERS:
       - "write AGENTS.md"
       - "docs first"
       - "document before building"
+    confidence_threshold: 50
   3:
     id: T3
     description: >-
@@ -33,3 +38,9 @@ TRIGGERS:
       - "audit docs"
       - "check documentation"
       - "docs out of sync"
+    confidence_threshold: 50
+    disambiguates_against:
+      - capability: audit
+        hint: "document maintains project docs; audit reviews codebase health"
+    patterns_regex:
+      - "\\baudit\\s+docs?\\b"

package/bundle/skills/agentera/capabilities/{dokumentera → document}/schemas/validation.yaml

@@ -73,8 +73,8 @@ VALIDATION:
     id: V8
     rule: exit_marker_required
     description: >-
-      Every dokumentera invocation MUST emit an exit marker using the
-      canonical glyph ▤ (SG8) in the format ▤ dokumentera · <status>
+      Every document invocation MUST emit an exit marker using the
+      canonical glyph ▤ (SG8) in the format ▤ document · <status>
       where status is one of EX1-EX4.
     severity: critical
     checks:
@@ -85,22 +85,22 @@ VALIDATION:
     id: V9
     rule: closeout_context_first
     description: >-
-      During final synchronization, Dokumentera MUST use `agentera prime
-      --context dokumentera --format json` and its `closeout_context`
+      During final synchronization, Document MUST use `agentera prime
+      --context document --format json` and its `closeout_context`
       before reading TODO, docs, changelog, or progress artifacts directly.
       Complete closeout context is the normal source for mappings, version
       policy, blockers, boundaries, progress evidence, benchmark evidence,
       caveats, fallback commands, raw-read policy, and completeness.
     severity: critical
     checks:
-      - "Closeout starts from hej capability context"
+      - "Closeout starts from status capability context"
       - "Complete closeout_context is used before raw artifact reads"
       - "Completeness and non-empty evidence flags are preserved"
   10:
     id: V10
     rule: closeout_fallback_before_raw
     description: >-
-      If closeout context is incomplete or caveated, Dokumentera MUST run the
+      If closeout context is incomplete or caveated, Document MUST run the
       listed existing CLI fallback commands before any last-resort raw artifact
       read. No unsupported capability-name command or new closeout command may
       be introduced.
@@ -113,7 +113,7 @@ VALIDATION:
     id: V11
     rule: closeout_caveat_preservation
     description: >-
-      Dokumentera MUST preserve closeout caveats about stale app/profile state,
+      Document MUST preserve closeout caveats about stale app/profile state,
       compacted or missing state, missing benchmark evidence, absent local
       metadata or tags, and unrecorded publication or remote state. Caveats must
       not be hidden, reconstructed, or converted into approval to refresh apps,
@@ -127,7 +127,7 @@ VALIDATION:
     id: V12
     rule: satisfaction_authority_boundary
     description: >-
-      When Dokumentera touches decision satisfaction, it may record provisional
+      When Document touches decision satisfaction, it may record provisional
       satisfaction with evidence but MUST NOT user-confirm satisfaction. Missing,
       compacted, open, provisional, or review-needed satisfaction state remains a
       caveat and review pressure; automation must not reconstruct hidden outcomes

package/bundle/skills/agentera/capabilities/{optimera → optimize}/schemas/artifacts.yaml

@@ -5,7 +5,7 @@ ARTIFACTS:
     local_role: produces_and_consumes
     description: >-
       Optimization target definition: metric, current value, target, constraints,
-      scope, and measurement approach. Optimera writes this during brainstorm
+      scope, and measurement approach. Optimize writes this during brainstorm
       and reads it every cycle. Written to only during brainstorm, refine, or
       canonical closure.
   2:
@@ -23,41 +23,41 @@ ARTIFACTS:
     description: >-
       Log of every experiment: hypothesis, method, change, metric before/after,
       regression result, status (kept/discarded/error), conclusion, and next
-      suggestion. Optimera appends to this each cycle.
+      suggestion. Optimize appends to this each cycle.
   4:
     id: A4
     artifact_id: progress
     local_role: consumes
     description: >-
-      Optimera inspects the last 3 entries to detect 3 consecutive failures
+      Optimize inspects the last 3 entries to detect 3 consecutive failures
       before reporting exit status.
   5:
     id: A5
     artifact_id: todo
     local_role: produces
     description: >-
-      Optimera writes to this when logging a failure pattern after 3
+      Optimize writes to this when logging a failure pattern after 3
       consecutive failures.
   6:
     id: A6
     artifact_id: decisions
     local_role: consumes
     description: >-
-      Optimera reads this during Orient for context on prior deliberations
+      Optimize reads this during Orient for context on prior deliberations
       about the optimization objective.
   7:
     id: A7
     artifact_id: profile
     local_role: consumes
     description: >-
-      Optimera reads this to modulate experiment aggressiveness and constraint
+      Optimize reads this to modulate experiment aggressiveness and constraint
       tolerance based on user preferences.
   8:
     id: A8
     artifact_id: docs
     local_role: consumes
     description: >-
-      Optimera reads this first to resolve project-local artifact mappings
+      Optimize reads this first to resolve project-local artifact mappings
       before accessing other artifacts.
   9:
     id: A9
@@ -65,5 +65,5 @@ ARTIFACTS:
     local_role: consumes
     description: >-
       CLI-provided startup benchmark summary from `agentera prime --context
-      optimera --format json`. Optimera consumes this before any direct
+      optimize --format json`. Optimize consumes this before any direct
       latest-report.json, latest-report.md, or runs.jsonl diagnostic read.

package/bundle/skills/agentera/capabilities/{optimera → optimize}/schemas/triggers.yaml

@@ -3,11 +3,16 @@ TRIGGERS:
     id: T1
     description: >-
       Direct invocation by name or slash command. Matches when the user
-      explicitly requests optimera.
+      explicitly requests optimize.
     priority: high
     patterns:
-      - "optimera"
-      - "/optimera"
+      - "optimize"
+      - "/optimize"
+    confidence_threshold: 60
+    borderline_band: 20
+    disambiguates_against:
+      - capability: audit
+        hint: "optimize tunes existing code; audit reviews codebase health"
   2:
     id: T2
     description: >-
@@ -26,6 +31,8 @@ TRIGGERS:
       - "get the score up"
       - "hit the target"
       - "improve the metric"
+    confidence_threshold: 50
+    borderline_band: 20
   3:
     id: T3
     description: >-
@@ -37,3 +44,4 @@ TRIGGERS:
       - "run experiments"
       - "tune"
       - "experiment until"
+    confidence_threshold: 50

package/bundle/skills/agentera/capabilities/{optimera → optimize}/schemas/validation.yaml

@@ -34,7 +34,7 @@ VALIDATION:
     id: V4
     rule: one_experiment_per_invocation
     description: >-
-      Each optimera invocation performs exactly one experiment. Multiple
+      Each optimize invocation performs exactly one experiment. Multiple
       experiments require multiple invocations or /loop setup.
     severity: critical
     checks:
@@ -53,8 +53,8 @@ VALIDATION:
     id: V6
     rule: exit_marker_required
     description: >-
-      Every optimera invocation MUST emit an exit marker. The marker uses
-      the canonical glyph ⎘ (SG7) in the format ⎘ optimera · <status>
+      Every optimize invocation MUST emit an exit marker. The marker uses
+      the canonical glyph ⎘ (SG7) in the format ⎘ optimize · <status>
       where status is one of EX1-EX4.
     severity: critical
     checks:
@@ -65,21 +65,21 @@ VALIDATION:
     id: V7
     rule: benchmark_context_first
     description: >-
-      For benchmark-oriented startup, Optimera MUST start from `agentera prime
-      --context optimera --format json` and consume complete
+      For benchmark-oriented startup, Optimize MUST start from `agentera prime
+      --context optimize --format json` and consume complete
       benchmark_context before direct retained benchmark file reads. Direct
       latest-report.json, latest-report.md, or runs.jsonl reads are last-resort
       diagnostics only when the CLI context is incomplete.
     severity: critical
     checks:
-      - "Optimera startup uses benchmark_context before direct retained benchmark files"
+      - "Optimize startup uses benchmark_context before direct retained benchmark files"
       - "Incomplete benchmark_context follows listed CLI fallback and manual refresh guidance"
       - "Direct benchmark file reads are treated as last-resort diagnostics"
   8:
     id: V8
     rule: benchmark_caveat_preservation
     description: >-
-      Benchmark caveats from benchmark_context MUST be preserved when Optimera
+      Benchmark caveats from benchmark_context MUST be preserved when Optimize
       reports measurement evidence. Agents must not hide, upgrade, reconstruct,
       or infer away caveats for manual-only execution, missing local history,
       runtime coverage degradation, missing token estimates, non-comparable

package/bundle/skills/agentera/capabilities/{orkestrera → orchestrate}/schemas/artifacts.yaml

@@ -4,8 +4,8 @@ ARTIFACTS:
     artifact_id: plan
     local_role: produces_and_consumes
     description: >-
-      Orkestrera consumes plan task queue state through
-      `agentera prime --context orkestrera --format json` before raw
+      Orchestrate consumes plan task queue state through
+      `agentera prime --context orchestrate --format json` before raw
       artifact access, then updates status (pending -> complete/blocked) only
       when resolving a task.
   2:
@@ -13,7 +13,7 @@ ARTIFACTS:
     artifact_id: progress
     local_role: consumes
     description: >-
-      Orkestrera consumes progress verification state from the returned
+      Orchestrate consumes progress verification state from the returned
       orchestration context first, then routine CLI fallback output before any
       last-resort raw artifact read for the Step 3 presence check.
   3:
@@ -21,7 +21,7 @@ ARTIFACTS:
     artifact_id: health
     local_role: consumes
     description: >-
-      Orkestrera consumes returned health state first after plan completion to
+      Orchestrate consumes returned health state first after plan completion to
       decide whether to start a new plan cycle; raw reads are last-resort after
       listed CLI fallbacks.
   4:
@@ -29,14 +29,14 @@ ARTIFACTS:
     artifact_id: todo
     local_role: produces
     description: >-
-      Orkestrera consumes TODO caveats from CLI startup context and writes
+      Orchestrate consumes TODO caveats from CLI startup context and writes
       blocked task logging only when a task exhausts its retry budget.
   5:
     id: A5
     artifact_id: decisions
     local_role: consumes
     description: >-
-      Orkestrera consumes included decision context or the listed
+      Orchestrate consumes included decision context or the listed
       `agentera decisions --format json` fallback before raw access, preserving
       firm constraints, exploratory uncertainties, and compacted-entry caveats.
   6:
@@ -44,14 +44,14 @@ ARTIFACTS:
     artifact_id: vision
     local_role: consumes
     description: >-
-      Orkestrera consumes returned vision state or missing-state caveats during
-      bootstrap when chaining inspirera for vision-gap analysis.
+      Orchestrate consumes returned vision state or missing-state caveats during
+      bootstrap when chaining research for vision-gap analysis.
   7:
     id: A7
     artifact_id: profile
     local_role: consumes
     description: >-
-      Orkestrera consumes returned profile status and caveats first for persona
+      Orchestrate consumes returned profile status and caveats first for persona
       context. If missing or stale, it proceeds without refreshing profile
       state and preserves the caveat.
   8:
@@ -59,6 +59,6 @@ ARTIFACTS:
     artifact_id: docs
     local_role: consumes
     description: >-
-      Orkestrera uses docs mapping from CLI startup context first to resolve
+      Orchestrate uses docs mapping from CLI startup context first to resolve
       project-local artifact mappings before any last-resort raw artifact read
       or artifact write.

package/bundle/skills/agentera/capabilities/{orkestrera → orchestrate}/schemas/triggers.yaml

@@ -3,11 +3,15 @@ TRIGGERS:
     id: T1
     description: >-
       Direct invocation by name or slash command. Matches when the user
-      explicitly requests orkestrera.
+      explicitly requests orchestrate.
     priority: high
     patterns:
-      - "orkestrera"
-      - "/orkestrera"
+      - "orchestrate"
+      - "/orchestrate"
+    confidence_threshold: 60
+    borderline_band: 10
+    patterns_regex:
+      - "\\b/orchestrate\\b"
   2:
     id: T2
     description: >-
@@ -21,6 +25,10 @@ TRIGGERS:
       - "keep going until done"
       - "run through the plan"
       - "build everything"
+    confidence_threshold: 55
+    disambiguates_against:
+      - capability: build
+        hint: "orchestrate runs the whole plan autonomously; build executes one development cycle"
   3:
     id: T3
     description: >-
@@ -32,6 +40,7 @@ TRIGGERS:
       - "orchestrate"
       - "orchestrate skills"
       - "multi-cycle"
+    confidence_threshold: 50
   4:
     id: T4
     description: >-
@@ -40,3 +49,7 @@ TRIGGERS:
     priority: medium
     patterns:
       - "autonomous plan execution"
+    confidence_threshold: 50
+    disambiguates_against:
+      - capability: build
+        hint: "orchestrate chains multi-cycle execution; build runs a single cycle"

package/bundle/skills/agentera/capabilities/{orkestrera → orchestrate}/schemas/validation.yaml

@@ -3,24 +3,24 @@ VALIDATION:
     id: V1
     rule: never_read_source
     description: >-
-      Orkestrera MUST NEVER read implementation source code. It dispatches
+      Orchestrate MUST NEVER read implementation source code. It dispatches
       capabilities; it does not implement. Artifact files (PLAN.md, HEALTH.md,
       DECISIONS.md, PROGRESS.md, etc.) are not source code and are expected
       to be read. This rule verifies the prose explicitly states the
       source-code read prohibition.
     severity: critical
     checks:
-      - "orkestrera prose (packages/cli/src/capabilities/orkestrera/instructions.ts) contains NEVER read implementation source code"
+      - "orchestrate prose (packages/cli/src/capabilities/orchestrate/instructions.ts) contains NEVER read implementation source code"
   2:
     id: V2
     rule: evaluation_gate_required
     description: >-
-      Every completed task MUST be verified by inspektera before being marked
+      Every completed task MUST be verified by audit before being marked
       complete. The orchestrator MUST NOT skip evaluation. This rule verifies
       the prose contains the never-skip-evaluation safety rail.
     severity: critical
     checks:
-      - "orkestrera prose contains NEVER skip evaluation"
+      - "orchestrate prose contains NEVER skip evaluation"
   3:
     id: V3
     rule: retry_budget_enforced
@@ -30,18 +30,18 @@ VALIDATION:
       is stated in the prose and safety rails.
     severity: critical
     checks:
-      - "orkestrera prose contains retry budget of 2"
+      - "orchestrate prose contains retry budget of 2"
   4:
     id: V4
     rule: exit_marker_required
     description: >-
-      Every orkestrera invocation MUST emit an exit marker. The marker uses
-      the canonical glyph ⎈ (SG12) in the format ⎈ orkestrera · <status>
+      Every orchestrate invocation MUST emit an exit marker. The marker uses
+      the canonical glyph ⎈ (SG12) in the format ⎈ orchestrate · <status>
       where status is one of EX1-EX4.
     severity: critical
     checks:
-      - "orkestrera prose contains exit marker with glyph ⎈ (SG12)"
-      - "orkestrera prose references exit signals EX1-EX4"
+      - "orchestrate prose contains exit marker with glyph ⎈ (SG12)"
+      - "orchestrate prose references exit signals EX1-EX4"
   5:
     id: V5
     rule: orchestrator_read_only_artifacts
@@ -60,42 +60,42 @@ VALIDATION:
     id: V6
     rule: orchestration_context_first
     description: >-
-      Orkestrera startup and evaluation MUST use
-      `agentera prime --context orkestrera --format json` and the
+      Orchestrate startup and evaluation MUST use
+      `agentera prime --context orchestrate --format json` and the
       returned orchestration context before raw plan, progress, health, TODO,
       or decisions artifact reads.
     severity: critical
     checks:
-      - "orkestrera prose contains agentera prime --context orkestrera --format json"
-      - "orkestrera prose contains Use the returned `orchestration_context` before raw plan, progress, health, TODO, or decisions artifacts"
-      - "orkestrera prose contains If `source_contract.complete_for_orchestration_context` is true, do not read raw plan, progress, health, TODO, or decisions artifacts"
+      - "orchestrate prose contains agentera prime --context orchestrate --format json"
+      - "orchestrate prose contains Use the returned `orchestration_context` before raw plan, progress, health, TODO, or decisions artifacts"
+      - "orchestrate prose contains If `source_contract.complete_for_orchestration_context` is true, do not read raw plan, progress, health, TODO, or decisions artifacts"
   7:
     id: V7
     rule: cli_fallback_before_raw_read
     description: >-
-      When orchestration context is incomplete, Orkestrera MUST run listed
+      When orchestration context is incomplete, Orchestrate MUST run listed
       routine CLI fallback commands before any last-resort raw artifact read.
     severity: critical
     checks:
-      - "orkestrera prose contains run the listed routine CLI fallback commands"
-      - "orkestrera prose contains Read a raw artifact only as a last-resort diagnostic"
+      - "orchestrate prose contains run the listed routine CLI fallback commands"
+      - "orchestrate prose contains Read a raw artifact only as a last-resort diagnostic"
   8:
     id: V8
     rule: caveats_preserved_for_evaluation
     description: >-
-      Orkestrera MUST preserve compacted-decision, stale health/profile/app,
+      Orchestrate MUST preserve compacted-decision, stale health/profile/app,
       missing-state, and retry-state provenance caveats when handing a task to
-      inspektera.
+      audit.
     severity: critical
     checks:
-      - "orkestrera prose contains compacted decision caveats"
-      - "orkestrera prose contains stale health/profile/app caveats"
-      - "orkestrera prose contains retry-state provenance"
+      - "orchestrate prose contains compacted decision caveats"
+      - "orchestrate prose contains stale health/profile/app caveats"
+      - "orchestrate prose contains retry-state provenance"
   9:
     id: V9
     rule: satisfaction_authority_boundary
     description: >-
-      When Orkestrera touches decision satisfaction, it may pass through or request
+      When Orchestrate touches decision satisfaction, it may pass through or request
       provisional satisfaction with evidence but MUST NOT user-confirm satisfaction.
       Missing, compacted, open, provisional, or review-needed satisfaction state
       remains a caveat and review pressure; automation must not reconstruct hidden
@@ -109,12 +109,12 @@ VALIDATION:
     id: V10
     rule: inspektera_citation_required
     description: >-
-      Orkestrera Step 3 Surface 2 inspektera delegation MUST require a
+      Orchestrate Step 3 Surface 2 audit delegation MUST require a
       citation: <file>:<line> (or not-applicable: <reason>) for every WARN and
       FAIL finding, and require verify_command for WARN rows with file:line
       citations. Authority: references/cli/capability-instruction-contract.yaml#evaluator_handoff.
     severity: critical
     checks:
-      - "orkestrera prose contains citation: `<file>:<line>` OR `not-applicable: <reason>`"
-      - "orkestrera prose contains verify_command"
-      - "orkestrera prose contains evaluator_handoff.output_requirements"
+      - "orchestrate prose contains citation: `<file>:<line>` OR `not-applicable: <reason>`"
+      - "orchestrate prose contains verify_command"
+      - "orchestrate prose contains evaluator_handoff.output_requirements"

package/bundle/skills/agentera/capabilities/{planera → plan}/schemas/artifacts.yaml

@@ -5,7 +5,7 @@ ARTIFACTS:
     local_role: produces_and_consumes
     description: >-
       Active plan with tasks, dependencies, and behavioral acceptance criteria.
-      Planera writes this during the planning session and may read existing
+      Plan writes this during the planning session and may read existing
       plan context before replacing or refining it.
   2:
     id: A2
@@ -20,43 +20,43 @@ ARTIFACTS:
     artifact_id: vision
     local_role: consumes
     description: >-
-      Planera reads this during Orient to understand project direction and
+      Plan reads this during Orient to understand project direction and
       align the plan with the vision.
   4:
     id: A4
     artifact_id: decisions
     local_role: consumes
     description: >-
-      Planera reads firm (DL1) entries only as hard constraints for planning.
+      Plan reads firm (DL1) entries only as hard constraints for planning.
   5:
     id: A5
     artifact_id: todo
     local_role: consumes
     description: >-
-      Planera reads this to identify related known
+      Plan reads this to identify related known
       issues that the plan should address.
   6:
     id: A6
     artifact_id: health
     local_role: consumes
     description: >-
-      Planera reads this to factor structural issues into the plan.
+      Plan reads this to factor structural issues into the plan.
   7:
     id: A7
     artifact_id: progress
     local_role: consumes
     description: >-
-      Planera reads this to understand what was built recently.
+      Plan reads this to understand what was built recently.
   8:
     id: A8
     artifact_id: profile
     local_role: consumes
     description: >-
-      Planera reads this to calibrate planning depth and pattern preferences.
+      Plan reads this to calibrate planning depth and pattern preferences.
   9:
     id: A9
     artifact_id: docs
     local_role: consumes
     description: >-
-      Planera reads this first to resolve project-local artifact mappings and
+      Plan reads this first to resolve project-local artifact mappings and
       reads the versioning block for version bump task generation.

package/bundle/skills/agentera/capabilities/{planera → plan}/schemas/exit.yaml

@@ -4,8 +4,8 @@ EXIT_CONDITIONS:
     condition: complete
     description: >-
       PLAN.md was written and approved (or skip level confirmed), the
-      adversarial review ran for full plans, and the handoff to realisera
-      or orkestrera was suggested.
+      adversarial review ran for full plans, and the handoff to build
+      or orchestrate was suggested.
     exit_signal: complete
   2:
     id: E2

package/bundle/skills/agentera/capabilities/{planera → plan}/schemas/triggers.yaml

@@ -3,11 +3,15 @@ TRIGGERS:
     id: T1
     description: >-
       Direct invocation by name or slash command. Matches when the user
-      explicitly requests planera for structured planning.
+      explicitly requests plan for structured planning.
     priority: high
     patterns:
-      - "planera"
-      - "/planera"
+      - "plan"
+      - "/plan"
+    confidence_threshold: 60
+    borderline_band: 10
+    patterns_regex:
+      - "\\b/plan\\b"
   2:
     id: T2
     description: >-
@@ -21,6 +25,10 @@ TRIGGERS:
       - "decompose this"
       - "spec this out"
       - "plan before building"
+    confidence_threshold: 50
+    disambiguates_against:
+      - capability: build
+        hint: "plan structures work into tasks before coding; build implements the work"
   3:
     id: T3
     description: >-
@@ -32,3 +40,7 @@ TRIGGERS:
       - "how should we build this"
       - "multi-step feature"
       - "this is too big for one cycle"
+    confidence_threshold: 50
+    disambiguates_against:
+      - capability: build
+        hint: "plan sizes work before implementation; build runs the development cycle"