workflow-development SKILL.md skillA
workflow-development from lugassawan/swe-workbench is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lugassawan/swe-workbench/workflow-development@git:20261020.b88f838Pins git:20261020.b88f838 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lugassawan/swe-workbench
- Path
skills/workflow-development/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261020.b88f838, committed Oct 20, 2026
- First version recorded
- Aug 20, 2026
- Size
- 19,435 bytes
- Repository stars
- 3
- License
- MIT
Development workflow — full lifecycle from Branch → Implement → Verify → Review → Deliver. Activated by /swe-workbench:implement, /swe-workbench:design, /swe-workbench:refactor, /swe-workbench:debug, /swe-workbench:test, /swe-workbench:architect, /swe-workbench:migrate, and /swe-workbench:document when the plan being authored modifies the codebase (Mode A) or when driving an implementation (Mode B). Entry point to execute a written implementation plan end to end — delegates to…
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
# Development Workflow Single source of truth for how development work flows. Three modes: - **Mode A (Plan Writing):** Embed an `## Evidence` section (`templates/plan-evidence-section.md`) and a `## Workflow` section (`templates/plan-workflow-section.md`) into plans - **Mode B (Implementation):** Guide step-by-step execution through all 5 phases - **Mode C (Orchestration):** Coordinate multiple parallel agents across dependency rounds — see `orchestration.md` **Announce at start:** "I'm using the development skill to [write the workflow section / guide this implementation]." ## When This Skill Activates - **Mode A:** Writing or finalizing an implementation plan (before `ExitPlanMode`) - **Mode B:** User says "implement this", "build this", "execute this plan", "run the implementation plan end to end" — any branch → code → deliver flow. For focused bug diagnosis prefer `/swe-workbench:debug` (invokes the `debugger` subagent, which composes `superpowers:systematic-debugging`); escalate here when the fix needs the full 5-phase lifecycle. <!-- validate: prose-ref --> …
Read the whole file at its exact version.
How to install
mdr add lugassawan/swe-workbench/workflow-development@sha256:0ba79c1ce859d5adThe line at the top of this page pins the label git:20261020.b88f838, 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_ytibvyfykggwfbzx)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 20, 2026 and Oct 20, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.b88f838 latest | 2026-10-20 | b88f838 | 19,435 B | A | view · diff |
| git:20261006.bf03fb1 | 2026-10-06 | bf03fb1 | 18,692 B | A | view · diff |
| git:20260828.71a6399 | 2026-08-28 | 71a6399 | 18,655 B | A | view · diff |
| git:20260823.c767d95 | 2026-08-23 | c767d95 | 18,692 B | A | view · diff |
| git:20260821.93037a7 | 2026-08-21 | 93037a7 | 18,685 B | A | view · diff |
| git:20260820.d8473ad | 2026-08-20 | d8473ad | 18,482 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 (19435 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
lugassawan/swe-workbench · 3 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ytibvyfykggwfbzx GET https://markdownregistry.com/api/v1/resolve?ref=lugassawan/swe-workbench/workflow-development GET https://markdownregistry.com/api/v1/blob/0ba79c1ce859d5addcf2bf496fbee3b22b4ac9978a63aef3a75f39c311c461bb
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.