Skip to content
Skills Library
Science & research · Analysis

slo-pattern

/slo-pattern

Use this skill after /slo-play has filled §4, to fill §5 Pattern Catalog — turn raw play into named reusable mechanisms (a vocabulary of tricks). Mode is convergent. Cite probe IDs for every pattern, run the next-curve check and the DICEE check, and narrow to at most five serious candidates. Do NOT promote everything. Hands off to /slo-precision.

Licence
MIT
Last repository change
26.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use this skill after /slo-play has filled §4, to fill §5 Pattern Catalog — turn raw play into named reusable mechanisms (a vocabulary of tricks). Mode is convergent. Cite probe IDs for every pattern, run the next-curve check and the DICEE check, and narrow to at most five serious candidates. Do NOT promote everything. Hands off to /slo-precision.

Original author description

Use this skill after /slo-play has filled §4, to fill §5 Pattern Catalog — turn raw play into named reusable mechanisms (a vocabulary of tricks). Mode is convergent. Cite probe IDs for every pattern, run the next-curve check and the DICEE check, and narrow to at most five serious candidates. Do NOT promote everything. Hands off to /slo-precision.

How it works

  1. Inputs
  2. Output
  3. Method — fill §5, opening with the Phase Contract (Mode: convergent)
  4. Gate
  5. Handoff
  6. Anti-patterns
Original SKILL.md headings · 51 lines, 298 words
SKILL.md preview
---
name: slo-pattern
description: >
  Use this skill after /slo-play has filled §4, to fill §5 Pattern Catalog — turn
  raw play into named reusable mechanisms (a vocabulary of tricks). Mode is
  convergent. Cite probe IDs for every pattern, run the next-curve check and the
  DICEE check, and narrow to at most five serious candidates. Do NOT promote
  everything. Hands off to /slo-precision.
---

# /slo-pattern — name the reusable tricks

The play log is full of raw probes. Your job is to name the reusable mechanisms
hiding in them — the "vocabulary of tricks" — and narrow the field enough to
measure. Mode: **convergent** (judge reusability).

## Inputs

- `docs/slo/experiments/<slug>/EXPERIMENT.md` — §4 Play Log (probe ledger, dead-ends).
- The binding spec `docs/slo/design/innovation-loop-experiment-book-spec.md` (§5 body).

## Output

Fill **§5 Pattern Catalog** of the Experiment Book. Produces `PatternCatalog`
(+ NextCurveCandidates, ProductPull, ArchitecturePull).

## Method — fill §5, opening with the Phase Contract (Mode: convergent)

1. **Pattern candidates** table: name, mechanism, **probe evidence (cite probe
   IDs)**, why surprising, reuse cases, risks. **Cite probe IDs for every
   pattern** — a pattern with no probe evidence is rejected.
2. **Cap: at most five serious candidates** (≤5). If play produced more, narrow.
3. **Next-Curve check**: for each pattern, is it a 10% improvement or a
   category change? (Kawasaki's "jump to the next curve".)
4. **DICEE check**: Deep / Intelligent / Complete / Empowering / Elegant.
5. **Sunlit strategic fit**: B2C / B2B / secure-data / cybersecurity.
6. **Product pull** + **Architecture pull**: which patterns suggest a user-facing
   wedge vs. a reusable platform capability.
7. Update the §1 tracker (phase 3 `complete`), append a Safety Check, hand off.

## Gate

Do not proceed with more than five serious candidates, and never with a pattern
that cites no probe ID. The output should narrow the field enough to measure.

## Handoff

Suggest **`/slo-precision <slug>`** — make the surviving claims measurable.

## Anti-patterns

- Promoting everything (the cap exists to force a choice).
- Naming a pattern with no probe evidence (cite probe IDs).
- Confusing a 10% improvement with a next-curve move — the next-curve check
  exists to keep that honest.

---

**Loops**: Innovation Sandbox loop — see [docs/LOOPS-ENGINEERING.md#innovation-sandbox-loop](../../docs/LOOPS-ENGINEERING.md#innovation-sandbox-loop).

Versions

The database has no other skills named slo-pattern.

Database snapshot: 13.11.2026 · package version 115c3cbfa359 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90slo-play
    Use this skill after /slo-sandbox has filled §3, to fill §4 Play Log — generate many raw probes from the sandbox's probe seeds WITHOUT premature judgment. Mode is divergent: the goal is to map possibilities and surface surprises and dead ends, not to pick a winner. This is the…
  • 90slo-precision
    Use this skill after /slo-pattern has filled §5, to fill §6 Precision Model — make the invisible measurable. Mode is measurement. Convert each promising pattern into a falsifiable claim with a measurement handle, an accept threshold AND a kill threshold, resource bounds,…
  • 90slo-implementation
    Plan, implement, or review slo implementation work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests slo implementation work.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.