36 lines
1.3 KiB
Markdown
36 lines
1.3 KiB
Markdown
# Design
|
|
|
|
## Scale
|
|
|
|
Scale: `standard`.
|
|
|
|
Rationale: this validation has a clear target and no business-code risk, but it intentionally exercises the full normal artifact set rather than the reduced micro path.
|
|
|
|
## Interface Impact
|
|
|
|
Interface impact: L1 internal documentation/protocol validation.
|
|
|
|
No API, DTO, database, event, service, or cross-module runtime contract changes are expected.
|
|
|
|
## Artifact Model
|
|
|
|
Standard validation requires:
|
|
|
|
- OpenSpec: `proposal.md`, independent `design.md`, `specs/`, `tasks.md`.
|
|
- Devflow archive: `brief.md`, `evidence.md`, `decisions.md`, `acceptance.md`.
|
|
|
|
The validation checks that current skill rules point to `references/scales.md` for the exact standard artifact requirements instead of redefining them elsewhere.
|
|
|
|
## Execution Design
|
|
|
|
1. Build the standard OpenSpec fixture.
|
|
2. Run static scans for standard artifact wording and duplicated scale definitions.
|
|
3. Run skill validation and reference integrity checks.
|
|
4. Record evidence separately in `devflow/.../evidence.md`.
|
|
5. Mark the fixture as committed only if artifact completeness and alignment pass.
|
|
|
|
## Risks
|
|
|
|
- The external OpenSpec archive/apply commands are not exposed in the current tool surface; this validation uses file-based checks.
|
|
- File presence does not prove independent-agent usability; forward-testing remains a separate optional validation surface.
|