agentera 0.0.0 → 3.0.0-dev.0

package/bundle/skills/agentera/schemas/artifacts/todo.yaml

@@ -0,0 +1,110 @@
+# Todo Artifact Schema
+#
+# Open issues and tasks maintained by realisera and inspektera. Severity-ranked
+# checklist of work to be done, resolved items, and deferred work.
+#
+# Note: TODO.md is a human-facing Markdown artifact. It remains at the
+# project root and is not migrated to YAML. This schema exists for validation
+# and CLI discovery consistency.
+
+meta:
+  name: todo
+  version: "1.0.0"
+  description: >-
+    Open issues and tasks. Produced by capabilities that file work or findings.
+    Human-facing: remains Markdown at project root.
+  artifact_type: human_facing
+  path: "TODO.md"
+  producer:
+    [
+      dokumentera,
+      inspektera,
+      inspirera,
+      optimera,
+      orkestrera,
+      realisera,
+      resonera,
+      visualisera,
+    ]
+  consumers: [hej, all_skills]
+  format: markdown
+
+GROUP_PREFIXES:
+  BUDGET: TB
+  ITEM: TI
+  VALIDATION: TV
+  CONVENTION: TC
+
+BUDGET:
+  1:
+    id: TB1
+    token_budget: 5000
+    description: >-
+      Maximum tokens for TODO.md content. Exceeding triggers compaction.
+
+ITEM:
+  1:
+    id: TI1
+    field: severity
+    type: string
+    required: true
+    description: >-
+      Issue severity per protocol.yaml SEVERITY_ISSUE:
+      critical (⇶), degraded (⇉), normal (→), annoying (⇢).
+    validation:
+      - "Must be one of: critical, degraded, normal, annoying"
+  2:
+    id: TI2
+    field: description
+    type: string
+    required: true
+    description: >-
+      Brief description of the task or issue.
+  3:
+    id: TI3
+    field: status
+    type: string
+    required: true
+    description: >-
+      Current status: open or resolved.
+    validation:
+      - "Must be one of: open, resolved"
+
+CONVENTION:
+  1:
+    id: TC1
+    field: type_tag
+    level: advisory
+    description: >-
+      Each item should carry a type tag such as [fix], [feat], [chore],
+      [test], [perf], or [docs] for commit-scope alignment and scan
+      discoverability.
+  2:
+    id: TC2
+    field: version_suffix
+    level: advisory
+    description: >-
+      Feature and fix items should include a version scope like [fix:2.4.x]
+      or [feat:2.3.x] when the work targets a specific release train.
+  3:
+    id: TC3
+    field: title_format
+    level: advisory
+    description: >-
+      Items within the same severity section should use a consistent format:
+      either all plain prose or all "**BoldTitle**: description".
+  4:
+    id: TC4
+    field: resolved_summary
+    level: advisory
+    description: >-
+      Resolved items should end with "· resolved by ..." to distinguish
+      completed work from open or deferred items at a glance.
+  5:
+    id: TC5
+    field: resolved_strikethrough
+    level: advisory
+    description: >-
+      Resolved items should wrap the original task text in Markdown
+      strikethrough (~~text~~) before the resolution summary, keeping
+      the original intent readable while visually marking it closed.

package/bundle/skills/agentera/schemas/artifacts/vision.yaml

