godmode-spec-lifecycle skillA
godmode-spec-lifecycle is agent-read markdown (skill) from aiimagined/godmode: Move a specification and its plan through specify, approve, implement, review, and status as one linked, resumable record instead of separate hand-authored drafts that drift apart. Use when a task needs its spec written, a plan approved before mutation, work bound back to that plan, and its status checked or reverted. Not for authoring a standalone document with no tracked contract, and never as a way to approve a plan against yourself..
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
# Godmode Spec Lifecycle ## Outcome A task's what/why, its plan's how, its approval, its bound implementation, and its status are one linked chain a later session can resume from `planmode check` - not a set of prose drafts that drift and get reconciled by hand, after the fact, in a checkpoint note. ## Use - A task needs a spec (`objective`, `outcome`, `acceptance`, `non_goals`) recorded before any plan names a how. - A plan's contract is complete and needs approval before the first edit, or its current gap list needs reading. - Work already done needs binding back to its approved plan, so drift outside the declared scope is named rather than silently allowed. - Two divergent drafts of the same spec or plan need reconciling into one linked record instead of a superseding claim added by hand later. - A stalled or abandoned plan needs its status read, or the project needs reverting to a prior verified point. ## Do Not Use - Writing a one-off prose document (a README section, a design write-up) with no plan or mutation behind it - that is ordinary authoring, not this flow. …
Read the whole file at its exact version.
How to install
mdr add aiimagined/godmode/godmode-spec-lifecycle@git:20260923.51b2535mdr add aiimagined/godmode/godmode-spec-lifecycle@sha256:2714b333f49aa36aPin 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_idlelx6vlcyir2pd)
1 badge views in 30 days
Versions
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 (6813 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
aiimagined/godmode · 6 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_idlelx6vlcyir2pd GET https://markdownregistry.com/api/v1/resolve?ref=aiimagined/godmode/godmode-spec-lifecycle GET https://markdownregistry.com/api/v1/blob/2714b333f49aa36a23336ffda21d40c4101b24f6cfa53ce55f4ef2fefa7aec95
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.