drink-from-the-firehose

Guides role-aware onboarding walkthroughs of a codebase with sourced claims and quizzes.

9|1|Updated Aug 28, 2026
One-click install
npx skills add https://github.com/RisorseArtificiali/skills --skill drink-from-the-firehose-risorseartificiali
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: drink-from-the-firehose
Source: https://github.com/RisorseArtificiali/skills/tree/main/skills/drink-from-the-firehose
Command: npx skills add https://github.com/RisorseArtificiali/skills --skill drink-from-the-firehose-risorseartificiali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Newcomers to a large project face an overwhelming amount of code, docs, and conventions with no structured path through them. This Skill turns project onboarding into a guided, chapter-based walkthrough that adapts to each person's role and prior knowledge. ## Core Features & Use Cases - Manifest-driven chapter plan: Scans README, build files, docs trees, and entry points to build a walkthrough plan where every chapter cites a real file or doc path. - Role-aware teaching with receipts: Calibrates to developer, designer, PM, or user roles, and every factual claim carries a file:line or doc path source, with inferences explicitly labelled. - Quiz-driven adaptive pacing: Closed-question checks after each teaching chunk adjust density and difficulty, and heavy material is emitted as self-contained HTML/JS artifacts (maps, diagrams, explorers). - Use Case: A new developer joins a 50-person Java project; the walkthrough covers architecture, build and test conventions, and workflow chapter by chapter, ending with a final project map artifact linking every doc and file visited. ## Quick Start Ask the agent to walk you through this project as a newcomer, starting from the README and build files, with quizzes after each chapter.

Frequently Asked Questions about drink-from-the-firehose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I onboard a new developer to a large codebase quickly?▼

Run a guided walkthrough that scans the project's README, build files, and docs tree to build a chapter plan covering architecture, build and test, and workflow. Each chapter teaches with cited sources and checks understanding with short quizzes.

How does the walkthrough adapt to different roles like PM or designer?▼

The kickoff asks for the user's role and calibrates with questions about their actual exposure to the domain and stack. Sources then follow the role: developers get code and tests, PMs get PRDs and milestones, designers get UX surfaces.

Can the onboarding walkthrough resume after an interrupted session?▼

Yes. State lives only in the conversation as a 'Chapter N/M' progress line, so on a resumed session the walkthrough re-orients from the last announced chapter. Nothing is written to disk except emitted artifacts.

When does the walkthrough generate HTML artifacts instead of chat text?▼

Artifacts are emitted only when a chapter needs navigation, visualization, or interactivity that chat cannot provide, such as module maps, architecture diagrams, or quiz boards. Linear prose stays in chat, with at most two artifacts per chapter.

What are the limitations of a quiz-driven project walkthrough?▼

It depends on the project having discoverable docs and build files to scan; chapters with no real source file are merged or dropped. It also teaches rather than executes, so it does not replace hands-on coding practice.