agentera 3.0.0-dev.26 → 3.0.0-dev.28

package/bundle/skills/agentera/capabilities/audit/schemas/triggers.yaml

@@ -1,47 +1,25 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests audit.
+    description: Audit local codebase health, architecture, quality, or technical debt.
     priority: high
-    patterns:
-      - "audit"
-      - "/audit"
-    confidence_threshold: 60
-    borderline_band: 10
-    patterns_regex:
-      - "\\b/audit\\b"
   2:
     id: T2
-    description: >-
-      Audit and codebase health requests. Matches when the user wants to
-      assess codebase health, architecture quality, or structural integrity.
-    priority: medium
-    patterns:
-      - "audit the codebase"
-      - "check code health"
-      - "architecture review"
-      - "find technical debt"
-      - "assess code quality"
-      - "how healthy is this codebase"
-      - "what needs fixing"
-      - "structural review"
-      - "pattern audit"
-      - "dependency check"
-      - "test coverage audit"
-    confidence_threshold: 55
+    description: Review the local repository's code, architecture, dependencies, or structural health.
+    priority: high
+    disambiguates_against:
+      - capability: research
+        hint: "audit reviews this local codebase; research analyzes an external source or repository"
+      - capability: document
+        hint: "audit owns code and architecture health; document owns documentation maintenance and docs audits"
+      - capability: design
+        hint: "audit owns code and architecture health; design owns visual identity and design-system review"
+      - capability: optimize
+        hint: "audit assesses local health; optimize improves an existing system against a measurable target"
   3:
     id: T3
-    description: >-
-      Implicit trigger after extended build activity. Matches when
-      build has run 5+ cycles without a health check and the system
-      detects an overdue audit.
+    description: Review local health after implementation activity reveals a need for assessment.
     priority: medium
-    patterns:
-      - "health check overdue"
-      - "audit after build"
-    confidence_threshold: 50
     disambiguates_against:
       - capability: build
         hint: "audit checks codebase health after build activity; build continues development"

package/bundle/skills/agentera/capabilities/build/schemas/triggers.yaml

@@ -1,49 +1,27 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests build for autonomous development.
+    description: A scoped implementation task or one verified development cycle.
     priority: high
-    patterns:
-      - "build"
-      - "/build"
-    confidence_threshold: 60
-    borderline_band: 10
   2:
     id: T2
-    description: >-
-      Development cycle requests. Matches when the user wants to run an
-      autonomous development cycle or evolve the project.
-    priority: medium
-    patterns:
-      - "run a dev cycle"
-      - "evolve the project"
-      - "develop autonomously"
-      - "build the next feature"
-    confidence_threshold: 50
+    description: Implement one requested feature, fix, or bounded development task.
+    priority: high
+    disambiguates_against:
+      - capability: vision
+        hint: "build implements code; vision defines or refines project direction"
+      - capability: profile
+        hint: "build implements a software task; profile builds a reusable decision profile"
+      - capability: orchestrate
+        hint: "build completes one task or cycle; orchestrate runs an entire plan or multiple tasks"
   3:
     id: T3
-    description: >-
-      Continuous development signals. Matches when the user wants ongoing
-      building or to start working on the project.
+    description: Start or continue a single concrete implementation task.
     priority: medium
-    patterns:
-      - "keep building"
-      - "start building"
-      - "work on the project"
-    confidence_threshold: 50
   4:
     id: T4
-    description: >-
-      Vision refinement within a development context. Matches when the user
-      wants to refine the project vision as part of a development session.
+    description: Implement a scoped task after its plan or requirements are established.
     priority: medium
-    patterns:
-      - "refine the vision"
-    confidence_threshold: 50
     disambiguates_against:
-      - capability: vision
-        hint: "build implements code after vision work; vision defines direction"
-    patterns_regex:
-      - "\\brefine\\s+the\\s+vision\\b"
+      - capability: plan
+        hint: "build implements an established task; plan structures work before implementation"

package/bundle/skills/agentera/capabilities/design/schemas/triggers.yaml

@@ -1,45 +1,16 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests design.
+    description: Define, maintain, or assess visual identity and a design system.
     priority: high
-    patterns:
-      - "design"
-      - "/design"
-    confidence_threshold: 60
-    borderline_band: 10
-    patterns_regex:
-      - "\\b/design\\b"
   2:
     id: T2
-    description: >-
-      Design system creation requests. Matches when the user wants to
-      create or set up a visual identity system or design tokens.
-    priority: medium
-    patterns:
-      - "create design system"
-      - "write DESIGN.md"
-      - "design tokens"
-      - "visual identity"
-      - "define the aesthetic"
-      - "set up design system"
-    confidence_threshold: 50
+    description: Create a visual identity, design system, design tokens, or aesthetic direction.
+    priority: high
   3:
     id: T3
