chore(openspec): adopt slice-driven planning schema #27

Open

forgejo-admin wants to merge 1 commit from chore/openspec-slice-driven into main

pull from: chore/openspec-slice-driven

merge into: celilo:main

celilo:main

celilo:changeset-release/main

celilo:fix/capability-major-public-web-4

celilo:polecat/td-b7p

celilo:fix/electron-port-guard

celilo:fix/segment-border

celilo:feature/triage-nav

celilo:fix/triage-layout-and-queue

celilo:feature/fuel-gauge

celilo:feature/save-modes

celilo:feature/tap-key

celilo:feature/electron-shell

celilo:fix/triage-jank

celilo:feature/track-duration

celilo:feature/electronic-category

celilo:feature/reset-taps

celilo:feature/wide-triage

celilo:feature/dim-marks-sliders

celilo:feature/blues-category

celilo:feature/triage-rails

celilo:fix/triage-completes-track

celilo:library/pending-triage

celilo:chore/root-tsconfig-exclude-website

celilo:caps2-tango-dj

celilo:implement-tango-dj-app

Conversation 0 Commits 1 Files changed 6 +519 -1

forgejo-admin commented 2026-08-31 18:25:30 +00:00

Owner

Copy link

What

Sets this repo's OpenSpec schema to slice-driven and vendors the schema (schema.yaml + templates) under openspec/schemas/slice-driven/.

The config.yaml change is one line (schema: spec-driven → schema: slice-driven).

Why

slice-driven decomposes 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

## What Sets this repo's OpenSpec schema to `slice-driven` and vendors the schema (`schema.yaml` + templates) under `openspec/schemas/slice-driven/`. The `config.yaml` change is one line (`schema: spec-driven` → `schema: slice-driven`). ## Why `slice-driven` decomposes 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](https://claude.com/claude-code)

forgejo-admin added 1 commit 2026-08-31 18:25:30 +00:00

chore(openspec): adopt slice-driven planning schema ... 126d84af71

Set the project's OpenSpec schema to slice-driven and vendor the schema
(schema.yaml + templates) under openspec/schemas/. New changes now decompose
into vertical slices with just-in-time per-slice TDD task compilation.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin chore/openspec-slice-driven:chore/openspec-slice-driven

git switch chore/openspec-slice-driven

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

celilo/tango-dj!27

No description provided.