02 / Methods

Twelve methods. None mandatory by default.

These plugin-native names describe distinct engineering pressures. Natural-language work may stay direct or route into one method; a person can also choose any method explicitly.

Servotab methods

ordinary / Describe the complete outcome normally. Servotab may keep the work direct.

explicit / Use a name such as $review when you want precise control.

designinvoke / $design

Clarifies unsettled product, interaction, or architecture choices until implementation can proceed with confidence.

Use when a real decision is still open.

Read method contract

spec-chaininvoke / $spec-chain

Carries an approved specification into a complete, traceable implementation plan without shrinking the accepted outcome.

Use when the specification is already authoritative.

Read method contract

planinvoke / $plan

Structures settled multi-step work when no adopted specification already owns the complete plan.

Use when sequencing matters before edits begin.

Read method contract

executeinvoke / $execute

Turns a settled request or plan into working code through coherent, verified slices.

Use when the route is known and the work should move.

Read method contract

debuginvoke / $debug

Reproduces the failure, traces its causal mechanism, and restores the contract with focused evidence.

Use when behavior is wrong or unexplained.

Read method contract

tddinvoke / $tdd

Uses tests as design and evidence, with strict red-green discipline where it materially sharpens the contract.

Use for rules, state, parsers, regressions, and risky boundaries.

Read method contract

reviewinvoke / $review

Inspects a diff or implementation for concrete, actionable defects against the real goal and repository truth.

Use when another pair of eyes should challenge the change.

Read method contract

review-feedbackinvoke / $review-feedback

Validates external review feedback against current source before applying a narrow, justified correction.

Use when feedback arrives from a reviewer or bot.

Read method contract

verifyinvoke / $verify

Matches fresh evidence to the exact claim, broadening checks only when the blast radius requires it.

Use when readiness or completion needs proof.

Read method contract

worktreeinvoke / $worktree

Chooses, reuses, restores, and parks workspaces while preserving work, host ownership, and explicit cleanup authority.

Use to resume, isolate, organize, or safely retire a workspace.

Read method contract

delegateinvoke / $delegate

Chooses responsibility before deep work: keeps one responsibility's coupled parts in a single lane, coordinator or worker, and hands a bounded lane to a worker with an explicit return.

Use when clean context or coordinator attention repays the handoff.

Read method contract

finishinvoke / $finish

Closes the engineering loop with scoped validation, documentation truth, integration choices, and an honest handoff.

Use when the work must become safely resumable or ready to integrate.

Read method contract

Selection rule

The risk chooses the depth.

Method names do not create permission or ceremony. The current task, repository evidence, host capability, and user authority decide what is useful. Clear work can still bypass the list entirely.