---
name: roadmap
description: "Builder employee · The EXCLUSIVE owner of the AIEB 7-Day Challenge—its scorecard, fresh test, completion report, and credit-first flow—and the build-roadmap/triage front door. ALWAYS USE for 'start my Challenge', 'continue my Challenge', 'Challenge progress', 'create my scorecard', 'run my fresh test', 'generate my completion report', 'apply my Challenge credit', 'what's next', 'what should I build next', 'where am I', 'roadmap', 'continue building', 'I keep doing X by hand', or 'I don't know what to build'. Challenge mode reuses saved intake and tracks seven checkpoints. Ladder mode tracks post-onboarding AIEB progress. Triage mode routes plain-language pain to the right skill, system, harness, MCP, hook, or command builder. Also use for repeated manual work when the artifact is not named. Do NOT use for first-run setup (onboard), an operational business diagnosis outside an active Challenge (business-x-ray), or when the exact artifact is already named (use its meta-create builder)."
---

# roadmap — MCP loader

Load the licensed instructions before doing this job:

`get_skill(skill_id="roadmap", path="SKILL.md", section="contents")`

The tool prefix varies by host. Search available and lazy-loaded tools for any name ending in `get_skill`. If none exists, run the local `check-setup` skill and follow its repair. Do not improvise install commands or versions, and never ask for a license key in chat.

Follow the returned routing map. Fetch only the section this run needs, then fetch each workflow, reference, template, example, or script it names with the same `skill_id` and exact remote path. Those files live on the AIEB server, not local disk. If a fetched instruction says to run a script, fetch it first and follow its safety instructions.

If the server returns a 🔒, entitlement, or setup message, relay its explanation and next action once. Do not retry a locked call, reconstruct paid content, or claim setup is fixed before a live fetch succeeds.