-    description: >-
-      Design system refinement and audit requests. Matches when the user
-      wants to evolve, check, or update an existing design system.
-    priority: medium
-    patterns:
-      - "audit design"
-      - "refine design system"
-      - "update DESIGN.md"
-    confidence_threshold: 50
+    description: Refine, update, or audit a visual design system, including “audit the design system”.
+    priority: high
     disambiguates_against:
       - capability: audit
         hint: "design here is about visual identity, not codebase auditing"
-    patterns_regex:
-      - "\\baudit\\s+design\\b"
-      - "update\\s+DESIGN\\.md"

package/bundle/skills/agentera/capabilities/discuss/schemas/triggers.yaml

@@ -1,54 +1,20 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests discuss for structured deliberation.
+    description: Structured deliberation about a choice, decision, or tradeoff.
     priority: high
-    patterns:
-      - "discuss"
-      - "/discuss"
-    confidence_threshold: 60
-    borderline_band: 10
   2:
     id: T2
-    description: >-
-      Decision-oriented requests. Matches when the user wants help thinking
-      through a decision or evaluating tradeoffs.
-    priority: medium
-    patterns:
-      - "deliberate"
-      - "help me think through"
-      - "help me decide"
-      - "think this through with me"
-      - "let's deliberate"
-      - "what are the tradeoffs"
-      - "brainstorm"
-      - "rubber duck"
-    confidence_threshold: 50
+    description: Help decide, think through alternatives, or evaluate tradeoffs.
+    priority: high
   3:
     id: T3
-    description: >-
-      Option-comparison signals. Matches when the user is torn between
-      choices or wants to evaluate competing approaches.
-    priority: medium
-    patterns:
-      - "should I"
-      - "I'm torn between"
-      - "what's the right approach"
-      - "let's reason about"
-    confidence_threshold: 50
+    description: Compare competing options before committing to an approach.
+    priority: high
   4:
     id: T4
-    description: >-
-      Pre-build scoping signals. Matches when the user wants to scope or
-      reason about work before starting implementation.
+    description: Explore uncertain scope or approach before committing to implementation.
     priority: medium
-    patterns:
-      - "scope this out"
-      - "before I build this"
-      - "talk me through"
-    confidence_threshold: 50
     disambiguates_against:
       - capability: plan
         hint: "discuss explores options before committing; plan structures committed work"

package/bundle/skills/agentera/capabilities/document/schemas/triggers.yaml

@@ -1,45 +1,16 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests document.
+    description: Create, maintain, or assess project documentation.
     priority: high
-    patterns:
-      - "document"
-      - "/document"
-    confidence_threshold: 60
-    borderline_band: 10
-    patterns_regex:
-      - "\\b/document\\b"
   2:
     id: T2
-    description: >-
-      Documentation creation requests. Matches when the user wants to
-      write or create documentation, including DTC-first workflows.
-    priority: medium
-    patterns:
-      - "write docs"
-      - "document this"
-      - "create README"
-      - "write AGENTS.md"
-      - "docs first"
-      - "document before building"
-    confidence_threshold: 50
+    description: Write or create project documentation, including README and agent guidance.
+    priority: high
   3:
     id: T3
-    description: >-
-      Documentation maintenance and audit requests. Matches when the user
-      wants to update, check, or verify existing documentation.
-    priority: medium
-    patterns:
-      - "update the docs"
-      - "audit docs"
-      - "check documentation"
-      - "docs out of sync"
-    confidence_threshold: 50
+    description: Update, verify, or audit documentation, including “audit the docs”.
+    priority: high
     disambiguates_against:
       - capability: audit
         hint: "document maintains project docs; audit reviews codebase health"
-    patterns_regex:
-      - "\\baudit\\s+docs?\\b"

package/bundle/skills/agentera/capabilities/optimize/schemas/triggers.yaml

@@ -1,47 +1,16 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests optimize.
+    description: Improve an existing system against a measurable target.
     priority: high
-    patterns:
-      - "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: >-
-      Metric-driven optimization requests. Matches when the user wants to
-      improve a concrete, quantifiable property of their codebase.
-    priority: medium
-    patterns:
-      - "optimize"
-      - "improve performance"
-      - "reduce latency"
-      - "increase test coverage"
-      - "lower bundle size"
-      - "speed up"
-      - "make faster"
-      - "make smaller"
-      - "get the score up"
-      - "hit the target"
-      - "improve the metric"
-    confidence_threshold: 50
-    borderline_band: 20
+    description: Improve a concrete metric such as startup time, latency, coverage, or size.
+    priority: high
   3:
     id: T3
