---
name: step-by-step
description: "Keep iterative user conversations to one current unit: requirement clarification, conversational reviews, task discussions, triage and revision rounds. Not for autonomous execution, scheduling, delegation or worker concurrency."
---

# Step by step

Keep an iterative conversation focused on exactly one current unit: a question, review section, discussed task or equivalent defined by the active workflow.

## Sequence

1. Identify the ordered units without presenting them all at once.
2. Make one unit current. Present that unit only.
3. Resolve, complete or explicitly block it before moving to the next. If it needs the user's response, wait for that response.
4. Keep naturally atomic units whole. Neither bundle independent units for speed nor split one unit into artificial fragments.

When the current unit needs a decision, give one clear, reasoned recommendation first. Include up to four meaningful alternatives only when they help; invent none. Then ask one concrete question that advances the unit. Do not hand back an unguided menu or an unexplained “A or B?” question. For a factual question without a basis for a recommendation, ask for the missing fact without inventing advice.

## Scope and user choice

Load this skill when the first matching iterative conversation occurs, not merely at session start. Reuse the loaded instructions for later matching conversations; reread after a resource reload or a relevant content change. Autonomous execution and worker concurrency do not activate this technique.

Follow an explicit user-selected presentation or sequence change, including a request to present several units together. A general request for brevity, speed or fewer acknowledgements alone does not select a different sequence. Preserve other governing requirements when changing presentation. If a higher-priority rule or concrete contradiction prevents the requested sequence, name the conflict rather than silently improvising.

This skill owns conversational sequencing only. The active domain workflow owns its questions, state, record, approval rules and completion criteria. Step by Step creates and maintains no files and adds no workflow state, scheduling system or delegation mechanism.

This is an adaptable Skill example, not an installed resource. Native Pi advertises and loads Skills; reading this file applies instructions, not an invocation API or permission grant.