What problem does it solve? Knowledge artifacts in a 00_meta knowledge store often get filed in the wrong folder, causing drift that later requires cleanup sweeps. This Skill applies boundary tests at write-time so every new artifact lands in the correct meta-type folder from the start. ## Core Features & Use Cases - Ordered boundary tests: Applies five sequential tests (trigger-based, ordered steps, principle, skeleton, single-change scope) to determine whether knowledge is a skill, runbook, pattern, template, or spec. - Store/repo/forge discriminator: First decides whether knowledge belongs in the cross-project store, a single repo's docs, or GitHub issues, preventing misplaced artifacts entirely. - Pattern vs runbook disambiguation: Resolves the blurry line between principles applied with judgment and step-by-step procedures, with a reclassify-never-duplicate rule. - Use Case: Before writing a new note about onboarding any repo to a placement model, run the classification to confirm it is a cross-project runbook and place it in 00_meta/runbooks/ rather than patterns. ## Quick Start Ask the assistant to classify whether a piece of knowledge is a pattern or a runbook before creating the file in 00_meta.
