@redv/owner
v0.1.1
Published
Resumable Loop and Pipeline vibe coding for Claude Code and Codex
Maintainers
Readme
Owner
Owner is a resumable vibe-coding workflow for Claude Code and Codex. It turns an AI coding request into a persisted, guarded lifecycle with requirement shaping, implementation, evidence-backed verification, bounded repair, recovery, and archive.
Owner provides two independent workflows:
- Loop:
Shape → Build ↔ Verify → Archive. A self-contained runtime for strong autonomous models. It does not depend on OpenSpec or Superpowers. - Pipeline:
Open → Design → Build → Verify → Archive. OpenSpec owns WHAT, Superpowers owns design/TDD/debug/review methods, and Owner owns orchestration, guards, recovery, and archive.
Supported hosts:
Owner is distributed under the MIT License. See LICENSE.
Requirements
- Node.js 22+
- npm or pnpm
- Git
- Claude Code or Codex
- Network access for Pipeline dependencies (OpenSpec and Superpowers)
Install from npm
npm install @redv/owner
npx owner --versionYou can also clone the TAN-cyber repository and build locally:
git clone https://github.com/TAN-cyber/owner.git
cd owner
corepack enable
pnpm install
pnpm build
npm linkInstalling the CLI does not modify a host configuration. Owner writes Skills, Rules, and Hooks only after the user explicitly runs npx owner init.
Initialize
Codex with both workflows:
npx owner init /path/to/project \
--scope project \
--platform codex \
--workflow bothClaude Code with Loop:
npx owner init /path/to/project \
--scope project \
--platform claude \
--workflow loopGlobal installation is explicit:
npx owner init --scope global --platform codex --workflow both
npx owner init --scope global --platform claude --workflow both--platform accepts only claude or codex.
Host paths
| Host | Project Skills | User Skills | Rules/Hooks |
|---|---|---|---|
| Claude Code | .claude/skills/ | ~/.claude/skills/ | .claude/rules/, .claude/settings.local.json |
| Codex | .agents/skills/ | ~/.agents/skills/ | .codex/rules/, .codex/hooks.json |
Codex paths follow the official Skills documentation.
Use
Claude Code:
/owner implement order cancellation with idempotent refundsCodex:
$owner implement order cancellation with idempotent refundsThe unified entry runs:
npx owner workflow resolve . --activate --jsonIt loads exactly one of owner-loop or owner-pipeline from .owner/config.yaml. It never switches workflows based on task size or model judgment.
Core commands
npx owner status [project] --json
npx owner resume-probe [project] --utterance "continue yesterday's task" --json
npx owner doctor [project] --json
npx owner loop new <change> --json
npx owner loop status [change] --details --json
npx owner loop next <change> [required inputs] --json
npx owner loop archive <change> --preview --json
npx owner state init <change> full --isolation current
npx owner state next <change>
npx owner guard <change> <phase> --apply
npx owner handoff <change> design --write
npx owner archive <change> --dry-runLoop portable artifacts live under docs/owner/; local locks, logs, receipts, and transactions live under .owner/runtime/loop/. Pipeline state lives in docs/openspec/changes/<change>/.owner.yaml by default.
Contributing
Development, verification, and release instructions are maintained in CONTRIBUTING.md.
Boundaries
- A fresh Verifier reduces self-confirmation bias but is not a correctness proof.
- Owner cannot verify a requirement that was never captured in acceptance/specs.
- Unsynced code cannot be recovered from portable state alone.
- A passing Verify result does not authorize push, PR, or merge.
- Pipeline installs third-party OpenSpec and Superpowers packages.
License
MIT. See LICENSE.
