Refine sm-flow trigger and scale rules

This commit is contained in:
aruo
2026-07-05 14:30:15 +08:00
parent 433f7a93a4
commit e4f6e013a5
28 changed files with 937 additions and 105 deletions
@@ -0,0 +1,33 @@
# Validate SM Flow Standard Change Acceptance
## Result
Accepted and archived.
## Static Validation
- Scale rule centralization passed.
- Obsolete wording scan passed.
- Standard artifact completeness passed.
- Cross-artifact alignment passed.
## Script Validation
- Passed: skill quick validation.
- Passed: reference integrity scan.
## Browser Or Manual Validation
- Not applicable. This validation covers skill protocol files and OpenSpec/devflow records.
## Unverified
- External OpenSpec CLI integration.
- Independent forward-testing by a separate agent.
## OpenSpec Archive
- User confirmed archive.
- Archived location: `openspec/archive/2026-07-05-validate-sm-flow-standard-change/`.
- 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.
@@ -0,0 +1,25 @@
# Validate SM Flow Standard Change Brief
## Background
The micro validation confirmed the reduced path. This record validates the normal standard path, where independent design and separate evidence are required.
## Goal
Confirm that the current `sm-flow` skill supports a standard change with complete OpenSpec and devflow artifacts.
## Scope
- Validate standard artifact requirements.
- Validate scale rule centralization.
- Validate skill structure and reference integrity.
## Non-Goals
- No business code changes.
- No archive move without user confirmation.
- No complex migration, rollback, or cross-team interface test.
## Linked OpenSpec
`openspec/changes/validate-sm-flow-standard-change/`
@@ -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`.
@@ -0,0 +1,34 @@
# Validate SM Flow Standard Change Evidence
## Static Evidence
- Scale definition scan found complete `standard / micro / complex` definition headings and definition phrases only in `.agents/skills/sm-flow/references/scales.md`.
- Obsolete wording scan returned no matches for:
- minute/hour/second/timebox metrics
- old skip semantics
- old fixed `proposal.md + design.md` expression
- old conflict wording targeted by prior validation
## Script Evidence
- Passed: `python C:/Users/兜/.codex/skills/.system/skill-creator/scripts/quick_validate.py .agents/skills/sm-flow`
- Passed: `references/*.md` integrity scan.
## Artifact Evidence
- OpenSpec standard artifacts exist:
- `openspec/changes/validate-sm-flow-standard-change/proposal.md`
- `openspec/changes/validate-sm-flow-standard-change/design.md`
- `openspec/changes/validate-sm-flow-standard-change/specs/sm-flow-standard-change/spec.md`
- `openspec/changes/validate-sm-flow-standard-change/tasks.md`
- Devflow standard artifacts exist:
- `brief.md`
- `evidence.md`
- `decisions.md`
- `acceptance.md`
## Limits
- This validation is static/file-based.
- It does not run a real external OpenSpec CLI command.
- It does not include independent subagent forward-testing.