help
Learn how to use devloop - interactive guide to commands, workflow, and best practices
What this skill does
# Devloop Help
Interactive guide to devloop.
## Step 1: Choose Topic
If `$ARGUMENTS` specifies a topic, skip to that section. Otherwise:
```yaml
AskUserQuestion:
questions:
- question: "What would you like to learn about?"
header: "Topic"
multiSelect: false
options:
- label: "Getting Started"
description: "New to devloop? Start here"
- label: "Commands"
description: "What each command does"
- label: "The Loop"
description: "The plan -> run -> fresh cycle"
- label: "Skills & Agents"
description: "On-demand knowledge and parallel work"
- label: "Superpowers"
description: "How devloop works with superpowers plugin"
```
---
# Topic: Getting Started
## What is devloop?
Development workflow where **Claude does the work directly**. No routine agents. Just you, Claude, and the code.
## Quick Start
```bash
/devloop:plan "How should we implement feature X?" # Plan (or --deep for exploration)
/devloop:run # Execute tasks
/devloop:fresh && /clear # Save state, clear context (every fresh_threshold tasks (default 10, configurable in .devloop/local.md))
/devloop:run # Continue execution
```
## First Session
1. Have a task? `/devloop:plan [task]` (or `--deep` for detailed exploration)
2. Claude explores, creates plan
3. You approve
4. `/devloop:run` to implement
5. Every fresh_threshold tasks (default 10, configurable in .devloop/local.md): `/devloop:fresh` then `/clear` then `/devloop:run`
6. Done? `/devloop:ship`
---
# Topic: Commands
## Decision Tree
```
Starting new work?
|-- Unclear requirements -> /devloop:plan --deep
|-- Small, clear task -> /devloop:plan --quick
|-- Normal feature -> /devloop:plan
|-- Have a plan -> /devloop:run
Mid-workflow?
|-- Context heavy -> /devloop:fresh -> /clear -> /devloop:run
|-- Ready to commit -> /devloop:ship
|-- Want review -> /devloop:review
Returning?
|-- /devloop:run
```
## Command Reference
| Command | Purpose |
|---------|---------|
| `/devloop` | Start new workflow (smart entry point) |
| `/devloop:plan` | Autonomous planning (default mode) |
| `/devloop:plan --deep` | Comprehensive exploration with spike report |
| `/devloop:plan --quick` | Fast path for small, clear tasks |
| `/devloop:plan --from-issue N` | Start from GitHub issue #N |
| `/devloop:run` | Autonomous execution |
| `/devloop:run --interactive` | With checkpoints |
| `/devloop:run --next-issue` | Full issue-to-ship pipeline |
| `/devloop:run-swarm` | Swarm for 10+ tasks |
| `/devloop:fresh` | Save state for clear |
| `/devloop:review` | Code review |
| `/devloop:ship` | Commit & PR |
| `/devloop:archive` | Archive completed plan |
| `/devloop:new` | Create GitHub issue |
| `/devloop:issues` | List GitHub issues |
| `/devloop:statusline` | Configure statusline |
| `/devloop:help` | This guide |
### Migration from Old Commands
| Old Command | New Command |
|-------------|-------------|
| `/devloop:spike` | `/devloop:plan --deep` |
| `/devloop:quick` | `/devloop:plan --quick` |
| `/devloop:from-issue N` | `/devloop:plan --from-issue N` |
| `/devloop:continue` | `/devloop:run --interactive` |
| `/devloop:ralph` | `/devloop:run` |
---
# Topic: The Loop
## Pattern
```
/devloop:plan [topic] -> Creates plan
|
/devloop:run -> Implements tasks
|
After fresh_threshold tasks (default 10, configurable in .devloop/local.md)?
|-- Yes -> /devloop:fresh -> /clear -> /devloop:run
|-- No -> Continue
```
## Why It Works
- Fresh context = better reasoning
- Plan preserves progress
- Checkpoints keep control
- Sustainable pace
## When to Fresh
- After fresh_threshold tasks (default 10, configurable in .devloop/local.md)
- When responses slow
- After long exploration
- Before taking a break
## State Files
| File | Purpose |
|------|---------|
| `.devloop/plan.md` | Current plan (persists) |
| `.devloop/next-action.json` | Fresh state (consumed) |
| `.devloop/worklog.md` | Work history |
---
# Topic: Skills & Agents
## Skills: On-Demand Knowledge
Load when needed: `Skill: skill-name`
| Skill | Purpose |
|-------|---------|
| `plan-management` | Working with plan.md |
| `local-config` | Project settings via .devloop/local.md |
| `pr-feedback` | Integrate PR review comments |
| `devloop-audit` | Audit devloop against Claude Code updates |
**Don't preload.** Claude loads automatically when needed.
## Agents: Parallel Work Only
**Use for:** parallel implementations, security scans, large exploration (50+ files)
**Don't use for:** writing code, tests, git ops, single files, docs
| Agent | Purpose |
|-------|---------|
| `devloop:engineer` | Exploration, architecture, code review |
| `devloop:qa-engineer` | Test generation |
| `devloop:security-scanner` | OWASP, secrets |
| `devloop:doc-generator` | READMEs, API docs |
| `devloop:swarm-worker` | Parallel task execution |
---
# Topic: Troubleshooting
## Common Issues
**Plan corrupted:** `rm .devloop/plan.md && /devloop`
**Session ended:** `/devloop:run`
**Abandon plan:** `/devloop:archive && /devloop`
**Context heavy:** `/devloop:fresh && /clear && /devloop:run`
**Skill not loading:** Check exact name in skills/INDEX.md
**Progress not saving:** Use `[x]` not `[X]`
**Statusline missing:** `/devloop:statusline`, restart Claude Code
## Claude Code Native Integrations
**LSP tools in agents**: `engineer`, `qa-engineer`, and `security-scanner` agents use LSP for symbol navigation (`goToDefinition`, `findReferences`, `documentSymbol`). Gracefully falls back to Grep/Glob if no LSP server is configured.
**Monitor for long commands**: `run`, `run-epic`, and `run-swarm` use Monitor (not Bash) for test suites, builds, and full-codebase linting to stream output in real-time. Falls back to Bash if Monitor is unavailable.
**Worktree isolation**: `run-swarm --worktrees` runs each worker in an isolated git worktree. Enable via flag or `git.worktree_isolation: true` in `.devloop/local.md`. Off by default.
**Token budget**: `tokens.token_budget` in `.devloop/local.md` caps how many tokens `gather-task-context.sh` collects per task (default: 4000). Lower for leaner context; raise for large codebases.
**Cache-friendly context**: `tokens.cache_friendly_context: true` (default) reorders agent spawn prompts to maximize prompt cache hits, reducing API costs on repeated runs.
## Reset Everything
```bash
rm -rf .devloop/ && /devloop
```
---
# Topic: Automation
## Autonomous Execution
```bash
/devloop:run # Up to 50 iterations
/devloop:run --max-iterations 100 # Custom limit
/devloop:run --interactive # With checkpoints
```
## How It Works
1. `/devloop:run` creates ralph-loop state
2. Claude works on tasks, marks `[x]`
3. When all done, outputs `<promise>ALL PLAN TASKS COMPLETE</promise>`
4. Loop terminates
## Context Guard
Auto-exits at 70% context usage. Configure in `.devloop/local.md`:
```yaml
context_threshold: 80
```
## Stopping Early
- `/cancel-ralph`
- Max iterations reached
- Context guard triggered
---
---
# Topic: Superpowers
## Complement, Not Dependency
Devloop and superpowers are complementary plugins with distinct lanes:
- **Devloop** = Workflow orchestration (plan, run, fresh, ship)
- **Superpowers** = Quality practices (TDD, debugging, verification, code review)
Devloop works fully standalone. Superpowers is optional.
## When to Use Which
| Task | Use |
|------|-----|
| Plan and implement a feature | `/devloop:plan` -> `/devloop:run` |
| Write tests first, then code | `superpowers:test-driven-development` |
| Debug a failing test | `superpowers:systematic-debugging` |
| Quick review of changes | `/devloop:review` |
| Thorough code review | `superpowers:requesting-code-review` |
| Commit and PR | `/devloop:ship` |
## Key Difference
- `/devloop:plan` creRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.