Skill

tour

Provides interactive onboarding tour of repository architecture, tech stack, guardrails, and Context-Driven Development patterns through developer challenges and questions.

documentation

developer-tools

npx claudepluginhub mayurpise/draft --plugin draft

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Provide an interactive codebase walk-through based on existing architecture and guardrail constraints.

SKILL.md

Similar Skills

code-tour

29.8k

Creates CodeTour .tour files for persona-targeted, step-by-step walkthroughs linking to files and line numbers. Supports 20 personas, all step types, for onboarding, PR reviews, bug tours, architecture overviews.

4 files

awesome-copilot-refactor

code-tour

173.8k

Creates persona-targeted CodeTour .tour files with real file and line anchors for step-by-step codebase walkthroughs. For onboarding, architecture, PR reviews, RCA, and feature explanations.

everything-claude-code

onboard

242

Guides new developers through structured codebase onboarding across five stages: big picture, core domain, interfaces, patterns, and hardening. Tracks progress with challenges and mastery checks.

gauntlet

Stats

Stars33

Forks3

Last CommitApr 26, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Draft Tour: Interactive Onboarding

Provide an interactive codebase walk-through based on existing architecture and guardrail constraints.

Red Flags - STOP if you're:

Dumping the entire architecture.md into the chat window.

Giving answers to foundational pattern questions before prompting the developer to guess.

Explaining code the developer hasn't explicitly asked to view yet.

Execution Constraints

Load Context: Read draft/architecture.md, draft/tech-stack.md, and draft/guardrails.md.

Interactive Cadence: Ask the developer if they are familiar with the tech stack constraints found in draft/tech-stack.md.

Module Introduction: Instead of listing all modules, introduce the "Entry Point" module first.

Active Challenge: After explaining a module's responsibility, challenge the developer: "Based on our Context-Driven Development rules, how do you think we handle data persistence here?" Wait for their answer before revealing the architecture strategy.

Traceability: Highlight draft/.state/facts.json showing how module constraints have evolved.

Completion: Guide the developer to create their first test track using /draft:new-track so they understand the artifact loop.

Draft Tour: Interactive Onboarding

Provide an interactive codebase walk-through based on existing architecture and guardrail constraints.

Red Flags - STOP if you're:

Dumping the entire architecture.md into the chat window.
Giving answers to foundational pattern questions before prompting the developer to guess.
Explaining code the developer hasn't explicitly asked to view yet.

Execution Constraints

Load Context: Read draft/architecture.md, draft/tech-stack.md, and draft/guardrails.md.
Interactive Cadence: Ask the developer if they are familiar with the tech stack constraints found in draft/tech-stack.md.
Module Introduction: Instead of listing all modules, introduce the "Entry Point" module first.
Active Challenge: After explaining a module's responsibility, challenge the developer: "Based on our Context-Driven Development rules, how do you think we handle data persistence here?" Wait for their answer before revealing the architecture strategy.
Traceability: Highlight draft/.state/facts.json showing how module constraints have evolved.
Completion: Guide the developer to create their first test track using /draft:new-track so they understand the artifact loop.