feature-init skillA
feature-init is agent-read markdown (skill) from swingerman/engineer: Use when a new feature folder must be created for the DAE pipeline, or when discuss promotes/parks an idea. Triggers — "/engineer.feature-init", "create a feature", "start a new feature", "init a feature"..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# feature-init Create a feature folder for the DAE pipeline — `feature.md` (the Ready contract), the folder, a branch, and a tracker entry. Checkpoint 1.5. ## When to use Five paths: - **From `discuss`** — receives a `feature_intake` payload in context (park or promote outcome). No interview. - **Standalone** — no payload; run the intake interview. - **From a tracker capture** — promoting an untriaged row a human added directly to the tracker (no `Slug`; see *Tracker-as-intake* in `references/tracker.md`). Pre-fill intake from the row (its title → `title`/`outcome`, `Type`, any notes); confirm the rest. Reuse the row — don't create a new one (Step 9). - **From a roadmap item** — promoting a strategic roadmap item (status `planned`) into a feature (typically from `next`'s ON THE ROADMAP bucket, or `discuss`). Pre-fill intake from the item (`title`, `area`, `notes`). Signalled by a `roadmap_ref` (the item `id`) passed in — carry it onto `feature.md` and mark the item in-progress (Step 9). See *the roadmap ↔ feature funnel* in `references/roadmap.md`. …
Read the whole file at its exact version.
How to install
mdr add swingerman/engineer/feature-init@git:20260922.ccea2d9mdr add swingerman/engineer/feature-init@sha256:b0b1285437d6142fPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_zbiegs5eogzmum4i)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.ccea2d9 latest | 2026-09-22 | ccea2d9 | 10,368 B | A | view · diff |
| git:20260916.7c916c4 | 2026-09-16 | 7c916c4 | 9,368 B | A | view · diff |
| git:20260903.f661a4f | 2026-09-03 | f661a4f | 9,111 B | A | view · diff |
| git:20260826.e7447cd | 2026-08-26 | e7447cd | 8,920 B | A | view · diff |
| git:20260823.7f6ca14 | 2026-08-23 | 7f6ca14 | 8,542 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 (10368 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
swingerman/engineer · 150 stars · license MIT · pushed 2026-09-22 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_zbiegs5eogzmum4i GET https://markdownregistry.com/api/v1/resolve?ref=swingerman/engineer/feature-init GET https://markdownregistry.com/api/v1/blob/b0b1285437d6142f5de991a5c1d0fbe766a7924f1f0a4757f855ca64b0a74a5b
Your agent 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.