@@ -0,0 +1,262 @@
+# Vision Artifact Schema
+#
+# Project vision document. Captures the north star, target personas, design
+# principles, strategic direction, identity (personality, voice, emotional
+# register, naming), and the core tension the project navigates.
+#
+# Structural pattern: UPPER_CASE groups with numbered entries and stable IDs,
+# following capability_schema_contract.yaml and protocol.yaml conventions.
+#
+# ── Field-by-field mapping: v1 VISION.md → v2 vision.yaml ──
+#
+# v1 Field                              v2 Field               v2 ID
+# ─────────────────────────────────────────────────────────────────────
+# # <project name>                       HEADER.project_name    VN1
+# ## North Star                          NORTH_STAR.content     VN2
+# ## Who It's For / ### persona name     PERSONA.entry          VN3
+# (persona heading)                      PERSONA.name           VN4
+# (persona prose)                        PERSONA.description    VN5
+# ## Principles / - principle            PRINCIPLE.entry        VN6
+# (bold name + description)              PRINCIPLE.name         VN7
+# (principle prose)                      PRINCIPLE.description  VN8
+# ## Direction                           DIRECTION.content      VN9
+# ## Identity / ### Personality          IDENTITY.personality   VN10
+# ## Identity / ### Voice                IDENTITY.voice         VN11
+# ## Identity / ### Emotional register   IDENTITY.emotional_register VN12
+# ## Identity / ### Naming               IDENTITY.naming        VN13
+# ## The Tension                         TENSION.content        VN14
+#
+# Protocol references:
+#   No protocol primitives directly. Vision defines project-level identity
+#   that capabilities reference for voice and personality consistency.
+#   Skills never push to remote repos or modify VISION during execution cycles.
+
+meta:
+  name: vision
+  version: "1.0.0"
+  description: >-
+    Project vision. Produced by visionera and direction-shaping capabilities.
+    Consumed by capabilities that need strategic alignment. No compaction:
+    vision is not a growing artifact.
+  artifact_type: agent_facing
+  path: ".agentera/vision.yaml"
+  producer: [inspirera, realisera, resonera, visionera]
+  consumers: [dokumentera, hej, inspektera, orkestrera, planera, realisera, resonera, visionera, visualisera]
+  format: yaml
+
+GROUP_PREFIXES:
+  BUDGET: VB
+  HEADER: VH
+  NORTH_STAR: VN_NS
+  PERSONA: VN_PE
+  PRINCIPLE: VN_PR
+  DIRECTION: VN_DIR
+  IDENTITY: VN_ID
+  TENSION: VN_TN
+  VALIDATION: VVL
+
+BUDGET:
+  1:
+    id: VB1
+    scope: full_file
+    max_words: 1500
+    description: >-
+      Maximum words for the full file. Vision should be concise and
+      stable. Budgets are guidelines, not hard blockers.
+  2:
+    id: VB2
+    scope: compaction
+    rule: none
+    description: >-
+      No compaction. Vision is not a growing artifact. It is written
+      once (or refined infrequently) and never accumulates entries.
+
+HEADER:
+  1:
+    id: VH1
+    field: project_name
+    type: string
+    required: true
+    description: >-
+      Project name. Appears as the top-level heading. Must match the
+      project identity.
+    validation:
+      - "Non-empty string"
+
+NORTH_STAR:
+  1:
+    id: VN_NS1
+    field: content
+    type: string
+    required: true
+    description: >-
+      The project's north star. A concise statement of what the project
+      is, who it serves, and why it exists. Should be the single
+      paragraph that orients all decisions.
+    validation:
+      - "Non-empty string"
+
+PERSONA:
+  1:
+    id: VN_PE1
+    field: entry
+    type: map
+    required: true
+    description: >-
+      Each persona entry. At least one persona required. Personas
+      describe the target users in vivid narrative detail.
+    min_count: 1
+  2:
+    id: VN_PE2
+    field: name
+    parent: PERSONA.entry
+    type: string
+    required: true
+    description: >-
+      Persona name or archetype label (e.g., 'The solo founder who
+      knows better').
+    validation:
+      - "Non-empty string"
+  3:
+    id: VN_PE3
+    field: description
+    parent: PERSONA.entry
+    type: string
+    required: true
+    description: >-
+      Narrative description of the persona. Describes their context,
+      pain points, goals, and how the project serves them.
+    validation:
+      - "Non-empty string"
+
+PRINCIPLE:
+  1:
+    id: VN_PR1
+    field: entry
+    type: map
+    required: true
+    description: >-
+      Each design principle. At least one required. Principles guide
+      all design and implementation decisions.
+    min_count: 1
+  2:
+    id: VN_PR2
+    field: name
+    parent: PRINCIPLE.entry
+    type: string
+    required: true
+    description: >-
+      Short bold-name for the principle (e.g., 'One entry point,
+      deep capabilities').
+    validation:
+      - "Non-empty string"
+  3:
+    id: VN_PR3
+    field: description
+    parent: PRINCIPLE.entry
+    type: string
+    required: true
+    description: >-
+      Full principle text. Explains what the principle means, why it
+      matters, and how it guides decisions.
+    validation:
+      - "Non-empty string"
+
+DIRECTION:
+  1:
+    id: VN_DIR1
+    field: content
+    type: string
+    required: true
+    description: >-
+      Strategic direction. Where the project is heading, what the
+      adoption arc looks like, and what the next layer of evolution
+      entails.
+    validation:
+      - "Non-empty string"
+
+IDENTITY:
+  1:
+    id: VN_ID1
+    field: personality
+    type: string
+    required: true
+    description: >-
+      The project's personality. A vivid metaphor or description
+      that captures the feel of interacting with the product.
+    validation:
+      - "Non-empty string"
+  2:
+    id: VN_ID2
+    field: voice
+    type: string
+    required: true
+    description: >-
+      The project's voice and communication style. Describes tone,
+      register, and how capabilities communicate with users.
+    validation:
+      - "Non-empty string"
+  3:
+    id: VN_ID3
+    field: emotional_register
+    type: string
+    required: true
+    description: >-
+      How using the project should feel. The emotional experience
+      design that guides all user-facing output.
+    validation:
+      - "Non-empty string"
+  4:
+    id: VN_ID4
+    field: naming
+    type: string
+    required: true
+    description: >-
+      Naming conventions and rules. Describes the naming system,
+      its cultural roots, and the vocabulary of the work.
+    validation:
+      - "Non-empty string"
+
+TENSION:
+  1:
+    id: VN_TN1
+    field: content
+    type: string
+    required: true
+    description: >-
+      The core tension the project navigates. The fundamental
+      tradeoff or paradox that the design must resolve.
+    validation:
+      - "Non-empty string"
+
+VALIDATION:
+  1:
+    id: VVL1
+    rule: required_fields
+    severity: error
+    description: >-
+      The vision must have: project_name, north_star, at least one
+      persona, at least one principle, direction, and all identity
+      fields (personality, voice, emotional_register, naming), and
+      tension.
+    checks:
+      - "project_name is present and non-empty"
+      - "north_star.content is present and non-empty"
+      - "At least one persona entry exists"
+      - "Each persona has name and description"
+      - "At least one principle entry exists"
+      - "Each principle has name and description"
+      - "direction.content is present and non-empty"
+      - "identity.personality is present and non-empty"
+      - "identity.voice is present and non-empty"
+      - "identity.emotional_register is present and non-empty"
+      - "identity.naming is present and non-empty"
+      - "tension.content is present and non-empty"
+  2:
+    id: VVL2
+    rule: word_budget
+    severity: advisory
+    description: >-
+      Advisory check. Full file should be <=1500 words.
+    checks:
+      - "Total file word count <= 1500"

package/bundle/skills/hej/.claude-plugin/plugin.json

@@ -0,0 +1,6 @@
+{
+  "name": "hej",
+  "version": "2.0.3",
+  "description": "Legacy Agentera v1 explicit /hej bridge to the v2 /agentera upgrade flow; do not use for bare text hej.",
+  "author": { "name": "jgabor" }
+}

package/bundle/skills/hej/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: hej
+description: >
+  Legacy Agentera v1 explicit /hej bridge. Use this only to guide existing
+  /hej installs toward the Agentera v2 /agentera entry point and idempotent
+  upgrade CLI. Do not use this skill for bare text `hej`; route that through
+  the bundled agentera skill and the agentera hej dashboard path.
+version: "2.7.6"
+legacy_bridge: true
+---
+
+# hej legacy bridge
+
+This skill exists only for users who still have the Agentera v1 `/hej`
+entry point installed. Agentera v2 uses `/agentera` as the single active
+entry point. A bare text message exactly `hej` is not this legacy bridge; it
+belongs to the bundled `agentera` skill and its `agentera hej` dashboard path.
+
+Do not run the old HEJ orientation workflow from v1. Do not produce the v1
+dashboard. This bridge is an upgrade handoff.
+
+## When Loaded
+
+1. Explain briefly in plain language: `This is the old /hej entry point.
+   Agentera now starts from /agentera` (`$agentera` in Codex).
+2. Check the current project for v1 Markdown artifacts that do not yet have
+   v2 YAML counterparts:
+   - `.agentera/PROGRESS.md` without `.agentera/progress.yaml`
+   - `.agentera/PLAN.md` without `.agentera/plan.yaml`
+   - `.agentera/DECISIONS.md` without `.agentera/decisions.yaml`
+   - `.agentera/HEALTH.md` without `.agentera/health.yaml`
+   - `.agentera/DOCS.md` without `.agentera/docs.yaml`
+   - root `VISION.md` without `.agentera/vision.yaml`
+3. If any old project state is present, show the affected files and run or offer
+   this preview command. Say clearly that the preview changes nothing:
+
+   ```bash
+   npx -y agentera@latest doctor
+   ```
+
+4. Ask before applying changes. Explain the apply step plainly: it installs or
+   repairs Agentera's local app, updates managed runtime surfaces, and converts
+   old Agentera project notes to the new format with backups. It will not edit
+   shell startup files. After explicit confirmation, use:
+
+   ```bash
+   npx -y agentera@latest prime
+   ```
+
+   agentera ships as a self-contained npm package: running the latest version
+   uses the newest bundled app data directly. There is no separate local app
+   install to copy or repair.
+
+5. To refresh the version a runtime invokes, point its command at
+   `npx -y agentera@latest` (or a pinned `agentera@<version>`).
+
+6. End by telling the user to invoke `/agentera` (`$agentera` in Codex).
+
+## Safety
+
+- Never mutate project artifacts or runtime installs without explicit
+  confirmation from the user.
+- Never ask Agentera to edit shell startup files. Leftover 1.x managed marker
+  blocks reported by doctor are user-owned manual cleanup.
+  Upgrade does not scan shell startup files.
+- Prefer `npx -y agentera@latest` so the newest published self-contained package
+  is used without a separate install step.
+- From a local Agentera checkout, the equivalent is
+  `node packages/cli/dist/bin/agentera.js …` after `pnpm -C packages/cli build`.

package/bundle/skills/hej/agents/hej.toml

@@ -0,0 +1,11 @@
+name = "hej"
+description = "Legacy Agentera v1 explicit /hej bridge to the v2 /agentera upgrade flow; do not use for bare text hej."
+developer_instructions = """You are the Agentera legacy hej bridge.
+
+Read the bridge workflow at ${AGENTERA_HOME}/skills/hej/SKILL.md when available.
+Do not run the old v1 HEJ orientation workflow. Your job is to detect whether
+the project still has Agentera v1 artifacts, preview the v2 upgrade command,
+ask before applying changes, and route the user to /agentera after upgrade.
+Do not handle a bare text message exactly hej; that belongs to the bundled
+agentera skill and its agentera hej dashboard path.
+"""

package/bundle/skills/hej/agents/openai.yaml

@@ -0,0 +1,8 @@
+version: 1
+skill:
+  name: hej
+  display_name: Agentera v1 upgrade bridge
+  description: Legacy Agentera v1 explicit $hej bridge to the v2 $agentera upgrade flow; do not use for bare text hej.
+  invocation_hint: Use $hej only when explicitly requested for an old Agentera v1 install; bare text hej belongs to $agentera.
+  policy:
+    allow_implicit_invocation: false