implement SKILL.md skillA
implement from rsmdt/the-startup is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rsmdt/the-startup/implement@git:20261026.9ddf98dPins git:20261026.9ddf98d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rsmdt/the-startup
- Path
plugins/start/skills/implement/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261026.9ddf98d, committed Oct 26, 2026
- First version recorded
- Oct 26, 2026
- Size
- 8,574 bytes
- Repository stars
- 577
- License
- MIT
Implementation entry point. Use to execute a completed specification. Reads the spec's slice and scenario tasks from the tracker, then runs a dynamic workflow that builds each phase's slices and evaluates the phase through a barriered code→eval retry loop until every slice's holdout scenarios pass the threshold.
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
## Persona Act as the implementation orchestrator. You resolve the spec, gather everything the build loop needs, then author and run **one dynamic workflow** (the Workflow tool with an inline script you write) that builds every slice. You do **not** write product code and you do **not** hand-run the loop — the workflow holds the loop, the branching, and the retries as code. Everything is a task (`task.js`). Each plan phase is a root **phase** task with **slice** child tasks (each body is a code brief) and, under each slice, **scenario** child tasks (the holdout acceptance evidence). specify-plan authors them; you read their structure. **Implementation Target**: $ARGUMENTS ## Constraints **Always:** - Resolve the spec via the specify-meta skill; read the task graph with `task.js graph`. - Read task **structure only** — ids, `dependsOn`, scenario counts. Never open a slice or scenario body yourself: you write every agent's prompt, so whatever you read can leak across the barrier. - Preserve the information barrier inside the workflow: the code agent reads only its **slice** task; the eval agent reads only that slice's **scenario** child tasks. …
Read the whole file at its exact version.
How to install
mdr add rsmdt/the-startup/implement@sha256:c3187dfc1115289cThe line at the top of this page pins the label git:20261026.9ddf98d, 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_wbr3gg7jwkg5ep6b)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, all committed on Oct 26, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.9ddf98d latest | 2026-10-26 | 9ddf98d | 8,574 B | A | view · diff |
| git:20261026.1fa3434 | 2026-10-26 | 1fa3434 | 8,712 B | A | view · diff |
| git:20261026.2c8aabe | 2026-10-26 | 2c8aabe | 8,516 B | A | view · diff |
| git:20261026.a50780e | 2026-10-26 | a50780e | 8,454 B | A | view · diff |
| git:20261026.024721f | 2026-10-26 | 024721f | 7,668 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 (8574 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
rsmdt/the-startup · 577 stars · license MIT · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wbr3gg7jwkg5ep6b GET https://markdownregistry.com/api/v1/resolve?ref=rsmdt/the-startup/implement GET https://markdownregistry.com/api/v1/blob/c3187dfc1115289c05820b0b0a3894ceed5a5a628aeedfde4c46041b835c4558
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.
More from rsmdt/the-startup
Every file in rsmdt/the-startup