99187460b1
Implement complete workflow for checking and applying OpenCode updates: - check-version.sh: Compare current vs latest GitHub release - fetch-sha256.sh: Fetch SHA256 hash using nix-prefetch-url - update-nix-file.sh: Update Nix package definition with dry-run support - verify-update.sh: Verify installed version matches expectation Includes comprehensive documentation (SKILL.md for agents, README.md for users) and full spec in specs/002-update-opencode/ with user stories and acceptance criteria. Eliminates manual Nix file editing and hash lookups for OpenCode updates.
2 KiB
2 KiB
Specification Quality Checklist: Update OpenCode Skill
Purpose: Validate specification completeness and quality before proceeding to planning
Created: 2025-11-11
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
Validation Notes
Content Quality: ✅ PASS
- Specification describes WHAT and WHY without implementation details
- Success criteria focus on user outcomes (time to complete, success rates, audit compliance)
- Language is accessible to operations team members
Requirement Completeness: ✅ PASS
- All 16 functional requirements are testable and specific
- No clarification markers present - all assumptions documented
- Edge cases cover network failures, partial updates, version conflicts
- Scope clearly separates in-scope (Nix updates) from out-of-scope (npm, rollback automation)
Feature Readiness: ✅ PASS
- Three prioritized user stories (P1: check, P2: update, P3: pinning) with independent test scenarios
- Success criteria are measurable and technology-agnostic
- Acceptance scenarios use Given/When/Then format consistently
Overall Status: ✅ READY FOR PLANNING
All checklist items pass. The specification is complete, unambiguous, and ready for /speckit.plan to create implementation plan.