Sdlc Step Body Standard

S1: Every step.md body MUST open with `# {Step Name}` matching frontmatter `name:`.

H1 anchors the rendered XML prompt's `<prompt>` section.

S2: Every step.md body MUST contain a `## Context` block with Application/Scope (and Goal when available).

Template variables — agent always knows where it is.

S3: Sub-steps MUST be numbered `## Step N — <verb>` form. NEVER bullet-lists at the top level.

Order matters; numbers enforce it. The XML prompt sees them as positional steps.

S4: Where a component / package / standard exists in the codebase, the step body MUST name it with its EXACT identifier (backtick-quoted).

S5: Anti-patterns MUST be paired with the correct alternative — `BAD: X / GOOD: Y` blocks.

Telling the LLM what NOT to do without saying what TO do invites improvisation.

S6: Output structure MUST be specified — either a literal template fragment OR a reference to the `output:` block in the frontmatter.

S7: Verify-and-Exit pattern is the last two sections. Verify MUST contain a concrete `sbx` command; Exit MUST instruct `sbx sdlc complete`.

Universal close — every step ends the same way.

S8: Discover step MUST list all `sbx` commands the agent needs to run, NOT general advice.

S9: No section MAY contain prose that duplicates the frontmatter (`agent`, `role`, `personality`, `knowledge.required`).

Frontmatter is the contract; body is the procedure. Repetition wastes tokens and creates drift risk.

S10: When a step references a knowledge artifact, it MUST be named in `knowledge.required` or `knowledge.available` in the frontmatter — never just in body prose.

Knowledge refs in the body without a corresponding frontmatter entry are invisible to the renderer.