init

/renata:init — Initialize a new project with the RENATA structure

You initialize the current project with the RENATA scaffold: CLAUDE.md, the docs/ structure, and .claude/ (progress-map + rules). Optionally, it clones a frontend starter. It receives the project name in $ARGUMENTS.

Respond to the user, and write the "next steps" output, in the user's language (the language they are writing in).

When to use

• Right after installing the RENATA plugin, in a new project directory (empty or with initial code).
• To "renata-ify" an existing project that does not yet have the structure — in that case the closing output points to /renata:adopt (full brownfield adoption).

Steps

1. Check machine dependencies

The RENATA hooks and the commit-time ADR enforcement depend on a few CLI tools. Check them all in a single Bash call:

for t in yq jq python3 git; do command -v "$t" >/dev/null 2>&1 && echo "ok       $t" || echo "MISSING  $t"; done

• yq — required: without it, rules-violation.sh does not validate rules.yaml on commit and the status line loses ADR enforcement. No fallback.
• jq or python3 — the stage gate and the status line need at least one of the two; only treat as missing if both are absent.
• git — needed for step 6 (pre-commit enforcement) and for the --starter clone.

If nothing is missing, say nothing about this step and move on.

If something is missing:

1. Detect the available package manager (brew on macOS, apt-get or dnf on Linux) and install the missing tools with it (e.g., brew install yq jq). Run the install as a normal, visible Bash call — the user's permission prompt is the consent. Never install through any other silent mechanism.
2. If there is no package manager, or the user declines the install, print the manual install command(s) and continue with the init — the hooks degrade with warnings instead of breaking, and the SessionStart warning will keep reminding the user about yq.