-    description: >-
-      Iterative experimentation requests. Matches when the user wants to
-      run experiments, benchmark, or iterate on a measurable objective.
+    description: Benchmark, experiment, or iterate toward a measurable objective.
     priority: medium
-    patterns:
-      - "benchmark and iterate"
-      - "run experiments"
-      - "tune"
-      - "experiment until"
-    confidence_threshold: 50

package/bundle/skills/agentera/capabilities/orchestrate/schemas/artifacts.yaml

@@ -6,8 +6,9 @@ ARTIFACTS:
     description: >-
       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. Failed evaluator results are recorded through the
+       artifact access, then updates status (pending -> complete/blocked) only
+       when resolving a task. Superseded tasks are terminal dependency
+       satisfiers and stay out of ready and blocked queues. Failed evaluator results are recorded through the
       retry-safe typed `record-evaluation` mutation before retry or blocking.
   2:
     id: A2

package/bundle/skills/agentera/capabilities/orchestrate/schemas/exit.yaml

@@ -3,7 +3,7 @@ EXIT_CONDITIONS:
     id: E1
     condition: complete
     description: >-
-      All plan tasks are complete, the health check passed, and the
+      All plan tasks are complete or validly superseded, the health check passed, and the
       orchestration session concluded with all planned work finished.
     exit_signal: complete
   2:

package/bundle/skills/agentera/capabilities/orchestrate/schemas/triggers.yaml

@@ -1,55 +1,23 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests orchestrate.
+    description: Execute an entire plan or coordinate multiple tasks and capabilities.
     priority: high
-    patterns:
-      - "orchestrate"
-      - "/orchestrate"
-    confidence_threshold: 60
-    borderline_band: 10
-    patterns_regex:
-      - "\\b/orchestrate\\b"
   2:
     id: T2
-    description: >-
-      Multi-cycle execution signals. Matches when the user wants to execute
-      an entire plan autonomously or run tasks through evaluation gating.
-    priority: medium
-    patterns:
-      - "run the plan"
-      - "execute the plan"
-      - "run all tasks"
-      - "keep going until done"
-      - "run through the plan"
-      - "build everything"
-    confidence_threshold: 55
+    description: Run every task in a plan or execute a full plan autonomously.
+    priority: high
     disambiguates_against:
       - capability: build
         hint: "orchestrate runs the whole plan autonomously; build executes one development cycle"
   3:
     id: T3
-    description: >-
-      Orchestration and delegation signals. Matches when the user wants to
-      chain multiple capabilities, delegate work, or coordinate multi-step
-      execution.
+    description: Coordinate multiple tasks or capability handoffs through completion.
     priority: medium
-    patterns:
-      - "orchestrate"
-      - "orchestrate skills"
-      - "multi-cycle"
-    confidence_threshold: 50
   4:
     id: T4
-    description: >-
-      Autonomous plan execution signals. Matches when the user wants
-      evaluated, plan-driven development without manual intervention.
+    description: Run evaluated, plan-driven development across multiple tasks without manual sequencing.
     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/plan/schemas/triggers.yaml

@@ -1,46 +1,23 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests plan for structured planning.
+    description: Requests to structure work into a plan before implementation.
     priority: high
-    patterns:
-      - "plan"
-      - "/plan"
-    confidence_threshold: 60
-    borderline_band: 10
-    patterns_regex:
-      - "\\b/plan\\b"
   2:
     id: T2
-    description: >-
-      Planning requests. Matches when the user wants to create a plan,
-      break work down, or specify requirements before building.
-    priority: medium
-    patterns:
-      - "plan this"
-      - "write a plan"
-      - "break this down"
-      - "decompose this"
-      - "spec this out"
-      - "plan before building"
-    confidence_threshold: 50
+    description: Create a plan, break work down, or specify requirements before building.
+    priority: high
     disambiguates_against:
       - capability: build
         hint: "plan structures work into tasks before coding; build implements the work"
+      - capability: discuss
+        hint: "plan structures committed work; discuss explores an undecided choice or tradeoff"
+      - capability: vision
+        hint: "plan structures work toward known direction; vision defines the direction itself"
   3:
     id: T3
-    description: >-
-      Architectural planning signals. Matches when the user is asking how
-      to approach building something or when the work is too large for a
-      single development cycle.
+    description: Plan a multi-step feature or approach too large for one development cycle.
     priority: medium
-    patterns:
-      - "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"

package/bundle/skills/agentera/capabilities/profile/schemas/triggers.yaml

@@ -1,49 +1,20 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests profile.
+    description: Create, maintain, or analyze a reusable decision profile.
     priority: high
