30 lines
1012 B
Markdown
30 lines
1012 B
Markdown
# Validate SM Flow Explicit Trigger Brief
|
|
|
|
## Background
|
|
|
|
`sm-flow` was simplified so it should only run on explicit user invocation. Related cleanup centralized scale rules, removed time-based metrics, and separated fallback/glossary details into references.
|
|
|
|
## Goal
|
|
|
|
Validate the current `sm-flow` design by running a real micro OpenSpec change through Discover, Commit, Apply, and Archive.
|
|
|
|
## Scope
|
|
|
|
- Validate `.agents/skills/sm-flow/SKILL.md`.
|
|
- Validate `.agents/skills/sm-flow/references/*.md`.
|
|
- Fix any protocol inconsistency found during validation.
|
|
- Record fallback capability source because external OpenSpec commands are unavailable in the current tool surface.
|
|
|
|
## Non-Goals
|
|
|
|
- No business code changes.
|
|
- No changes to the four visible checkpoints or nine internal phases.
|
|
- No automatic trigger heuristics.
|
|
- No historical archive rewrites.
|
|
|
|
## Scale
|
|
|
|
- Scale: `micro`.
|
|
- Evidence is folded into `decisions.md`.
|
|
- Linked OpenSpec change: `openspec/changes/validate-sm-flow-explicit-trigger/`.
|