pitroom-driven-development SKILL.md skillA
pitroom-driven-development from atastech/pitroom is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add atastech/pitroom/pitroom-driven-development@git:20261005.b00c55ePins git:20261005.b00c55e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- atastech/pitroom
- Path
skills/pitroom-driven-development/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261005.b00c55e, committed Oct 5, 2026
- First version recorded
- Sep 30, 2026
- Size
- 11,796 bytes
- Repository stars
- 28
- License
- MIT
Use when executing a written implementation plan - each task goes to a Pitroom worker in an isolated copy, a worker on another model reviews it, and you rule, apply and commit between tasks.
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
# Pitroom-Driven Development Execute a plan by giving each task to a fresh implementer worker in an isolated copy, a task review (spec compliance and code quality) by a worker on another model after each, and a whole-branch review at the end. You are the controller: you never write a task's code yourself; you rule on conflicts, apply patches and commit. **Why workers:** each gets exactly its task (Pitroom extracts it from the plan) and none of your conversation. Their tokens are cheap and your context stays free for coordination. A reviewer on a different backend is a second model, not the implementer grading itself. **Core principle:** fresh worker per task + task review on another model + whole-branch review = high quality at worker prices. **Narration:** between tool calls, at most one short line. `pitroom plan status` and the tool results carry the record. **Continuous execution:** do not pause to check in with your human partner between tasks. The only reasons to stop are the four below, or all tasks complete. "Should I continue?" prompts waste their time: they asked you to execute the plan. …
Read the whole file at its exact version.
How to install
mdr add atastech/pitroom/pitroom-driven-development@sha256:cc2d197ee3a6199eThe line at the top of this page pins the label git:20261005.b00c55e, 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_pz5ag7dbhtu4gpfu)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 30, 2026 and Oct 5, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.b00c55e latest | 2026-10-05 | b00c55e | 11,796 B | A | view · diff |
| git:20260930.edf1281 | 2026-09-30 | edf1281 | 11,821 B | A | view · diff |
| git:20260930.b3d668b | 2026-09-30 | b3d668b | 11,749 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 (11796 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
atastech/pitroom · 28 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pz5ag7dbhtu4gpfu GET https://markdownregistry.com/api/v1/resolve?ref=atastech/pitroom/pitroom-driven-development GET https://markdownregistry.com/api/v1/blob/cc2d197ee3a6199ed29330ae93245772fa3b55ed0276a969d42da5b2b81483fc
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.