t4-dev-workflow SKILL.md skillA
t4-dev-workflow from xenodeve/xeno-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add xenodeve/xeno-skills/t4-dev-workflow@git:20260820.0baca5ePins git:20260820.0baca5e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- xenodeve/xeno-skills
- Path
skills/t4/t4-dev-workflow/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260820.0baca5e, committed Aug 20, 2026
- First version recorded
- Aug 19, 2026
- Size
- 47,014 bytes
- Repository stars
- 2
- License
- MIT
Use when planning or implementing a feature/change in a T4-team repo (T4 Labs / Slow-Inc) — deciding how to go from idea to shipped code, filing or updating a GitHub issue or PRD, writing a bilingual (Thai + English) issue/PR body, opening a PR, or closing an issue. Covers the grill→PRD→issues→TDD pipeline, the PRD→issues→PR gate, the auto-triggered skill map, triage labels, and the issue lifecycle. Triggers include "let's build X", "file an issue for this", "write the PRD", "open a PR…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# T4 Dev Workflow ## Overview The T4 team's development pipeline, built for an **agent-primary** repo where GitHub issues are the source of truth for *what to do* and *its state* — not a formality. Session-local todos must reconcile back to issues before the session ends. This skill covers how work flows from idea to merge, which skills fire automatically, and the tracker conventions (labels, lifecycle, bilingual bodies). ## The pipeline When planning or implementing a feature, follow this order: 1. **`/grill-me`** — stress-test the concept interview-style before committing to it. 2. **`/grill-with-docs`** — challenge the plan against existing ADRs in `docs/adr/`; this also lazily produces domain docs (`CONTEXT.md` / ADRs) when a term or decision actually resolves. 3. **Survey the change sites** — enumerate *every* place the change touches **before** writing the plan (below). A PRD written without this plans the change you imagined, not the one the repo needs. 4. **`/to-prd`** — turn the grilled plan into a PRD (one PRD per epic), carrying the survey as its change inventory. 5. **`/to-issues`** — break the PRD into GitHub issues with triage labels (one issue per deliverable). …
Read the whole file at its exact version.
How to install
mdr add xenodeve/xeno-skills/t4-dev-workflow@sha256:8ef60e3886123703The line at the top of this page pins the label git:20260820.0baca5e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_q6r42gzlkgrqb4dp)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 19, 2026 and Aug 20, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260820.0baca5e latest | 2026-08-20 | 0baca5e | 47,014 B | A | view · diff |
| git:20260820.aa0b751 | 2026-08-20 | aa0b751 | 43,535 B | A | view · diff |
| git:20260819.1271f55 | 2026-08-19 | 1271f55 | 42,120 B | A | view · diff |
| git:20260819.473f945 | 2026-08-19 | 473f945 | 40,366 B | A | view · diff |
| git:20260819.39a8875 | 2026-08-19 | 39a8875 | 38,428 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (47014 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
xenodeve/xeno-skills · 2 stars · license MIT · pushed 2026-10-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_q6r42gzlkgrqb4dp GET https://markdownregistry.com/api/v1/resolve?ref=xenodeve/xeno-skills/t4-dev-workflow GET https://markdownregistry.com/api/v1/blob/8ef60e38861237033aa71d4c95fed7e2cb58abab5dd9d81d156a713d7e188248
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.