chore(openspec): adopt slice-driven planning schema #71
No reviewers
Labels
No labels
area/auth
area/backend
area/ci
area/deploy
area/e2e
area/frontend
area/shared
blocked
good-first-issue
needs-info
priority/high
priority/low
priority/medium
type/bug
type/chore
type/docs
type/feature
type/tech-debt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
celilo/lunacycle!71
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/openspec-slice-driven"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Sets this repo's OpenSpec schema to
slice-drivenand vendors the schema (schema.yaml+ templates) underopenspec/schemas/slice-driven/.The
config.yamlchange is one line (schema: spec-driven→schema: slice-driven).Why
slice-drivendecomposes a change into vertical slices (Goal / Consumes / Produces / Trigger-Owner / Blocked-by / Effort), checks cross-slice invariants and requirement coverage, and compiles TDD tasks just-in-time per slice against live code (red-green-verify, plus structural-guard-now + recorded-live-check for config/infra).Scope
Additive. No existing change is migrated — in-flight changes keep whatever schema they were authored under. Only new changes pick up slice-driven.
🤖 Generated with Claude Code
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.