Alrik Olson
Community@AlrikOlson · Portland, OR
Software Engineer, Platform Engineering
Agent Skills by Alrik Olson
Showing 13 vetted skills indexed across 1 GitHub repositories.
AlrikOlsongui-blueprint
Generates versioned ASCII GUI blueprint documents through structured user interviews.
AlrikOlsoncraft
Loads operating doctrine for projects using the think-and-ship, ministr, and serpapi MCP servers.
AlrikOlsonswitch-work
Sets a per-caller workstream and mode focus using roadmap MCP tools.
AlrikOlsonroadmap-refresh
Researches and updates an existing project roadmap via think-and-ship MCP roadmap tools.
AlrikOlsonroadmap
Advance a project roadmap one chunk at a time using think-and-ship MCP state.
AlrikOlsonhandoff
Generates a verified, copy-pasteable session-handoff prompt from think-and-ship state and current code.
AlrikOlsonroadmap-run
Executes multiple roadmap chunks in one session with per-chunk gates, commits, and subsumption checks.
AlrikOlsongui-scrutiny
Verify GUI work empirically in Storybook with Playwright, axe, and anti-slop probes.
AlrikOlsonsignals
Triage and enrich stakeholder feedback signals into validated roadmap chunks via MCP tools.
AlrikOlsonroadmap-sk
Advances roadmap chunks derived from Spec Kit spec, plan, and tasks artifacts.
AlrikOlsonbusiness-intel
Synthesizes roadmap state, codebase analysis, and market research into an executive board briefing.
AlrikOlsonroadmap-refresh-sk
Refreshes roadmaps backed by Spec Kit artifacts through research and drift detection.
AlrikOlsonadvance-work
Executes one bounded, evidenced unit of work in the focused roadmap workstream.
Frequently Asked Questions About Alrik Olson
FAQPage SchemaWhat tasks can I perform with Alrik Olson's skills?▼
You can switch and focus workstreams in shape, build, or listen mode; advance exactly one roadmap chunk or stakeholder signal per invocation; refresh roadmaps with external research; generate session handoff prompts; sketch interview-driven ASCII GUI blueprints; and empirically scrutinize GUIs through Storybook and Playwright.
Who are these skills designed for?▼
Platform and software engineers managing evolving projects across multiple workstreams, plus technical leads who want CEO/CTO-style board briefings on market, moat, tech debt, and delivery velocity. GUI-pack skills target front-end engineers enforcing design-token and object-model fidelity.
How do the skills operate at runtime?▼
Skills act as thin procedural clients over the think-and-ship, ministr, and serpapi MCP servers. State lives in native roadmap_*, ship_*, think_*, and signal_* stores; ROADMAP.md is only a generated view. Invoke slash commands like /advance-work, /switch-work, or /gui-scrutiny to run each procedure.
What are the prerequisites and dependencies?▼
A configured triad of think-and-ship, ministr, and serpapi MCP servers is required for core skills. Spec Kit variants need a speckit-initialized repo with a .specify/ directory. GUI scrutiny requires Storybook, Playwright, and axe; Spec Kit skills fall back to plain roadmap behavior otherwise.
Are these skills current or deprecated?▼
Most legacy skills (roadmap, roadmap-run, roadmap-refresh, signals, handoff, craft) are superseded by advance-work and switch-work but retained for existing users. The current surface is switch-work plus advance-work, with optional GUI-pack (gui-blueprint, gui-scrutiny) and business-intel specialist skills.