Operational discipline layer for AI-assisted software delivery: spec/ticket workflows, quality gates, and persistent engineering memory across Cursor, Claude Code, and VS Code.
Senior software architect and principal engineer reasoning — stack-agnostic. Evaluates design proposals, trade-offs, boundaries, complexity, and system evolution. Use when the user says "/architect", "design this", "evaluate this approach", "is this too complex", "architecture review", "trade-off analysis", "should I…
Autonomous implementation workflow for low-supervision execution with mandatory decision logging. Executes end-to-end without interactive approval gates, but persists auditable run logs and architecture decisions in project artifacts. Use when the developer asks for autonomous mode, low supervision, or unattended…
Capture the current work state so a developer, another agent, or a future session can resume without losing context. Use when the developer says "checkpoint", "save state", "checkpoint this", "handoff", "pause here", or "resume later".
Systematic, evidence-based code review — runs mandatory searches before any manual analysis, then produces a structured report with severity-classified findings. Stack-agnostic core with stack-specific searches and commands injected at install time. Use when the user says "/review", "code review", "review this", "PR…
Adversarial reviewer for high-impact decisions. Challenges the chosen approach from a clean, skeptical perspective — counter-argument, viable alternative, failure signals, and a Go/Go with conditions/Stop verdict.
Preview skill for council review of an idea, hypothesis, or implementation direction from multiple perspectives before turning it into a spec, ticket, ADR, or code change. Use when the developer says "council", "idea review", "validate this idea", "review this hypothesis", "should we build this", "implementation…
Minimal-friction implementation path for well-scoped tasks. Assumes the developer has full context, knows the codebase, and does not need planning ceremony. Use when the developer says "/express", wants to move fast on a well-understood single-layer change, or explicitly opts out of the full workflow.
Infrastructure as Code for .NET on Azure - defines, reviews, and troubleshoots Bicep and Terraform for .NET applications. Use when the user says "/iac", "infrastructure", "Bicep", "Terraform", "ARM template", "provision resources", "Azure resources", "deploy infra", "cloud setup", "new environment", or wants to…
Senior implementation lead — orchestrates the full feature lifecycle from problem exploration to commit. Enforces gated approval before writing code, incremental quality checks during implementation, and handoff to code-review for final validation. Stack-agnostic by default; loads stack-specific references when a…
Capture a durable project lesson in Agent Runway memory. Use when the developer says "learning", "remember this", "save this lesson", "add to memory", or when a completed task reveals a recurring decision, failure, convention, or guardrail that should influence future work.
Evaluates product quality of specs and tickets before implementation. Focuses on business value, clarity, scope, success metrics, risks, dependencies, and readiness from a Product Owner perspective. Use when the user says "/po-eval", "evaluate this spec", "evaluate this ticket from PO view", or "is this product-ready".
Guides structured refactoring to improve readability, maintainability, and SOLID/Clean Architecture alignment — without changing observable behaviour. Deepest examples are in .NET/C#, but the workflow applies to any stack. Use when the user says "/refactor", "clean up", "improve this", "simplify", "restructure"…
Lightweight risk check before continuing with a fast change. Use when the developer says "safety check", "risk check", "before I continue", "is this safe", or when a Lite workflow touches contracts, data, auth, secrets, deployment, or many files.
Creates implementation-ready specs from brief descriptions, existing markdown requirements, or prior specs. Adapts the ticket-creator workflow to spec-engineering with structured lifecycle states, execution planning, and quality gates. Use when creating or refining specs under .agent-runway/specs.
Entry point for any development task. Understands what the developer wants to do, classifies the intent and complexity, loads relevant project context, and routes to the right skill. Use when a developer doesn't know where to start, says "/start", "where do I begin", "I need to", "how do I", "I want to build", "I need…
Creates ready-to-dev tickets from brief descriptions, Jira tickets, or markdown files. Combines PO and BA perspectives to generate complete tickets with context, scope, acceptance criteria, dependencies, and QA notes. Use when creating tickets, writing user stories, preparing backlog items, or refining requirements.
Evaluates tickets and user stories for development readiness. Classifies ticket type, checks completeness against defined criteria, detects implementation antipatterns, and produces a structured report with a clear READY TO DEV verdict. Use when the user says "ticket eval", "validate ticket", "is this ready", "check…
.NET and C# implementation guidance — stack-specific. Covers application patterns, infrastructure, observability, testing, security, and API design for .NET 8/9 applications. Use when the user asks how to implement something in .NET, whether C# code is idiomatic, MediatR/EF Core patterns, .NET testing, observability…
Go implementation guidance — stack-specific. Covers project structure, idiomatic patterns, testing, security, and observability for Go backend services and CLIs. Use when the user asks about Go-specific structure, error handling, concurrency, testing strategy, or production reliability. Invoke via @go-core after…
Node.js implementation guidance — stack-specific. Covers architecture, async patterns, process lifecycle, testing, security, and observability for Node.js backend services, APIs, workers, and CLIs. Use when the user asks about Node.js-specific patterns, process management, stream handling, or production reliability.…
Python implementation guidance — stack-specific. Covers project structure, clean architecture, testing with pytest, security, and observability for Python backend services and APIs. Use when the user asks about Python-specific patterns, structuring a service, testing strategy, or production reliability. Invoke via…
React implementation guidance — stack-specific. Covers project structure, component patterns, state management, testing with React Testing Library, security, accessibility, and performance for React 18+ applications. Use when the user asks about React-specific structure, hooks, state decisions, testing strategy, or…
Rust implementation guidance — stack-specific. Covers project structure, idiomatic patterns, ownership, error handling, testing, security, and observability for Rust backend services and CLIs. Use when the user asks about Rust-specific patterns, ownership, async with Tokio, testing strategy, or production reliability.…
TypeScript implementation guidance — stack-specific. Covers architecture, application patterns, testing, security, observability, and API design for TypeScript applications. Use when the user asks how to structure TypeScript code, type-safe patterns, testing strategies, or security practices. Invoke via skill…
★not rated 2 17d agoA87 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: