C.R.I.S.P: Skill for Claude Code

CRISP — Session Orchestrator

Before doing anything else, output this exact text verbatim:

C — Clarify · R — Results · I — Investigate S — Spec · P — Prove · E — Execute

    Outcome first. Always.

---

Step 1: Detect project state

Check if docs/crisp-state.json exists.

---

If docs/crisp-state.json does NOT exist → Ask what we're starting

Do not assume. Ask:

"Starting fresh — two quick questions:

1. Do you have an existing codebase, or are we starting from scratch?
2. What's the project?"

If starting from scratch (no existing code):

• Copy templates/crisp-state.json to docs/crisp-state.json, set mode: "discovery"
• Read .claude/skills/phase1-clarify/SKILL.md
• Begin Phase C with: "Tell me about the project — what are you trying to solve, or what did the client brief say?"
• Do not explain the methodology. Just ask.

If existing codebase (has code, no docs):

• Copy templates/crisp-state.json to docs/crisp-state.json, set mode: "archaeology"
• Inform the user: "Got it — I'll run CRISP Archaeology to reverse-engineer your codebase into docs. This requires the crisp-archaeology skill. Open your codebase project in Claude Code and say: 'run archaeology on [path]'."
• Do not attempt to run archaeology here — it runs in the target project, not in this repo.

---

If docs/crisp-state.json EXISTS → Read it and route

Read docs/crisp-state.json. Check mode first, then route.

---

Mode: "discovery" (standard CRISP phases)

1. Report current status

Project: [project.name] · Client: [project.client]
Mode: Discovery
─────────────────────────────────────────
Phases complete: [phases.complete joined with " · " — or "None"]
Current phase:   [phases.current]
─────────────────────────────────────────

Summarise the current phase state in 2–3 lines:

• Phase C: "Problem defined as [oneSentence]. Go/No-Go: [goNoGo]. Type: [type]."
• Phase R: "Baseline: [baseline]. Target: [successTarget]. [N] HITL zones defined."
• Phase I: "Process track: [processTrack]. User types: [userTypes]. Data mapping: [dataMappingRequired]."
• Phase S: "[sprintCount] sprints planned. Stack: [stack.layers summary]."
• Phase P: "Outcome: [outcome]."