sunfish-admin
12d2179c20
Ship Magisk like GOLDEN; KernelSU optional recycle only; parallel to sunfish-a16-rom standby.
1.7 KiB
1.7 KiB
Specification Quality Checklist: KernelSU-Next on sunfish (LAB)
Purpose: Validate specification completeness and quality before planning
Created: 2026-09-15
Feature: spec.md
Content Quality
- No implementation details (languages, frameworks, APIs)
- Focused on user value and business needs
- Written for non-technical stakeholders
- All mandatory sections completed
Requirement Completeness
- No [NEEDS CLARIFICATION] markers remain
- Requirements are testable and unambiguous
- Success criteria are measurable
- Success criteria are technology-agnostic (no implementation details)
- All acceptance scenarios are defined
- Edge cases are identified
- Scope is clearly bounded
- Dependencies and assumptions identified
Feature Readiness
- All functional requirements have clear acceptance criteria
- User scenarios cover primary flows
- Feature meets measurable outcomes defined in Success Criteria
- No implementation details leak into specification
Notes
- Product names required by constitution (KernelSU-Next, SusFS, Magisk-as-non-default, TrickyStore-class experiment) appear as capability choices, not code design.
- Checklist item “non-technical stakeholders”: banking PASS/FAIL and LAB-only constraints are written for the owner; kernel revision pinning is an audit need.
- SC-002 “≥95% checklist rows” assumes a concrete verification checklist in
/speckit-plan/ tasks — acceptable at specify stage. - Ready for
/speckit-plan. Yuh PASS is a hard-gate (owner 2026-09-15): without it, root is not justified vs NeoBackup + native call-rec / FLAG_SECURE.