Compatibility command for the streamlined unattended developer workflow. Plans a software task with sl-plan when needed, then routes execution through sl-run in mode:unattended. Prefer sl-plan followed by sl-run for new workflows.
Run an explicit, non-mutating compatibility diagnostic for the super-looper plugin. Use only when validating a Claude Code or Codex installation, runtime adapter, bundled reference and script resolution, interactive question support, and one-worker subagent…
Compatibility command for interactive implementation. Plans a software task when needed, then routes canonical Markdown execution through sl-run in mode:interactive. Prefer sl-run directly for new workflows.
Compatibility command for the streamlined unattended developer workflow. Plans a software task with sl-plan when needed, then routes execution through sl-run in mode:unattended. Prefer sl-plan followed by sl-run for new workflows.
Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request,…
Document a recently solved problem to compound your team's knowledge or CONCEPTS.md, the project's shared domain vocabulary.
Create a compact cross-session handoff for research, debugging, design, or other non-run work whose important context is not already durable. Do not use for sl-run work: its state path and review packet are the handoff.
Run an explicit, non-mutating compatibility diagnostic for the super-looper plugin. Use only when validating a Claude Code or Codex installation, runtime adapter, bundled reference and script resolution, interactive question support, and one-worker subagent…