Skip to main content
Use these task examples for project exploration, features, bug fixes, long tasks, parallel agents, and static websites. Adapt paths and requirements to your project.

​
Understanding an unfamiliar project

Start with read-only investigation before deciding what to change. To restrict tool operations, choose Read Only in /permissions.
After reviewing the findings, use /init to capture project conventions in AGENTS.md.

​
Implementing a feature

Provide requirements and acceptance criteria together. Plan first when changes span modules.

​
Fixing bugs

Include symptoms, reproduction conditions, expected behavior, and relevant files. Attach screenshots or use ! to add diagnostic command output to context.

​
Tests and refactoring

Use /fork to separate conversation experiments. Code changes still share the working directory; use a Git worktree when file isolation is needed.

​
Delegating long tasks

Use /goal for hours-long work. Step Code continues after you set the goal; check progress with /goal status when you return.
Use /goal pause to pause and /goal resume to continue. Keep the process and network available. See Goal mode. Ask the model to create a cron schedule for recurring work, such as dependency security checks, and manage it with /cron. A durable task file is not an operating-system scheduling service; the runtime must remain available.

​
Parallel agents

Use workflow for batches of similar tasks, such as audits or comparing alternatives. Explicitly authorize it with ultraloop or ultracode; task size alone does not enable it.
For parallel writes, assign disjoint files or explicitly request separate worktrees. Each agent consumes tokens independently. See Agents and subagents.

​
Publishing static websites

The built-in steppage plugin publishes a directory as a shareable static website. Install it and set STEPFUN_API_KEY:
Restart Step Code, confirm the service in /mcp, then request deployment:
Manage sites and versions at platform.stepfun.com/sites. Deployment uploads files, so inspect the output first. See steppage: publish static websites.

​
Generating and maintaining documentation

Use /export to preserve important discussions, but do not replace maintained project documentation with conversation exports.

​
Next steps