phase5-prove skillA
phase5-prove is agent-read markdown (skill) from radekamirko/c.r.i.s.p: The Mileva Method (CRISP) — Phase 5: Prove. Success validation against Phase R baseline metrics, test log review, and AI justification validation. Use after deployment. Triggers on "prove", "phase 5", "validate", "did it work", "success criteria", "measure results", or after go-live..
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
## Pacing Rule — One Section at a Time > Present one section, deliverable, or elicitation move at a time. > After presenting — stop. Wait for the client to respond. > Do not pre-fill and present multiple sections in one message. > Do not move to the next step until the client confirms, corrects, or gives a clear go-ahead. > > The goal is a conversation, not a document dump. > If you've written more than one section without a client response in between — you've gone too far. --- # P — Prove: Success Validation > Did the needle move? ## Project State > At the start of Phase P: read `docs/crisp-state.json`. Pull `phases.R.baseline` and `phases.R.successTarget` as the measurement baseline. Check `phases.S.sprints` to know what was built. > > At the end of Phase P: update `docs/crisp-state.json`: > - Add `"P"` to `phases.complete` > - Set `phases.P.complete` to `true` > - Set `phases.P.outcome` to `"success"`, `"partial"`, or `"fail"` > - Add summary notes to `phases.P.notes` This phase closes the loop back to Phase R. Three questions drive everything. --- ## 1. Did the needle move? Pull the baseline and targets from `docs/success-metrics.md` and measure against them: …
Read the whole file at its exact version.
How to install
mdr add radekamirko/c.r.i.s.p/phase5-prove@git:20260423.24fa8e6mdr add radekamirko/c.r.i.s.p/phase5-prove@sha256:e28a2a21b52f984dPin 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_kvs6rzmedzlb7qxq)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260423.24fa8e6 latest | 2026-04-23 | 24fa8e6 | 4,544 B | A | view · diff |
| git:20260423.96a5b2c | 2026-04-23 | 96a5b2c | 4,051 B | A | view · diff |
| git:20260417.5da48f5 | 2026-04-17 | 5da48f5 | 2,426 B | A | view · diff |
| git:20260401.c120450 | 2026-04-01 | c120450 | 1,976 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 (4544 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
radekamirko/c.r.i.s.p · 52 stars · license MIT · pushed 2026-09-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kvs6rzmedzlb7qxq GET https://markdownregistry.com/api/v1/resolve?ref=radekamirko/c.r.i.s.p/phase5-prove GET https://markdownregistry.com/api/v1/blob/e28a2a21b52f984d2d0dbf86153c4dded21217877b435dab7f68e7f810c4b860
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.