Validate SM Flow Explicit Trigger Acceptance

Result

Accepted and archived.

Trigger rule verification:
- SKILL.md frontmatter says sm-flow is only used for explicit /sm-flow commands or explicit natural-language requests.
- SKILL.md trigger section says task type alone must not auto-trigger sm-flow.
- operating-rules.md startup checks now include explicit natural-language requests.
Scale source verification:
- Scale definition scan found standard, micro, and complex definition headings and definition phrases only in references/scales.md.
- Other files refer to references/scales.md instead of redefining the scale rules.
Obsolete wording verification:
- No matches for minute/hour/second/timebox metrics.
- No matches for old skip semantics or old fixed proposal.md + design.md expression.
- No matches for old conflict wording targeted by this validation.

Passed: python C:/Users/兜/.codex/skills/.system/skill-creator/scripts/quick_validate.py .agents/skills/sm-flow
Passed: reference integrity scan for references/*.md.

Not applicable. This change only modifies skill protocol text and validation records.

Real external OpenSpec CLI integration was not executed because the current tool surface does not expose those child commands.
Forward-testing with an independent subagent was not run in this pass.

Replaced remaining hard-coded design.md wording in phase/audit fallback rules where the protocol must respect scale-specific design artifacts.
Added explicit natural-language sm-flow requests to startup checks.

.archive-ready is present.
User confirmed archive.
Archived location: openspec/archive/2026-07-05-validate-sm-flow-explicit-trigger/.
Status: archived.
Archive method: local filesystem archive following existing repository convention because external openspec-archive-change is not directly callable in the current tool surface.