Refine sm-flow trigger and scale rules
This commit is contained in:
@@ -0,0 +1,52 @@
|
||||
# Validate SM Flow Standard Change Decisions
|
||||
|
||||
## Capability Source
|
||||
|
||||
- This is an ordinary engineering validation, not an explicit sm-flow invocation.
|
||||
- External OpenSpec child commands are not directly callable in the current tool surface.
|
||||
- Validation uses file-based OpenSpec fixtures and static/script checks.
|
||||
|
||||
## Scale Decision
|
||||
|
||||
- Scale: `standard`.
|
||||
- Reason: this validation intentionally exercises the full normal artifact set: proposal, independent design, specs, tasks, and separate evidence.
|
||||
- Interface impact: L1 internal documentation/protocol validation.
|
||||
|
||||
## Question Pool
|
||||
|
||||
| Question | Mode | Status | Result |
|
||||
| --- | --- | --- | --- |
|
||||
| Does standard require independent `design.md`? | evidence-driven | confirmed | `references/scales.md` defines independent `design.md` for standard. |
|
||||
| Does standard require separate `evidence.md` in devflow? | evidence-driven | confirmed | `references/scales.md` defines `brief.md`, `evidence.md`, `decisions.md`, `acceptance.md`. |
|
||||
| Are standard scale definitions duplicated outside `scales.md`? | evidence-driven | confirmed | Scale definition scan matched complete scale definitions only in `references/scales.md`. |
|
||||
| Is user scope confirmation needed? | user-interview | not required | User asked to validate a regular change; no product scope choice is blocked. |
|
||||
|
||||
## Cross-Artifact Alignment
|
||||
|
||||
| Link | Status | Notes |
|
||||
| --- | --- | --- |
|
||||
| proposal -> design | aligned | Proposal asks for standard artifact validation; design defines standard artifact model. |
|
||||
| design -> specs | aligned | Specs require full OpenSpec artifacts, evidence archive, and centralized scale definitions. |
|
||||
| specs -> tasks | aligned | Tasks include fixture creation, validation scans, commit gate, and devflow records. |
|
||||
|
||||
## Findings
|
||||
|
||||
- Standard OpenSpec artifact completeness passed: `proposal.md`, independent `design.md`, spec file, and `tasks.md` exist.
|
||||
- Cross-artifact alignment passed: proposal -> design -> specs -> tasks.
|
||||
- Scale duplication scan passed.
|
||||
- Obsolete wording scan passed.
|
||||
- Skill quick validation passed.
|
||||
- Reference integrity scan passed.
|
||||
|
||||
## Commit Gate
|
||||
|
||||
- `.committed` created.
|
||||
- Status: committed standard validation fixture.
|
||||
|
||||
## Archive Status
|
||||
|
||||
- Devflow standard records created.
|
||||
- User confirmed OpenSpec archive.
|
||||
- External `openspec-archive-change` was not directly callable in the current tool surface.
|
||||
- Archived by moving the OpenSpec change to `openspec/archive/2026-07-05-validate-sm-flow-standard-change/`, matching existing repository archive convention.
|
||||
- `devflow/index.md` status updated to `archived`.
|
||||
Reference in New Issue
Block a user