# Praxist Takeover

Orchestrate first-use Praxist onboarding, current task initialization, validation, and...

- Repository: https://github.com/sapientinc/PRAXIST (5536 stars)
- Category: AI and agents
- License: see repository
- Last updated: 2026-09-23
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add sapientinc/PRAXIST --skill praxist-takeover -g -a claude-code -y`
Codex: `npx skills add sapientinc/PRAXIST --skill praxist-takeover -g -a codex -y`
Cursor: `npx skills add sapientinc/PRAXIST --skill praxist-takeover -g -a cursor -y`
Gemini CLI: `npx skills add sapientinc/PRAXIST --skill praxist-takeover -g -a gemini-cli -y`

## Description

Orchestrate first-use Praxist onboarding, current task initialization, validation, and detached run launch from a supported agent interface. Use when a user wants a one-command or one-conversation path from an existing runnable research project to a started Praxist run, asks to onboard plus initialize plus start, asks for repo-to-task-to-run setup, or wants the agent to prepare and launch Praxist with minimal interaction. This skill composes onboarding, full task initialization or task-harness repair, runtime checks, control start, and confirmation gates without changing Praxist core.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Praxist Takeover

Use this skill to move a user from an existing runnable research project to a
detached Praxist run in one guided flow. It composes existing skills rather
than duplicating their detailed procedures:

- `praxist-onboarding` for Praxist context and local readiness scan.
- `praxist-task-initialization` or
  `praxist-interactive-task-init` for task-project creation.
- `praxist-control` for task validation and detached launch.

The operator-facing `praxist --takeover` command is only a first-project
handoff into this skill. It does not replace, abbreviate, or independently
implement any step below. Treat its selected absolute project path and final
Enter confirmation as explicit operator context.

The first operational action must be the complete `praxist-onboarding`
workflow. Do not replace onboarding with a shorter local checklist, and do not
proceed to task initialization or launch until onboarding has produced its
readiness summary. This applies even when Codex already appears familiar with
Praxist from prior context.

When no launch-ready task exists, the next action must be the **complete current
`praxist-task-initialization` workflow**. `praxist-takeover` must invoke and
follow that skill rather than recreating a shortened initializer from this file. Load
and read the installed skill's current `SKILL.md` at execution time; do not rely
on a remembered or summarized task-init procedure. Wait for task-init's
evaluator, lane-routing regression, resource plan, and required validations to
finish before continuing. A user who invokes only `praxist-takeover` must
receive the same harness contract as a direct task-init user.

## Hard Preconditions

Print this before doing work:

The rest: https://github.com/sapientinc/PRAXIST/blob/HEAD/skills/praxist-takeover/SKILL.md