-    patterns:
-      - "profile"
-      - "/profile"
-    confidence_threshold: 55
   2:
     id: T2
-    description: >-
-      Profile generation requests. Matches when the user wants to build
-      or regenerate their decision profile from scratch.
-    priority: medium
-    patterns:
-      - "build decision profile"
-      - "generate decision profile"
-      - "rebuild my profile"
-      - "regenerate profile"
-    confidence_threshold: 45
+    description: Build, generate, or regenerate a decision profile.
+    priority: high
+    disambiguates_against:
+      - capability: build
+        hint: "profile builds a reusable decision profile; build implements a software task"
   3:
     id: T3
-    description: >-
-      Profile maintenance requests. Matches when the user wants to update,
-      validate, or check their existing profile.
+    description: Update, validate, or refresh an existing decision profile.
     priority: medium
-    patterns:
-      - "update my profile"
-      - "refresh my decision profile"
-      - "validate my profile"
-      - "check my profile"
-      - "quick profile check"
-    confidence_threshold: 45
   4:
     id: T4
-    description: >-
-      Decision analysis requests. Matches when the user wants to understand
-      their own decision-making patterns or review past decisions.
+    description: Analyze personal decision patterns or review decision history.
     priority: medium
-    patterns:
-      - "what would I decide"
-      - "analyze my decisions"
-      - "mine my sessions"
-      - "decision patterns"
-      - "review my decision history"
-    confidence_threshold: 45

package/bundle/skills/agentera/capabilities/research/schemas/triggers.yaml

@@ -1,40 +1,16 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests research.
+    description: Research requests that analyze external sources, repositories, or approaches.
     priority: high
-    patterns:
-      - "research"
-      - "/research"
-    confidence_threshold: 55
   2:
     id: T2
-    description: >-
-      Applicability assessment requests. Matches when the user provides
-      an external URL and asks how it applies to their project or whether
-      they should adopt it.
-    priority: medium
-    patterns:
-      - "could I use this in"
-      - "how does this apply to my project"
-      - "is this relevant to"
-      - "what can I take from this"
-      - "should I adopt"
-    confidence_threshold: 45
+    description: Assess an external source's relevance, applicability, or adoption.
+    priority: high
   3:
     id: T3
-    description: >-
-      External resource review requests. Matches when the user wants
-      analysis of a library, repo, or approach for ideas and patterns.
-    priority: medium
-    patterns:
-      - "what do you think of this library"
-      - "review this repo for ideas"
-      - "anything worth stealing from"
-      - "how does this compare to what I'm doing"
-    confidence_threshold: 45
+    description: Review an external library, repository, or pattern for ideas.
+    priority: high
     disambiguates_against:
       - capability: audit
         hint: "research reviews external resources for ideas; audit reviews the local codebase for health"

package/bundle/skills/agentera/capabilities/status/schemas/triggers.yaml

@@ -1,62 +1,22 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests status.
+    description: Explicit status requests and orientation for the current project.
     priority: high
-    patterns:
-      - "status"
-      - "/status"
-    confidence_threshold: 60
-    borderline_band: 10
   2:
     id: T2
-    description: >-
-      Session-start signals. Matches explicit session-start or returning-to-project
-      requests from a user resuming work.
-    priority: medium
-    patterns:
-      - "start"
-      - "begin"
-      - "getting started"
-      - "onboard me"
-    confidence_threshold: 40
+    description: Session-start requests seeking orientation before choosing work.
+    priority: high
   3:
     id: T3
-    description: >-
-      Status and orientation requests. Matches when the user wants to know
-      the current state of the project or get a briefing.
+    description: Current project state, briefing, attention, or progress requests.
     priority: medium
-    patterns:
-      - "status"
-      - "dashboard"
-      - "pulse"
-      - "brief"
-      - "brief me"
-      - "update me"
-      - "what needs attention"
-    confidence_threshold: 45
   4:
     id: T4
-    description: >-
-      Returning-to-project signals. Matches when the user resumes work
-      on a known project and wants to pick up where they left off.
-    priority: medium
-    patterns:
-      - "where were we"
-      - "catch me up"
-      - "what should I work on"
-      - "what's next"
-    confidence_threshold: 45
+    description: Resume-work and “what's next?” requests with no separate requested outcome.
+    priority: high
   5:
     id: T5
-    description: >-
-      Fallback. Status is the default capability when no other capability's
-      trigger patterns match. This entry documents the fallback behavior
-      defined in the routing layer routing logic.
-    patterns:
-      - "*"
+    description: Fallback orientation when no capability fits the request.
     fallback: true
     priority: low
-    confidence_threshold: 0