Skip to content
Back to skills

Jt Understand

ASecurity

Reads a ticket and the code it touches before any edit, and names how each acceptance item will be seen working for real. Use when jt-work reaches the Understand step, or when the user asks what a ticket needs or how a change should be verified before coding starts.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agentsgo

Security analysis

A100/100

Scanned November 18, 2026

npx -y skills add thitinan147/jtek-skill --skill jt-understand --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jt Understand?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Jt Understand
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thitinan147-jt-understand/badge)](https://www.skillsdirectory.com/skills/thitinan147-jt-understand)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: jt-understand
description: Reads a ticket and the code it touches before any edit, and names how each acceptance item will be seen working for real. Use when jt-work reaches the Understand step, or when the user asks what a ticket needs or how a change should be verified before coding starts.
---

# jt-understand

Do this before the first edit. The output is a short list, not a document. Write it as text in the session, where the human can see it. Do not write a plan file.

## 1. Read

1. Read the ticket file whose path `jtek.py start` printed. Note `Goal`, each `Done when` item, `Out of scope`, and `kind` when it is set.
2. Read the code the ticket touches, the tests beside it, and one caller of each function you expect to change.
3. If a question can be answered by reading the code or its history, read. Do not ask the human.

## 2. Find the pattern

1. Find how this codebase already solves the same kind of problem, and plan to follow it.
2. If the nearest example is a workaround, do not copy it. Note it for the evidence.
3. Look for a function, a helper, or an installed package that already does what you need. Plan to use it.
4. If the codebase has no precedent for this kind of change, sketch two different shapes in a few lines each, and choose one. Say in the evidence which you chose and why.

## 3. Name the proof

For each `Done when` item, write one line: how you will see it work for real. A declared check counts. So does running the feature and looking at the output. "The code looks right" does not count.

An item that asks for a quality with no number or named standard ("fast", "secure", "accessible") cannot be seen working either.

If an item has no way to be seen working, stop: `jtek.py stop <id> --waiting input --note "<which item cannot be verified>"`.

## 4. Settle what the ticket leaves open

- **Small and easy to change later:** choose the reading that changes less of what users see today, even when it takes more code. Write the choice down for the evidence.
- **Costly to undo, or it changes what the ticket is for:** stop with `--waiting input` and ask one question.

## Done when

You can say, in a few lines: what will change, which existing pattern you follow, and how each `Done when` item will be seen working.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.