ot-intent

Installation
SKILL.md
  1. Listen to the request in the user's own words. Do not write spec.md. Highway implementation waits for approved spec.md and tasks.md; operational and Express parts follow step 2.

  2. Classify each request, splitting compound requests into parts before allocating anything; handle each part in its own lane. The user's explicit choice wins in both directions: naming ot-intent or asking for a track or intent selects the Highway for an edit; asking to do it directly or without a track selects the Express lane.

    • Operational: running, building, installing, inspecting, or reporting without editing a versioned target-repo file. Execute directly, with no track or artifact; never record it inside a track, including an assets/ note.
    • Express: all five criteria hold: (1) the request states what to build, with no open question that changes it; (2) the change is the smallest that serves the request as stated, one concern with at most three distinct edits, where the same edit repeated across files (a rename, a version string, a mirrored translation) counts once; (3) no public contract (API, CLI flags, schema, consumed file format), persisted data or migration, security control (authentication, authorization, secrets, permissions), or dependency (add, upgrade, remove) changes; (4) reverting the diff alone undoes it, with no data backfill or external side effect; (5) one existing command or one observable check verifies it. Say in one sentence that the change takes the Express lane, implement, run the check, write a crumb, and report the change and result. Apart from the crumb, create no track or file under on-track/ and do not regenerate the index. The crumb is the note for the maintainer's commit; the method never commits on its own. If a criterion stops holding, stop before the edit that breaks it, name the failed criterion, and start the Highway with ot-intent. The sole artifact exception is an ADR qualifying under step 6: file only that ADR and regenerate the index.
    • Highway: every other edit, and any edit where criterion 1, 3, 4, or 5 is uncertain. Doubt about criterion 2 alone keeps the edit on the Express lane, under its stop rule. The Highway runs intent, spec, implement, and ship, and is the default.
    • Research-only / assessment-only: route to ot-research / ot-assess without a track.

    Crumb: the local note an Express change leaves for whoever prepares the commit. Write it after the check, pass or fail, at on-track/crumbs/<YYYY-MM-DD-HHMMSSZ>-<slug>.md, timestamp in UTC. Frontmatter: created (UTC, ISO 8601) and files (a YAML block list, one path per line: every path the change touched, a filed ADR included). Body: ## Request (what the user asked, in one or two sentences), ## Cause (fixes only: the cause found), ## Changes (one line per file), ## Verification (the command or observation and its result). Crumbs stay out of git and out of the index: when on-track/crumbs/.gitignore is missing, create it holding the single line *. To undo an Express change, reverse your own edits hunk by hunk, so the user's uncommitted work in the same files survives, and delete its crumb. When preparing commits, read the crumbs oldest first, group the diff by each crumb's files and Changes, write the message from its Request and Cause, then delete every crumb you consumed and every crumb whose files no longer differ from HEAD.

Installs
11
First Seen
7 days ago