{
  "skills": [
    {
      "slug": "alissa-code-loopwork-wow",
      "title": "Loopwork Way of Work — operating the coding loop",
      "description": "The coding loop's operating manual: feed work (issue-ready task -> commit -> autodev BOW -> the daemons take over), the seat map (orcloop/devloop/revloop), authoring rules, consoles, escalations, and every operator lever. Sibling: alissa-code-loopwork-principles holds the theory (CLS, doctrines, catalog).",
      "tags": [
        "alissa",
        "loopwork",
        "wow",
        "way-of-work",
        "autonomous",
        "daemons",
        "operations",
        "cls"
      ],
      "triggers": [
        "loopwork wow",
        "way of work",
        "feed work",
        "autodev",
        "autodev bow",
        "autonomous dev",
        "register task for autonomous",
        "alissa:develop",
        "alissa:maintain",
        "orcloop",
        "devloop",
        "revloop",
        "stuck lane"
      ],
      "createdAt": "2026-07-27",
      "lastUpdated": "2026-07-27",
      "url": "alissa-code-loopwork-wow/index.json"
    },
    {
      "slug": "alissa-code-loopwork-principles",
      "title": "Loopwork Principles — Convergent Loop Systems (CLS)",
      "description": "The abstract CLS method: opposing loops with different initial conditions and incentives iterate until the opposition cancels — what survives is the artifact. Concepts, the doctrine registry (L1-L15), the loop catalog whose schema doubles as the new-loop design checklist, and the design-a-new-loop procedure. Instance-agnostic; concrete loops (first: the coding loop) get their own instance skills. Sibling: alissa-code-loopwork-wow is the coding loop's operating manual.",
      "tags": [
        "alissa",
        "autonomous",
        "cls",
        "convergence",
        "daemons",
        "loopwork",
        "method",
        "principles"
      ],
      "triggers": [
        "loopwork",
        "cls",
        "convergent loop",
        "convergence",
        "loop catalog",
        "design a loop",
        "doctrine"
      ],
      "createdAt": "2026-07-24",
      "lastUpdated": "2026-07-27",
      "url": "alissa-code-loopwork-principles/index.json"
    },
    {
      "slug": "alissa-code-review",
      "title": "Alissa Code Review",
      "description": "The fresh-instance PR review protocol for Alissa tasks and the adversarial review loop that drives it to convergence (conventions CR1–CR9): reviews trigger at the draft→ready flip, run in a brand-new context-isolated session, follow a five-dimension rubric (correctness, coding practices, security, performance, side-effects), post severity-tagged PR comments, and record a structured verdict as evidence on a downstream review task; the implementer triages every finding on its thread ([triage:pursue]/[triage:ignore]/[triage:later]/[triage:answer], reasoning mandatory) and re-enters with a fresh reviewer each round until approve — capped (default 3 rounds), cap-out escalates to the operator. Reviewer posture: read and comment only — never push, merge, or fix.",
      "tags": [
        "alissa",
        "alissa-code",
        "code-review",
        "pull-request",
        "conventions",
        "security",
        "performance",
        "quality",
        "workflow",
        "review-loop",
        "triage",
        "adversarial"
      ],
      "triggers": [
        "review a PR",
        "PR ready for review",
        "fresh instance review",
        "spawn a reviewer session",
        "review task",
        "review verdict",
        "severity tags blocker major minor nit",
        "request changes on a PR",
        "review rubric",
        "who reviews alissa task PRs",
        "review loop",
        "adversarial review loop",
        "run the review loop",
        "use the review loop",
        "loop until approval",
        "review until convergence",
        "triage review findings",
        "triage:pursue triage:ignore triage:later",
        "re-review round",
        "alissa-pr-review",
        "close the review loop",
        "review round cap",
        "max review rounds"
      ],
      "createdAt": "2026-07-14",
      "lastUpdated": "2026-07-20",
      "url": "alissa-code-review/index.json"
    },
    {
      "slug": "alissa-code-git",
      "title": "Alissa Code Git Conventions",
      "description": "The canonical git and PR conventions for coding sessions working Alissa tasks, independent of repo layout or launcher: commit attribution (the alissa-app <support@alissa.app> co-author trailer), TASK-branch naming, draft-first PR discipline, the PR↔task cross-link contract (PR URL attached to the task as evidence on creation, merge recorded on the task), truthful task status, and how a task's Definition of Done and validation criteria must word the PR bar — ready-for-review with verification stated, never \"draft PR opened\" as a terminal state.",
      "tags": [
        "alissa",
        "alissa-code",
        "git",
        "pull-request",
        "conventions",
        "co-author",
        "evidence",
        "workflow",
        "definition-of-done",
        "validation-criteria"
      ],
      "triggers": [
        "co-authored-by alissa",
        "alissa co-author trailer",
        "commit attribution",
        "TASK branch naming",
        "draft PR convention",
        "link a PR to a task",
        "attach PR url to task",
        "PR evidence",
        "record a merge on a task",
        "git conventions for alissa tasks",
        "definition of done wording for a PR",
        "validation criteria for a PR",
        "ready for review criterion",
        "writing task criteria that ship code"
      ],
      "createdAt": "2026-07-12",
      "lastUpdated": "2026-07-20",
      "url": "alissa-code-git/index.json"
    },
    {
      "slug": "alissa-code-orchestration",
      "title": "Alissa Code Orchestration",
      "description": "When and how a coding agent should act as an orchestrator that spins up managed Alissa tmux sessions (ali-*) and registers work in their queues, instead of (or alongside) its native sub-agent mechanism. Covers the durability/coupling decision rubric (native sub-agents first; escalate under documented conditions), a taxonomy of named orchestration patterns (fire-and-forget delegate, fleet fan-out/reconvene, queue-as-pipeline, cross-machine provisioning, service session, human-handoff prep), per-pattern recipes with failure modes and verification, cross-cutting conventions (task-as-truth writeback, naming, depth limits, queue hygiene), the security posture that queued text becomes keystrokes on a real terminal, and the outage-recovery runbook for reviving a crashed fleet after a tmux-server or desktop outage.",
      "tags": [
        "alissa",
        "orchestration",
        "tmux",
        "worker",
        "agents",
        "delegation",
        "fleet",
        "queue",
        "workflow",
        "recovery"
      ],
      "triggers": [
        "orchestrate agents",
        "spin up an agent session",
        "alissa tmux orchestration",
        "delegate to an agent session",
        "fan out agents",
        "agent fleet",
        "sub-agent vs tmux session",
        "queue as pipeline",
        "cross-machine agent",
        "run an agent on another machine",
        "unattended agent fleet",
        "orchestrator agent",
        "delegate a task to claude session",
        "when to use a managed tmux session",
        "recover from an outage",
        "revive crashed sessions",
        "tmux server crash",
        "sessions gone after reboot",
        "fleet recovery"
      ],
      "createdAt": "2026-07-12",
      "lastUpdated": "2026-07-18",
      "url": "alissa-code-orchestration/index.json"
    },
    {
      "slug": "alissa-code-workspace",
      "title": "Alissa Code Workspace",
      "description": "How to work inside an Alissa Code Workspace — a multi-repo layout of git worktree hubs: the mental model, the task/branch/worktree recipes, the rules of engagement (R1–R14), anti-patterns & recovery, the workspace binding contract (alissa-workspace.yaml, ALISSA_WORKSPACE_ROOT), and the canonical scaffolding templates consumed by the alissa code workspace CLI.",
      "tags": [
        "alissa",
        "workspace",
        "alissa-code",
        "git",
        "worktree",
        "multi-repo",
        "workflow",
        "templates",
        "scaffolding"
      ],
      "triggers": [
        "alissa workspace",
        "alissa code workspace",
        "ALISSA_WORKSPACE_ROOT",
        "alissa-workspace.yaml",
        "worktree hub",
        "git worktree add",
        "start a task branch",
        "how do I start a task in this workspace",
        "resume a branch worktree",
        "hub-ify a repo",
        "bare clone .source",
        "gitdir pointer file",
        "workspace rules",
        "draft PR workflow",
        "fatal: this operation must be run in a work tree"
      ],
      "createdAt": "2026-07-11",
      "lastUpdated": "2026-07-14",
      "url": "alissa-code-workspace/index.json"
    },
    {
      "slug": "alissa-code",
      "title": "alissa code — Agent Launcher",
      "description": "Understand and operate `alissa code`, the CLI launcher that runs a coding agent (default Claude Code) with Alissa context pre-checked, then hands off — token precheck, required-skills install, code-session lifecycle, ALISSA_SESSION_ID propagation, and the X-Alissa-Session MCP config auto-wiring. Covers handoff targets, flags, and failure modes.",
      "tags": [
        "alissa",
        "cli",
        "alissa-code",
        "handoff",
        "session",
        "launcher",
        "mcp",
        "setup"
      ],
      "triggers": [
        "alissa code",
        "launch claude with alissa",
        "alissa handoff",
        "--handoff",
        "why did alissa code change my .mcp.json",
        "why did alissa modify ~/.claude.json",
        "required skills missing",
        "no-mcp-config",
        "agent launcher",
        "start a coding agent with alissa"
      ],
      "createdAt": "2026-06-18",
      "lastUpdated": "2026-07-14",
      "url": "alissa-code/index.json"
    },
    {
      "slug": "alissa-tools",
      "title": "Alissa Capability Tools",
      "description": "Use Alissa capability tools — helpers from Alissa's agent harness on the same `alissa_…` token: metered platform inference (analyze a YouTube video, speech-to-text, text-to-speech, create_raw_deck AI deck authoring) billed against credits, plus free tools (`get_user_credit_balance` and the validate_deck/get_deck_url/save_deck Alissa Slides tools). Covers the availability matrix across MCP, REST API, and CLI (and why STT/TTS aren't on MCP), the credit/billing model, checking your balance, and error handling like a 402 empty balance.",
      "tags": [
        "alissa",
        "tools",
        "capability",
        "credits",
        "billing",
        "youtube",
        "stt",
        "tts",
        "metered",
        "balance",
        "slides",
        "decks"
      ],
      "triggers": [
        "alissa tools",
        "capability tool",
        "analyze youtube",
        "analyze_youtube",
        "transcribe audio",
        "text to speech",
        "speech to text",
        "alissa tools youtube",
        "alissa credits",
        "check credit balance",
        "credit balance",
        "get_user_credit_balance",
        "insufficient credits",
        "402 credits",
        "which tools are available on mcp",
        "validate_deck",
        "get_deck_url",
        "save_deck",
        "create_raw_deck",
        "build a slide deck",
        "alissa tools slides"
      ],
      "createdAt": "2026-06-18",
      "lastUpdated": "2026-06-23",
      "url": "alissa-tools/index.json"
    },
    {
      "slug": "alissa-slides",
      "title": "Alissa Slides",
      "description": "Generate on-brand slide decks on slides.alissa.app two ways: the anonymous encode endpoint (POST /api/encode → a self-contained share link, no install) and the Alissa-token tools (validate_deck, get_deck_url, save_deck, create_raw_deck) on MCP/REST/CLI. Same v1 deck contract — the layouts, slots, and limits.",
      "tags": [
        "alissa",
        "slides",
        "presentations",
        "decks",
        "api",
        "endpoint",
        "tools",
        "deck-authoring"
      ],
      "triggers": [
        "create slides",
        "make a deck",
        "generate a presentation",
        "slides.alissa.app",
        "presentation link",
        "share a deck",
        "slide deck",
        "POST /api/encode",
        "encode slides",
        "mermaid slide",
        "code slide",
        "chart slide",
        "vega-lite chart",
        "analytics slide",
        "private deck passkey",
        "validate_deck",
        "get_deck_url",
        "save_deck",
        "create_raw_deck",
        "generate a deck with AI",
        "alissa tools slides"
      ],
      "createdAt": "2026-06-22",
      "lastUpdated": "2026-06-23",
      "url": "alissa-slides/index.json"
    },
    {
      "slug": "alissa-mcp",
      "title": "Alissa MCP Server",
      "description": "Connect an MCP client to the Alissa MCP server (mcp.alissa.app) and use its task tools — a Model Context Protocol layer over the Alissa REST API. Covers client configuration (Claude Desktop, Claude Code, Cursor), authentication, the tool surface, read-only and local stdio modes, and troubleshooting.",
      "tags": [
        "alissa",
        "mcp",
        "model-context-protocol",
        "tools",
        "integration",
        "assistant"
      ],
      "triggers": [
        "alissa mcp",
        "mcp.alissa.app",
        "connect alissa to claude",
        "alissa mcp server",
        "add alissa mcp",
        "claude desktop alissa",
        "mcp client config",
        "alissa tools"
      ],
      "createdAt": "2026-06-16",
      "lastUpdated": "2026-06-23",
      "url": "alissa-mcp/index.json"
    },
    {
      "slug": "alissa-api",
      "title": "Alissa REST API",
      "description": "Operate the Alissa REST API at api.alissa.app — read and update tasks, drive status through the transition matrix, attach deliverables, satisfy validation criteria, comment, create tasks, link dependencies, create downstream tasks, and accept or decline incoming requests.",
      "tags": [
        "alissa",
        "api",
        "rest",
        "tasks",
        "automation",
        "integration"
      ],
      "triggers": [
        "alissa api",
        "api.alissa.app",
        "alissa rest",
        "alissa token",
        "update a task",
        "change task status",
        "attach deliverable",
        "accept request",
        "decline request",
        "filter tasks",
        "prioritize tasks",
        "task priorities",
        "list projects",
        "bodies of work",
        "alissa task automation"
      ],
      "createdAt": "2026-06-16",
      "lastUpdated": "2026-06-23",
      "url": "alissa-api/index.json"
    },
    {
      "slug": "alissa-session",
      "title": "Alissa Sessions",
      "description": "Work inside a running `alissa code` session — its three server-side coordination surfaces: session memory (a per-session key/value store plus the reserved current_task focus, for anchoring work, recalling it across tool calls, and surviving context compaction), session messages (a best-effort async operator↔agent thread, for reacting to the pending-message nudge, acknowledging operator messages, and posting status notes without blocking), and the Task Queue (a user-bound FIFO of committed tasks shared across the user's sessions, where take_next_task pops the head and sets it as this session's current_task focus). Transport-agnostic discipline over the MCP tools, REST API, and the `alissa session` CLI.",
      "tags": [
        "alissa",
        "session",
        "memory",
        "context",
        "kv",
        "current-task",
        "messages",
        "operator",
        "coordination",
        "resume",
        "compaction",
        "queue",
        "task-queue"
      ],
      "triggers": [
        "alissa session",
        "alissa code session",
        "session memory",
        "session context",
        "current_task",
        "what am I working on",
        "set context",
        "get context",
        "remember across compaction",
        "resume session",
        "focus task",
        "session message",
        "pending message",
        "operator message",
        "message from operator",
        "read_session_messages",
        "post_session_message",
        "leave a note for the user",
        "message the agent",
        "alissa session msg",
        "steer the agent",
        "interrupt the agent",
        "task queue",
        "what's next",
        "next task",
        "take next task",
        "queue a task",
        "enqueue_task",
        "take_next_task",
        "alissa queue"
      ],
      "createdAt": "2026-06-18",
      "lastUpdated": "2026-06-22",
      "url": "alissa-session/index.json"
    },
    {
      "slug": "alissa-chat",
      "title": "Consulting Alissa (Chat)",
      "description": "How an agent or script consults Alissa — the platform intelligence — over the chat surface (MCP `chat` tool, REST `POST /v1/chat`, or `alissa chat` CLI). Covers threading via conversationId, synchronous vs fire-and-forget replies, the credit cost (402 on empty balance), provenance, and the discipline of when to ask Alissa versus answer yourself, notify the human operator, or operate tasks directly.",
      "tags": [
        "alissa",
        "chat",
        "consult",
        "agent",
        "conversation",
        "credits",
        "mcp",
        "patterns"
      ],
      "triggers": [
        "ask alissa",
        "consult alissa",
        "alissa chat",
        "talk to alissa",
        "chat tool",
        "POST /v1/chat",
        "agent reach alissa",
        "alissa conversation",
        "continue conversation",
        "how to ask alissa"
      ],
      "createdAt": "2026-06-20",
      "lastUpdated": "2026-06-20",
      "url": "alissa-chat/index.json"
    },
    {
      "slug": "alissa-skills-usage",
      "title": "Alissa Skills Usage",
      "description": "The foundational skill for consuming skills.alissa.app: how to discover skills from the catalog, load a skill's manifest and layout, and traverse its artifacts (SKILL.md, procedures, references, scripts, assets) on demand over HTTP — plus how loading (ephemeral fetch into context) differs from installing a skill onto disk via the `alissa skill install` CLI.",
      "tags": [
        "alissa",
        "skills",
        "meta",
        "bootstrap",
        "foundational",
        "usage",
        "install"
      ],
      "triggers": [
        "skills.alissa.app",
        "alissa skill",
        "load a skill",
        "use a skill",
        "fetch a skill",
        "install a skill",
        "alissa skill install",
        "browse the skill catalog",
        "skill catalog",
        "skill index",
        "how do I use alissa skills"
      ],
      "createdAt": "2026-06-16",
      "lastUpdated": "2026-06-18",
      "url": "alissa-skills-usage/index.json"
    },
    {
      "slug": "alissa-skill-authoring",
      "title": "Authoring Alissa Skills",
      "description": "How to author an Alissa-compatible skill: the hard constraints inherited from the official Agent Skills spec plus Alissa's additions (meta.json, generated index.json, strict layout), and the house-style preferences (markdown everywhere, lean SKILL.md, how-tos in procedures, fetch-on-demand over duplication).",
      "tags": [
        "alissa",
        "skills",
        "meta",
        "authoring",
        "foundational",
        "spec"
      ],
      "triggers": [
        "create a skill",
        "author a skill",
        "write an alissa skill",
        "new skill",
        "scaffold a skill",
        "skill spec",
        "skill constraints",
        "skill conventions",
        "how do I make a skill"
      ],
      "createdAt": "2026-06-16",
      "lastUpdated": "2026-06-16",
      "url": "alissa-skill-authoring/index.json"
    },
    {
      "slug": "alissa-bok",
      "title": "Alissa Way of Work (BOK)",
      "description": "The foundational skill: reason and operate inside the Alissa epistemic stack — Observables, Theories of Change, Objectives, Projects, Processes — and produce valid, traceable artifacts under its accountability model.",
      "tags": [
        "alissa",
        "framework",
        "foundational",
        "meta",
        "bootstrap",
        "bok"
      ],
      "triggers": [
        "alissa",
        "bok",
        "way of work",
        "epistemic stack",
        "observable",
        "theory of change",
        "objective",
        "project",
        "process",
        "definition of done",
        "delegation",
        "accountability"
      ],
      "createdAt": "2026-06-16",
      "lastUpdated": "2026-06-16",
      "url": "alissa-bok/index.json"
    }
  ]
}