# Journey > Load BDD journey feature files as project context for a specific role. Use when the user invokes "/journey " where role is maintainer, contributor, or developer. Loads all .feature files from bdd/journeys// as living documentation context. Examples - "/journey maintainer" loads project rules (BDD workflow, conventions, testing, environment, release, architecture), "/journey contributor" loads build and setup specs, "/journey developer" loads SDK usage specs. Use when this capability is needed. - Skill: `tomevault-io/journey-2` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/journey-2` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/journey-2/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Docs & Writing - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/journey-2 --- # Journey Context Loader Load all BDD feature files for a role as working context. ## Usage Run the loader script with the role argument: ```bash bun SKILL_DIR/scripts/load-features.ts ``` Roles: `maintainer`, `contributor`, `developer` ## After Loading - The feature files ARE the documentation. Use them as the source of truth for all project rules and conventions. - When the user asks about project norms, answer from the loaded features. - When implementing code, check loaded features for relevant constraints. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/deepractice) — claim your Tome and manage your conversions.