routinize

Solid

Codify a recurring work pattern into a durable practice ("관행화"). Invoke when the same task pattern has recurred and should stop being re-remembered by hand — automatically when you notice a repeat, or explicitly via /routinize. Prime trigger — before-compact time, when the session's accumulated context (the raw material) is about to be compacted away. Follows Greatpractice's capture-eager / promote-deferred discipline (Greatpractice.md §5.4): captures the pattern to memory immediately, but never auto-ratifies a blocking practice — promotion to an enforced entry is user-gated. Skips phronesis-heavy work (judgement-heavy / rare-context) by design.

AI & Automation 7 stars 0 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 78/100

Stars 20%
30
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# /routinize — codify a recurring practice (관행화) Turn "work I keep doing the same way" into a durable Greatpractice entry — without over-codifying. This is the model-invoked front door to Greatpractice's **capture → mature → codify** pipeline (Greatpractice.md §1.2). The full normative model — tiers, maturity score, notability gate, phronesis boundary — lives in `Greatpractice.md`; this skill is the actionable procedure, not a restatement. **Core discipline — capture is immediate, promotion is deferred** (§5.4). A single session's repetition is usually the *same* trigger coordinate (§5.2), so most invocations end at capture/accumulate; only genuinely independent recurrence produces a draft. The skill never registers an enforcing hook on its own authority — that is a user decision. ## Procedure 1. **Scan for recurrence** — over the recent context, find work patterns that repeated: the same fix applied ≥2×, the same multi-step sequence run again, a "when X, also do Y" coupling, a mistake made → corrected → nearly repeated. Name each candidate pattern in one line. 2. **Phronesis gate — what NOT to codify** (§1.4 / §5.3). Drop any candidate that is *judgement-heavy* (outcome doesn't reduce to one metric), *rare-context* (long-tail work phase), or *high-context-dependent* (the same surface behavior means different things by context). These stay in the agent's instinct — codifying them causes phronesis atrophy. Keep a borderline-but-worth-capturing candidate, but mark `phrones...

Details

Author
SoliEstre
Repository
SoliEstre/EstreGenesis
Created
2 months ago
Last Updated
today
Language
JavaScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

skill-capture

Turn a recurring in-session workflow into a reusable Claude Code skill. Load this the moment you notice you have run the SAME multi-step sequence (same ordered steps or commands, small variation allowed) about three times in the current session, or when open candidates are waiting in .credo/skill-candidates.md at session start or resume. It is heuristic and in-session only - no persistent counter, no tracking backend. Mode-gated like the audit nit-disposition policy: autonomous mode NEVER builds a skill (it only appends a candidate note and keeps working), active / passive / default propose the capture via the Ask tool and build only on an explicit GO. Applies inside subagents too, where the safest branch (autonomous: candidate note only, never ask, never build) is the default whenever the mode cannot be determined.

13 Updated 4 days ago
Marcel-Bich
AI & Automation Listed

pattern-retrospective

Apply rigorous pattern-retrospective analysis to Claude transcripts. Triggers on writing studies, blog posts, handoff docs, retrospectives, specs, or improvement proposals that draw conclusions from past Claude sessions — phrasings like "handoff to X", "lessons from session Y", "pattern Z over time", "spec for X", "improvements to X", "audit my use of W" all match. Enforces target-system audit BEFORE specifying its requirements, streaming JSONL parsing (never load whole files), 5-tuple extraction with provenance tags, self-falsification of every cited claim including system-state claims, Bayesian confidence smoothing, and correlation-not-causation discipline. Designed to prevent the credulous-handoff failure mode where ~60% of proposed requirements turn out to already exist in the target system.

0 Updated today
BryceEWatson
AI & Automation Solid

codify

Sweep the project's LEARNINGS.md inbox and turn accumulated entries into durable skill, rule, or documentation changes. Run when ready to process learnings — not mid-task.

8 Updated 1 weeks ago
isvlasov