radekamirko/C.R.I.S.P / .claude/skills/crisp-report
crisp-report
VerifiedGenerate a beautiful single-file HTML report from the project's docs/ folder. Works after any CRISP phase, after Archaeology, or at sprint close in Execute. Triggers on "generate report", "export docs", "create HTML report", "share docs", or automatically at sprint close in CRISP Execute.
CRISP Report Generator
Converts all markdown files in docs/ into a single self-contained HTML file — cards overview, click-through to full documents, beautiful dark theme, no dependencies.
How to run
Step 1: Check dependencies
pip3 install markdown pygments
If pip3 isn't available, try: python3 -m pip install markdown pygments
Step 2: Run the script
python3 scripts/generate-report.py [docs_dir] [output_file]
Defaults:
docs_dir→./docsoutput_file→./crisp-report.html
Examples:
# Default — reads ./docs, outputs ./crisp-report.html
python3 scripts/generate-report.py
# Custom paths
python3 scripts/generate-report.py ./docs ./reports/sprint-3-report.html
Step 3: Open
open crisp-report.html
Or share the file directly — it's fully self-contained. No server needed.
What it produces
- Overview page — card grid, one card per document, grouped by section (Discovery / Spec / Archaeology / Execute)
- Document pages — click any card → full rendered document with proper typography, code highlighting, tables
- Escape / Back → returns to overview
- Direct URL linking via
#doc-idhash — shareable links to specific docs
When to run
- End of CRISP Phase S — before handing off to Execute. Share with stakeholders for review.
- End of each sprint — updated report alongside the sprint delta doc. The stakeholder report section is already in the HTML.
- After CRISP Archaeology — share the recovered docs with the client or team.
- Any time — "generate report" at any point in a CRISP session.
Script location
scripts/generate-report.py in the project root (copied from the CRISP repo).
If the script doesn't exist in the project yet, instruct the user to copy it from the CRISP repo:
curl -o scripts/generate-report.py https://raw.githubusercontent.com/radekamirko/C.R.I.S.P/main/scripts/generate-report.py
Or copy it manually from C.R.I.S.P/scripts/generate-report.py.
Output file naming convention
| When | Suggested name |
|---|---|
| Phase S complete | crisp-report.html |
| Sprint N close | crisp-report-sprint-N.html |
| Archaeology complete | crisp-report-archaeology.html |
| Ad hoc | crisp-report.html (overwrites) |
Troubleshooting
ModuleNotFoundError: No module named 'markdown'
→ Run: pip3 install markdown pygments --break-system-packages
No markdown files found in docs/
→ Make sure you're running from the project root, or pass the correct path: python3 scripts/generate-report.py ./path/to/docs
Docs are blank or broken → Check that docs are valid UTF-8 markdown. The script skips files it can't read.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |