Display Name
C.R.I.S.P
Category
Workflows & Knowledge Guides
Sub-Category
General
Primary Link
https://github.com/radekamirko/C.R.I.S.P
Author Name
radekamirko
Author Link
https://github.com/radekamirko
License
MIT
Other License
No response
Description
BA/PM process with 5 phases for AI developers. Guides a loose client brief through problem definition, stakeholder identification, process analysis, and sprint ready specification development to create a brief that is so precise that there’s nothing for Claude Code to hallucinate about. It was designed for the space between vibe coding and creating something worthwhile.
Validate Claims
Clone the repository. Move the .claude/skills folder to any Claude Code project. Start Claude Code. Look at phase1-clarify/SKILL.md. Conduct a discovery on your choice of application. Once you complete Phase 1, go to problem-statement.md. It is a well-formatted file created from your responses, not from Claude’s imagination.
Specific Task(s)
Apply the CRISP methodology to define an easy application (such as a personal expense management application). Complete all the stages from one to four. Determine whether the result (specifications generated by the AI model) can be passed to Claude Code so it can start development right away.
Specific Prompt(s)
Claude Code, inside a blank project folder: "I wish to develop an expense tracker for myself. Begin with CRISP Phase 1: Clarify." Go through each step carefully. Do not omit the exit checklist. After completing Phase 4, read the AI specification and ask yourself, "Would I give this to a developer?"
Additional Comments
The CRISP process evolved from actual discovery meetings where the developers were going straight to implementation without going through the BA/PM phase and creating the wrong application. This has been tested on various projects prior to its release. The examples/ directory has the completed documents used in an actual project deployment, not just demo documents. Submitted as #1248 and closed pending one week cooldown.
Recommendation Checklist
Display Name
C.R.I.S.P
Category
Workflows & Knowledge Guides
Sub-Category
General
Primary Link
https://github.com/radekamirko/C.R.I.S.P
Author Name
radekamirko
Author Link
https://github.com/radekamirko
License
MIT
Other License
No response
Description
BA/PM process with 5 phases for AI developers. Guides a loose client brief through problem definition, stakeholder identification, process analysis, and sprint ready specification development to create a brief that is so precise that there’s nothing for Claude Code to hallucinate about. It was designed for the space between vibe coding and creating something worthwhile.
Validate Claims
Clone the repository. Move the .claude/skills folder to any Claude Code project. Start Claude Code. Look at phase1-clarify/SKILL.md. Conduct a discovery on your choice of application. Once you complete Phase 1, go to problem-statement.md. It is a well-formatted file created from your responses, not from Claude’s imagination.
Specific Task(s)
Apply the CRISP methodology to define an easy application (such as a personal expense management application). Complete all the stages from one to four. Determine whether the result (specifications generated by the AI model) can be passed to Claude Code so it can start development right away.
Specific Prompt(s)
Claude Code, inside a blank project folder: "I wish to develop an expense tracker for myself. Begin with CRISP Phase 1: Clarify." Go through each step carefully. Do not omit the exit checklist. After completing Phase 4, read the AI specification and ask yourself, "Would I give this to a developer?"
Additional Comments
The CRISP process evolved from actual discovery meetings where the developers were going straight to implementation without going through the BA/PM phase and creating the wrong application. This has been tested on various projects prior to its release. The examples/ directory has the completed documents used in an actual project deployment, not just demo documents. Submitted as #1248 and closed pending one week cooldown.
Recommendation Checklist