it-journey

Run one incremental pass of the IT-Journey content-improvement loop. Use when asked to curate/improve content, run the daily CMS loop, work the .cms worklist, fix frontmatter/SEO/freshness across pages, or group content improvements into a PR.

Run one agentic, on-brand content-improvement pass for a single IT-Journey collection and open one gated PR. The Lane B (substantive) executor that wires the cms-curator loop to the brand-voice system. Use when asked to "improve a collection", "run the content factory", or driven by content-factory.yml in CI.

Consume ONE walkthrough's verified evidence and apply the smallest content-only edits that fix its VERIFIED issues, under a deterministic keep/revert gate. The fix-lane inverse of quest-walkthrough — the walker plays a slice and witnesses where it breaks; this skill repairs exactly what it witnessed, proving each edit helped with a deterministic signal (never the model's own grade). Use when asked to "fix a walked quest", run the quest fix lane, or driven by the fix arm of the quest-perfection loop. Writes only quest content; never branches, commits, or merges.

Forge a "quest-forge proposal" GitHub issue into a complete, validated epic-quest campaign in pages/_quests/codex/ and open one gated PR. Use when asked to "forge a quest from an issue", turn an epic-quest proposal into content, or driven by quest-forge.yml in CI. Composes the deterministic collector (forge_issue.py) + quest.instructions + brand-voice.

PostHog integration for any Ruby application using the Ruby SDK

Load IT-Journey brand context (values, voice, style, section guide) before drafting or editing a post or muse. Use when writing a new article, writing a short-form devops-news muse, rewriting for voice/tone, or checking that content matches a section's brand profile.

Run ONE incremental pass of the IT-Journey issue autopilot — analyze open issues, group them into PR-sized batches, then either route/triage them (close stale bot-noise, decompose epics, flag for a human) or resolve one batch into a single grouped PR. Use when asked to triage issues, work the issue queue, run the issue-autopilot loop, or drive the issue-triager / issue-resolver agents. Mirrors the cms-curator loop idiom.

Play a linked set of quests for one character + level end-to-end in an isolated sandbox, as if you were a learner, and write ONE evidence-based session report. Use when asked to "walk a quest", "validate a quest as an end user", "run the daily quest walkthrough", or driven by quest-walkthrough.yml in CI. Composes the deterministic planner (walkthrough_plan.py) + the agentic execute engine (agentic_validate.py) + the quest validation rubric.

Build, run, and drive the IT-Journey Jekyll site. Use when asked to start IT-Journey, serve the site locally, preview a content change, take a screenshot of a page, smoke-test routes, or validate frontmatter/quests.

Run ONE pass of the IT-Journey frontend canary — crawl it-journey.dev for UI/UX/a11y/theme defects, classify theme-vs-content, dedup, and file the theme issues upstream to bamr87/zer0-mistakes. Use when asked to test the it-journey.dev frontend, scout for theme bugs, run the frontend canary, or file theme issues upstream. Drives the theme-scout agent.