agentleFS
Sign inStart free
drafthqdrafthq/draft/skills/tour/SKILL.md

tour

Skill40 starsChanged 4 months agoMITView on GitHub

Interactive onboarding walkthrough for a new engineer. Use for "give me a tour", "onboard me", "walk me through the codebase".

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

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

    line 20
  2. Very specific:

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

    line 21
  3. Distinctive:

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

    line 22
  4. Distinctive:

    Active Challenge: After explaining a module's responsibility, challenge the developer: "Based on our *Context-Driven Development* rules, …

    line 23
  5. Very specific:

    If the answer is correct, confirm briefly and cite the supporting line in architecture.md / guardrails.md.

    line 24
  6. Distinctive:

    If the answer is partially right, name what they got right, then ask a narrower follow-up (e.g., "Right that we cache reads — what's the …

    line 25
  7. Distinctive:

    If the answer is wrong, do not just hand them the answer.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Load Context: Read draft/architecture.md, draft/tech-stack.md, and draft/guardrails.md.
  2. Interactive Cadence: Ask the developer if they are familiar with the tech stack constraints found in draft/tech-stack.md.
  3. Module Introduction: Instead of listing all modules, introduce the "Entry Point" module first.
  4. 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.
    • If the answer is correct, confirm briefly and cite the supporting line in architecture.md / guardrails.md.
    • If the answer is partially right, name what they got right, then ask a narrower follow-up (e.g., "Right that we cache reads — what's the invalidation trigger?") before revealing the rest.
    • If the answer is wrong, do not just hand them the answer. Quote the specific guardrail or HLD section that contradicts it, then re-prompt with a hint scoped to that section.
  5. Traceability: Highlight draft/.state/facts.json showing how module constraints have evolved.
  6. Track Lifecycle Walk: Show the full feature lifecycle and who owns each gate:
    • /draft:new-track → spec.md (requirements + classification + approvers) + plan.md (phases/tasks)
    • /draft:decompose → hld.md (always, with graph-derived diagrams) + lld.md (when --lld or High-complexity module)
    • Approvers (HLD): Technical Leads, Architecture Review Board, Cloud Operations (SaaS), QA Leads (on-prem), PM Leads
    • Approvers (LLD): Team Leads, Technical Leads, Quality Assurance
    • /draft:implement → TDD loop reading lld.md/hld.md for stub generation
    • /draft:upload → blocks git upload for high/mission-critical tracks until HLD §Approvals signed
    • /draft:deploy-checklist → blocks deploy until HLD §Checklist + LLD §Alerting Thresholds populated
    • Walk a real example track from draft/tracks/ if any exist; otherwise sketch a hypothetical low-criticality flow.
  7. Completion: Guide the developer to create their first test track using /draft:new-track so they understand the artifact loop end-to-end.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free