SCE workflow tutorial

1. Prepare the repository

Work from the correct branch, understand the working tree, ensurecontext/exists and reflects the project, and confirm your AI environment has the SCE commands, agents, and skills installed. Know the change goal, constraints, and success criteria before planning begins.

You can check whether SCE is ready by running this command, which validates that your SCE commands, agents, and skills are installed:

sce validate

Ifsceis not installed yet, start with thegetting started guidebefore continuing.

If setup or context is missing, expect the agent to ask before bootstrapping or repairing it. The human remains responsible for architecture, risk, and final decisions.

2. Turn your change request into a plan

Start by describing the change in plain language:

/change-to-plan [your change request]

The planning agent should read context, ask clarification questions when needed, and invite you to clarify or change anything through conversation until the plan is correct. It will then create or update a plan incontext/plans/, and break the work into stable task IDs such asT01,T02, andT03. Each task should capture its goal, boundaries, done criteria, and verification notes.

3. Run one task at a time

Continue with an approved task using the plan name or path and, when known, the task ID:

/next-task onboarding-flow T01

Don't worry if you are unsure what to run next. SCE will prompt you with the next step command.

The execution agent should review readiness first: resolve the plan, confirm the selected task, check for blockers, and keep the session to one task unless you explicitly approve more.

4. Confirm before implementation

Before editing files, the agent should stop and restate the task goal, scope boundaries, expected files, done checks, approach, trade-offs, and risks. Only continue after you confirm.

5. Implement, check, and capture evidence

During implementation, the agent should make the smallest in-scope change that satisfies the task. If out-of-scope work is required, it should stop and ask before expanding scope.

Each task should report evidence of what changed, which checks ran, and how the result was validated. Checks may include content inspection, targeted tests, linting, type checks, or a fast build.

You are invited to clarify or change anything through conversation so the task result is correct before moving on.

6. Sync context after each task

After an accepted implementation task, the agent should compare the changed behavior withcontext/and update current-state context files when needed. Code is the source of truth if context and code disagree.

7. Run the next task

If more tasks remain, start a new session for the next task:

/next-task onboarding-flow T02

Don't worry if you are unsure what to run next. SCE will prompt you with the next step command.

Each task repeats the same review, confirmation, implementation, checks, and context-sync cycle.

Repeat steps 3 through 7 until all planned tasks are complete.

8. Finish with validation and cleanup

The last step in an SCE plan is always a validation step. When the final task is complete, the agent should review the work against the plan success criteria, run applicable checks, confirm context accuracy, and perform allowed cleanup.

You are invited to clarify or change anything through conversation so the final task is correct before the workflow is considered complete.