wize-check-implementation-readiness skillA
wize-check-implementation-readiness is agent-read markdown (skill) from qwize-br/wize-development-kit: 3-solutioning: Check Implementation Readiness.
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
# Check Implementation Readiness
# Check Implementation Readiness
**Goal.** Before any story enters dev, confirm everything is in place. This is the **gate at the end of Phase 3**. Cheap; saves multiples of itself downstream.
Tony chairs. Hill and Hawkeye sign off. Pepper and Mantis answer if pulled in.
## Inputs
- `.wize/planning/prd.md` (validated)
- `.wize/planning/ux/ux-design/` + `index.md`
- `.wize/planning/tech-vision.md`
- `.wize/planning/nfr-principles.md`
- `.wize/solutioning/architecture.md`
- `.wize/solutioning/adrs/`
- `.wize/solutioning/design-system/`
- `.wize/solutioning/epics/` + `stories/`
- `.wize/implementation/tea/risk-profile.md` (Hawkeye)
- `.wize/config/tea.toml` (policy choice)
## Outputs
- `.wize/solutioning/readiness-{YYYY-MM-DD}.md` — checklist result + signoffs.
## Checklist (Tony chairs)
### Planning artifacts
- [ ] PRD `status: validated`.
- [ ] All open questions in PRD resolved (no `blocker` open).
- [ ] Trigger map covers every PRD goal.
### UX
- [ ] Every In-scope item has at least one screen spec.
- [ ] UX design index maps every screen → scenario → AC.
- [ ] Design system tokens + components needed by the UX exist.
### Strategy
…Read the whole file at its exact version.
How to install
mdr add qwize-br/wize-development-kit/wize-check-implementation-readiness@git:20260613.a8c0f41mdr add qwize-br/wize-development-kit/wize-check-implementation-readiness@sha256:63e048e56be048b9Pin 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_quvsukpcrrkkvw5h)
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 (3383 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
qwize-br/wize-development-kit · 16 stars · license NOASSERTION · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_quvsukpcrrkkvw5h GET https://markdownregistry.com/api/v1/resolve?ref=qwize-br/wize-development-kit/wize-check-implementation-readiness GET https://markdownregistry.com/api/v1/blob/63e048e56be048b9bdb60fa73fb8848270f270eb546be557c40aa01946a4c12e
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.
More from qwize-br/wize-development-kit
Every file in qwize-br/wize-development-kit