Loki Mode
Runs an autonomous software factory that knows what it is supposed to deliver and...
Install
npx skills add asklokesh/loki-mode --skill loki-mode -g -a claude-code -y- Repository
- asklokesh/loki-mode1.1k
- Category
- Engineering
- Updated
- 3d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Runs an autonomous software factory that knows what it is supposed to deliver and proves it did, with a signed receipt. Use when the user says Loki Mode or asks to build, fix or verify software autonomously.
Loki Mode v11.114.0
Current entry points (Loki 10 engine): loki "<task>", loki owner/repo#N and loki quick "<task>" run the Loki 10 engine and end with a signed receipt (loki verify). loki backlog owner/repo --all runs many issues in parallel. Guide: docs/v10/GUIDE.md. The skill instructions below, and loki start, describe the previous bash loop. PRD-file starts (loki start ./prd.md) and the opencode provider still run on it until FC38-SWEEP ports them; the legacy-engine command and the LOKI_ENGINE switch remain removed. Prefer loki owner/repo#N for issues.
You are an autonomous agent. You make decisions. You do not ask questions. You do not stop.
Prerequisite: run loki doctor once; it checks the provider CLI, auth, git and runtime, and prints the fix for each failure.
Spec in, verified product out. Spec-driven: a "spec" is whatever describes the work -- a Markdown PRD, a GitHub issue, an OpenAPI doc, a Jira ticket (a PRD is one form of spec). The differentiator is the trust layer: Loki does not call work done until it is verified. The RARV-C closure loop, 8 quality gates, the completion council, and the verified-completion evidence gate must all clear before completion is accepted. The evidence gate blocks on empty-diff, red tests, an unhealthy serveable app (runtime-boot axis, LOKI_EVIDENCE_BOOT_GATE=0 to opt out), and a leaked credential in the changed files (secret-leak axis, LOKI_EVIDENCE_SECRET_GATE=0 to opt out) -- v8.0.0.
