phase3-investigate SKILL.md skillA
phase3-investigate from radekamirko/c.r.i.s.p is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add radekamirko/c.r.i.s.p/phase3-investigate@git:20260423.24fa8e6Pins git:20260423.24fa8e6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- radekamirko/c.r.i.s.p
- Path
.claude/skills/phase3-investigate/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260423.24fa8e6, committed Apr 23, 2026
- First version recorded
- Apr 16, 2026
- Size
- 23,071 bytes
- Repository stars
- 52
- License
- MIT
The Mileva Method (CRISP) — Phase 3: Investigate. Process mapping for existing or greenfield processes, user journey mapping, UX discovery, project goals, system architecture (integration map + data flow). Use after outcome alignment. Triggers on "investigate", "phase 3", "map the process", "process mapping", "user journey", "as-is process", or after Phase R exit checklist is complete.
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
## 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. --- # I — Investigate: Process Understanding Map what exists (or what should exist) before designing a solution. ## Project State > At the start of Phase I: read `docs/crisp-state.json`. Check phases C and R are complete. Use `project.type`, `phases.R.hitlZones`, `phases.R.stakeholders` for context. > > At the end of Phase I (before exit checklist): update `docs/crisp-state.json`: > - Set `phases.current` to `"S"` > - Add `"I"` to `phases.complete` > - Set `phases.I.complete` to `true` > - Fill `phases.I.processTrack`, `phases.I.userTypes`, `phases.I.dataMappingRequired`, `phases.I.uxDiscoveryRequired`, `phases.I.navigationPattern` > - Add any unresolved items to `phases.I.openQuestions` ## Two Tracks …
Read the whole file at its exact version.
How to install
mdr add radekamirko/c.r.i.s.p/phase3-investigate@sha256:affb996a2eb835b8The line at the top of this page pins the label git:20260423.24fa8e6, 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_6yz7rk4mpslw7mon)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 16, 2026 and Apr 23, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260423.24fa8e6 latest | 2026-04-23 | 24fa8e6 | 23,071 B | A | view · diff |
| git:20260422.363b7cf | 2026-04-22 | 363b7cf | 22,578 B | A | view · diff |
| git:20260417.5da48f5 | 2026-04-17 | 5da48f5 | 18,546 B | A | view · diff |
| git:20260416.5c6d9c7 | 2026-04-16 | 5c6d9c7 | 17,960 B | A | view · diff |
| git:20260416.6bd4bae | 2026-04-16 | 6bd4bae | 17,377 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 (23071 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_6yz7rk4mpslw7mon GET https://markdownregistry.com/api/v1/resolve?ref=radekamirko/c.r.i.s.p/phase3-investigate GET https://markdownregistry.com/api/v1/blob/affb996a2eb835b8e45427186552f08425b936c03feb2c46f8cb3bd3a568d747
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.