slice-outline
Skill1 starsChanged 3 months agoMITView on GitHub
Defines the content and structure of a Slice record and its Size — the Stage 3 Solution Outline unit of delivery. Reference when assembling or reviewing slices/<id>/slice.json and size.json.
In this repository17 other files it gives its agents.
- acceptance-criteriaSkill
- adjudication-recordSkill
- adrSkill
- behavior-inventorySkill
- characterization-suiteSkill
- context-modelSkill
- contract-testsSkill
- cutover-planSkill
- design-docSkill
- divergence-registerSkill
- interface-inventorySkill
- migration-waypointsSkill
- observability-specSkill
- retirement-registerSkill
- roadmapSkill
- tactical-modelSkill
- variation-policySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
If a Slice's true size is not yet knowable (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Slice Outline
Defines what a Slice record and its Size contain. Does not define how Behaviors get partitioned into Slices — that judgment happens during Stage 3 drafting; this skill only governs the resulting artifact shapes.
Schemas
schemas/slice.schema.json (slices/<id>/slice.json) and schemas/size.schema.json (slices/<id>/size.json).
Required fields — Slice
id (SLC-NNNN), workstream (WS-NNNN), oracle_strategy, behaviors, state. oracle_strategy is required on every Slice, always — v1 accepts only "characterization"; "specification" is a reserved value for a future oracle and must be rejected in v1 with the message "Specification oracle is not implemented in this version." (seam S1.1).
Required fields — Size
slice, behaviors, interfaces_sync, interfaces_async. Contains no dates — size.json is scope only; dates belong exclusively to Stage 4's roadmap. A duration_days field on a size.json is a schema violation, not a convenience.
Content obligations
Every Behavior in scope must be assigned to exactly one Slice — behaviors[] is how the Stage 3 gate (trace-lint.py --stage 3) checks that no Behavior is left unassigned or double-assigned. Track failure_path_behaviors, divergences_open, consumers_affected, and data_migration_required in Size — these are the real cost drivers Stage 4's capacity model reads (11-estimation.md §2.1), not vanity metrics.
Behavior-ID citation
behaviors[] on the Slice record is itself the citation — every Behavior ID it lists is now this Slice's responsibility to deliver and verify.
Unknowns
If a Slice's true size is not yet knowable (e.g. failure-path coverage undetermined), say so in the accompanying PRD rather than guessing a size.json number — an inflated or deflated size number corrupts every roadmap forecast downstream.
Minimal worked example
{ "id": "SLC-0004", "name": "Order placement", "workstream": "WS-0001", "context": "CTX-0001",
"oracle_strategy": "characterization", "behaviors": ["BHV-0011", "BHV-0012", "BHV-0042"],
"state": "Outlined" }{ "slice": "SLC-0004", "behaviors": 3, "failure_path_behaviors": 1,
"interfaces_sync": 1, "interfaces_async": 1, "divergences_open": 0,
"consumers_affected": 2, "data_migration_required": false }Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

