jcosta33/skills

drill

Lock one change from language through obligation, place, and slice before writing. ALWAYS use when those levels mix, implementation starts before place is locked, or a lower question fires while a higher lock is open. Do not use for a checked staged transformation.

First seen Aug 20, 2026

Installation

$ npx skills add jcosta33/skills --skill drill

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from jcosta33/skills · top by installs.

npx skills add jcosta33/skills

Browse all from jcosta33/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,637 B
  • docs SUMMARY.md 278 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 7 installs

SKILL.md

Drill

Lock the next seam. Write only that seam.

Method

Work one level at a time. A higher lock that moves drops the in-flight slice.

  1. Language. Name the thing in the project's words. Stop until the name is shared.
  2. Obligation. Name what the slice guarantees: the behavior a caller can now rely on, and what

must stay true that already was. Then verify-with and rollback for each. Machinery is not implied by the guarantee. Do not open a staged transformation artifact.

  1. Place. Name the files, symbols, and runtime boundary. When coupling is unproven, trace the

path to closure first.

  1. Slice. Name the smallest write that keeps the obligation. Reuse first: search for the

existing rule and call it. Duplicate only with a named reason, and proximity is not a reason. Do not extract a wrapper that restates an existing operation. Then write it.

Prove discoverable technical questions from evidence. Structure remaining human-owned locks as explicit choices. Do not ask a lower question while a higher lock is open.

Escalate when ordered waves plus rollback must outlive the session.

Native notes only. No CONTEXT.md. No Suspec artifact.

Output

Return the four locks, the write, and the verify evidence as rendered Markdown. Keep evidence to the smallest untouched decisive excerpt.