jixoai

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Archive multiple completed changes at once. Use when archiving several parallel changes.

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

Repo-specific development workflow for agenter. Use when implementing, reviewing, or archiving changes in this repository, especially for OpenSpec work, release tooling, Studio UI, Storybook DOM tests, viewport/browser walkthroughs, worktree discipline, or repo-level docs/spec updates.

Orient yourself inside the runtime shell. Use this first when you need to choose between root tools, shell CLI, and deeper skill docs.

Create or update Agenter app packages, including first-party repo apps under apps/* and community agenter-app-* packages with peerDependencies.agenter compatibility.

Record, query, and maintain avatar-private raw notes through NoteSystem. Use when durable activity evidence, user corrections, terminal habits, ShellAssistant continuity, references, tags, or rename-safe note facts should be captured without turning them into distilled memory.

Inspect mounted real paths and choose the correct absolute cwd. Use this when path authority is unclear.

Create and drive durable terminal sessions. Use this when work needs a long-lived or interactive process; killed-terminal recovery is an explicit forensic path.

Install, enable, query, call, and recover MCP servers through the root runtime CLI. Use this when a task mentions MCP servers, MCP tools, stdio, Streamable HTTP, SSE, or project MCP availability.

Coordinate in shared rooms without breaking role boundaries or repeating already-claimed ownership. Use this when multiple users or avatars share one room.