@taskless/cli 0.7.0 → 0.8.0

package/README.md

@@ -32,8 +32,8 @@ Outputs CLI version, tool status, and login info as JSON to stdout:
 ### `taskless init`
 
 Launches an interactive wizard that detects supported tool directories in the
-current project (`.claude/`, `.opencode/`, `.cursor/`, `.agents/`), lets you
-pick which ones to install into, and walks through the auth tradeoff before
+current project (`.claude/`, `.opencode/`, `.cursor/`, `.agents/`), asks which
+tools to enable Taskless for, and walks through the auth tradeoff before
 writing anything. Running `taskless` with no subcommand in a TTY also launches
 this wizard. Without a TTY, bare `taskless` prints a short context preamble
 followed by the topic index from `taskless help`.
@@ -41,6 +41,13 @@ followed by the topic index from `taskless help`.
 In v0.7+, there is exactly one skill (`taskless`) and one command (`tskl`) —
 no opt-in selection needed.
 
+The skill and command content is written **once** to a canonical store in
+`.taskless/skills/` and `.taskless/commands/`. Each enabled tool directory
+receives only a thin reference stub — an ordinary file with a delegating body,
+never a symlink — so there is a single source of truth and no drift between
+copies. Stale layouts from earlier versions (full per-tool copies, symlinks)
+are converged into stubs automatically on the next `init`/`update`.
+
 For CI and scripted installs, pass `--no-interactive` to skip all prompts:
 
 ```bash
@@ -54,6 +61,38 @@ selected. Upgrading from v0.6 automatically removes the obsolete per-task
 skills and commands during this diff. Cancelling the wizard at any step
 (Ctrl-C) aborts cleanly with no filesystem changes.
 
+### `taskless onboard`
+
+Post-install discovery flow that helps a fresh user go from zero rules to a
+useful starter set. Run it after `taskless init`. The CLI prints an
+agent-facing recipe that walks the host AI tool through scanning the
+codebase, agent-memory files (CLAUDE.md / AGENTS.md / .cursorrules),
+recent PR review comments (when `gh` is available), and issue tracker
+tickets (when a relevant MCP is wired in) for high-signal rule
+candidates, then surfaces them as a bullet list the user can choose to
+materialize via `taskless rule create`.
+
+```bash
+taskless onboard                  # print the recipe (refused if already complete)
+taskless onboard --force          # re-run even when previously marked complete
+taskless onboard --mark-complete  # record completion in .taskless/taskless.json
+                                  # (invoked by the agent after explicit user
+                                  # confirmation; never automatically)
+```
+
+Onboarding state lives in `.taskless/taskless.json` as
+`install.onboarded` — a 3-state optional field (absent / `false` / `true`).
+Only the agent writes it, and only with the user's explicit confirmation.
+`taskless init` does not set it. Pass `--force` to re-run regardless of the
+current value.
+
+After a successful `taskless init`, the CLI prints a one-line trailer
+pointing the user at this command. The trailer wording adapts to the
+install plan: when the install included slash commands (Claude Code or
+Cursor), it mentions `/tskl onboard` along with the Taskless skill and the
+bare CLI; when the install only wrote skills (OpenCode, Codex, the
+`.agents/` fallback), it mentions the skill and the bare CLI only.
+
 ### `taskless check`
 
 Run ast-grep rules from `.taskless/rules/` against the codebase. Exits with code 1 if any error-severity matches are found.