runner-research
Runner Research
Research AI agent runners to keep LeanSpec's runner registry and configurations current as the ecosystem evolves rapidly.
Workflow
1. Gather Current State
Read the runner registry source to understand what LeanSpec currently supports:
rust/leanspec-core/src/sessions/runner.rs # RunnerRegistry::builtins()
Read the current runner catalog reference for known details:
- See references/runners-catalog.md for the full catalog of tracked runners
2. Research Updates
More from codervisor/lean-spec
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
54leanspec-development
Development workflows, commands, publishing, CI/CD, changelog management, and contribution guidelines for LeanSpec. Use when contributing code, fixing bugs, setting up dev environment, running tests or linting, working with the monorepo structure, looking up build/dev/test/publish/format/lint commands, preparing releases, publishing to npm, bumping versions, syncing package versions, testing dev builds, troubleshooting npm distribution, updating changelogs, triggering CI/CD workflows, monitoring build status, debugging failed runs, managing artifacts, checking CI before releases, or researching AI agent runners. Triggers include any development, scripting, publishing, CI/CD, changelog, or runner research task in this project.
44watch-ci
Watch GitHub Actions CI status for the current commit until completion. Use after pushing changes to monitor build results.
40github-integration
>
40parallel-worktrees
>
40leanspec-sdd
Spec-Driven Development methodology for AI-assisted development. Use when working with specs, planning features, creating/implementing/refining/organizing specs, checking progress, updating specs, task breakdowns, design decisions, or any task involving a specs/ folder or .lean-spec/config.json.
16