Aulafy
ESEN
Courses
Courses/Claude Code, from zero to pro/Pro Workflows
Lesson

Pro Workflows

The features and routines that separate occasional Claude Code users from those who truly get the most out of it: plan before you act, undo without fear, and work in parallel.

Plan Mode

In Plan Mode, Claude explores and investigates your code and proposes a detailed plan, but without touching any files. You review it and, if you're satisfied, give the green light to execute it. It's the best safety net for large tasks.

How to enable it

  • Press Shift + Tab to toggle the mode (press again to exit).
  • O al iniciar: claude --permission-mode plan

Checkpoints and Rewind (undo)

Every time you send a message, Claude Code creates a checkpoint (a save point). If a change goes wrong, you can roll back both the conversation and the code to an earlier state.

How to undo

  • Use the /rewind command to choose which point to return to.
  • Press Esc Esc (twice) as a "panic button."

Background tasks

You can launch tasks or subagents that run in the background while you keep working on something else in the main session. Perfect for long-running processes (heavy tests, builds, extensive research).

How to use it

  • Launch in background: claude --bg "your task"
  • Press Ctrl + B or ask it to "run this in the background."
  • Manage processes with claude agents (view, attach, logs, stop).

Output styles

Control how Claude Code responds—especially useful for scripts and automations:

TerminalCode
# Salida en texto normal (por defecto)
claude -p "resume los cambios" --output-format text

# Salida en JSON (para procesar con scripts)
claude -p "lista los TODO" --output-format json

# Salida en streaming JSON (para integraciones en vivo)
claude -p "analiza el repo" --output-format stream-json

You can also define custom styles (e.g., an "explanatory" mode that teaches more—ideal for learning) through configuration or the system prompt.

Most recommended workflows

Here's what the Claude Code community is sharing and recommending as best practices:

  • Plan Mode first, always. Before any serious task: Shift + Tab → review the plan → execute. Avoid surprises.
  • Parallel subagents + background. Delegate research, coding, tests, and review at the same time. Monitor with claude agents.
  • Standardized skills. Create or install skills for review, deploy, and test. Use disable-model-invocation: true on those with side effects (like deploy) so they don't launch on their own.
  • Rewind / Esc Esc as a panic button when something goes wrong.
  • Hooks + MCP to integrate your environment: automatic formatting after edits, connection with Slack or your ticket manager.
  • Intensive review before production. A rigorous review pass (with a powerful model) before pushing important changes.
  • A lightweight CLAUDE.md + specific skills, and version the .claude/ folder in your repository so the team shares the same configuration.

Check your version

Claude Code updates very frequently (frequent releases). If a feature here doesn't show up for you, update:

TerminalCode
claude --version
npm update -g @anthropic-ai/claude-code
PluginsCommands