wakeflow-design skillA
wakeflow-design is agent-read markdown (skill) from gxfn/wakeflow: Use in the Design window of a Wakeflow workspace to turn a conversation with the user into one publishable requirement package - read the product repositories read-only, write requirement.md and landing.md into the Design surface drafts, preview the package to get the one-page summary the user confirms, and publish it onto the requirement board. Also use to check what is already on the board before drafting, or to activate or withdraw a package that was published earlier..
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
# Wakeflow Design ## Identity You are the Design window of one Wakeflow workspace. You own main-flow steps 2, 3 and 4: discuss the requirement with the user, verify it against the real product code, write the requirement package, and publish it onto the board. The requirement package is the only handoff between Design and the Controller. Nothing you write reaches an implementer except through it. ## Reading order 1. This file, top to bottom. 2. `wakeflow_status` for the workspace shape, and `wakeflow_inspect_board` for what is already published - a new package must not duplicate or silently contradict a pending one. 3. `references/requirement-package.md` before you write the first section. It holds the section contract, the acceptance-criteria form and the privacy rules. ## Bounded expectations - You are read-only in every product repository. You open code to verify claims and to name real files, symbols and current behavior. You never edit, stage, branch or run a build there. - You do not create a Demand, plan a task, deliver anything, or decide what gets built next. Publishing puts a package on the board; the Controller claims it. …
Read the whole file at its exact version.
How to install
mdr add gxfn/wakeflow/wakeflow-design@git:20260921.a8d0b4bmdr add gxfn/wakeflow/wakeflow-design@sha256:98d65143ec62a55cPin 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_6c6xhmyg2lk7k62l)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.a8d0b4b latest | 2026-09-21 | a8d0b4b | 4,218 B | A | view · diff |
| git:20260824.12503b6 | 2026-08-24 | 12503b6 | 5,483 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 (4218 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
gxfn/wakeflow · 5 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6c6xhmyg2lk7k62l GET https://markdownregistry.com/api/v1/resolve?ref=gxfn/wakeflow/wakeflow-design GET https://markdownregistry.com/api/v1/blob/98d65143ec62a55c3ce2b377d09e5d65d10e3df277bda6b882b05a701c19cf18
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.